July 29th F2F Agenda Item - Opt-in/opt-out of editing features and menus
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Context menus currently exist for formatting (on Safari) and for clipboard related actions (other browsers)
These three points could possibly be combined into a proposal that works for everyone
○ JS editor developers have asked for a way to be able to disable context menus (especially on mobile).
○ Hallvord Steen (Clipboard API) has defined a way to define how to disable clipboard actions in the standard context menu (beforeCopy, beforePaste, etc. events which are triggered at the moment the menu is potentially shown) but he is not happy with the implementation and wonders if we could do something better in the editing taskforce.
○ It was proposed at the editing meeting at TPAC to create a way to opt-in/out of features which would then also disable/enable corresponding editing menus
Which spec should this go into? (input events being one option)
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
No source file or test is named; start by reading the Input Events and Clipboard API/context-menu proposals described here and the editing taskforce discussion. Done means selecting the target spec and defining coherent opt-in/opt-out behavior for editing features and menus, including the listed browser and mobile cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- api, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100