schickling/chromeless

Performing copy/paste clipboard operations via chromeless

Open

#366 opened on Dec 21, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (606 forks)batch import
help wantedquestion

Repository metrics

Stars
 (13,240 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I was trying to test copy/paste in Chromeless but it’s not working. I’m not sure if I’m missing something or it’s rather a common problem. Is there any known approach for performing clipboard operation using Chromeless? I’ve tried performing CTRL+C and CTRL+V key strokes but it doesn’t seem to work:

const chromeless = new Chromeless({ remote: true })

const screenshot = await chromeless
  .goto('https://vimeo.com/search')
  .type('Lorem ipsum')
  .press(65, 1, 17)
  .press(88, 1, 17)
  .focus('.js-topnav_menu_search_input')
  .press(86, 1, 17)
  .screenshot()

console.log(screenshot)

await chromeless.end()

Live example: https://chromeless.netlify.com/#src=const%20chromeless%20=%20new%20Chromeless(%7B%20remote:%20true%20%7D)%0A%0Aconst%20screenshot%20=%20await%20chromeless%0A%20%20.goto('https://vimeo.com/search')%0A%20%20.type('Lorem%20ipsum')%0A%20%20.press(65,%201,%2017)%0A%20%20.press(88,%201,%2017)%0A%20%20.focus('.js-topnav_menu_search_input')%0A%20%20.press(86,%201,%2017)%0A%20%20.screenshot()%0A%0Aconsole.log(screenshot)%0A%0Aawait%20chromeless.end()

Contributor guide

Research direction
Investigate how Chromeless implements keyboard events via Chrome DevTools Protocol. Check if clipboard operations require special permissions or if the Ctrl+C/V key codes are correctly mapped. Look for existing discussions or documentation on clipboard handling in headless Chrome.
Tech stack
typescript
Domain
testingdeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ChromelessNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75