What do we need to integrate with the clipboard api?
Open
Nobody has claimed this yet.
ContentEditableEvents
Future
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
contentEditable=Events lacks execCommand, so what do we need in order to still allow clipboard access (using custom UI controls)?
Contributor guide
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
The issue mentions contentEditable=Events, execCommand, custom UI controls, and clipboard access, but names no files, tests, or entry points. Start by reviewing how contentEditable=Events relates to clipboard access and identify the integration requirements. Done means the needed approach for custom clipboard controls is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100