Behavior of queryCommandEnabled
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
From @zetafunction on May 19, 2015 16:39
Right now, queryCommandEnabled("paste") in Chrome only returns true if we're in an editable area (and https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#enabled specifically mentions that cut and paste are not always enabled, though it doesn't really define when that would be).
However, executing a paste via the top-level menu or the key combination still fires a paste event at the page.
It seems like queryCommandEnabled("paste") should just match when we allow execCommand("paste") / Ctrl+V / etc?
Copied from original issue: w3c/clipboard-apis#7
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
Start by reading the issue's references to queryCommandEnabled("paste"), execCommand("paste"), and paste events. Determine and document the intended relationship between these behaviors, with the relevant editing specification updated once the expected behavior is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100