anomalyco / anomalyco/browser-control
fillInput rejects contenteditable elements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 407
- Forks
- 20
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 33
Description
Problem
fillInput throws unless the locator resolves to an input or textarea:
locator.evaluate: Error: fillInput expects an input or textarea locator
Rich-text editors built on contenteditable DIVs (e.g. LinkedIn headline/About editors) cannot be filled, forcing a manual click + Ctrl+A + keyboard.type fallback.
Environment
Relay 0.6.0, extension 0.0.24, protocol v2, extension-backed Chromium tab.
Request
Accept contenteditable elements in fillInput (focus + select-all + insert text), mirroring the documented input/textarea fallback path.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the fillInput entry point and compare its documented input/textarea fallback path with the requested contenteditable behavior. Verify that contenteditable elements can be focused, select all, and receive inserted text, while existing input and textarea behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100