New attribute to control UA-provided writing assistance
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- html
- Domain
- web-dev
Research direction
Read the WHATWG/html#9065 and WHATWG/html#10018 discussions, then review the Writing Suggestions explainer and Bugzilla issue 1871621. Compare the proposed writingsuggestions attribute and its inheritance behavior with Mozilla’s standards-positions guidance; done means recording a decided Mozilla position.
Written by the indexing model from the issue text.
Description
Request for Mozilla Position on an Emerging Web Specification
- Specification Title: New attribute to control UA-provided writing assistance
- Specification or proposal URL (if available): whatwg/html#9065, whatwg/html#10018
- Explainer URL (if available): https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WritingSuggestions/explainer.md
- Caniuse.com URL (optional):
- Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1871621
- Mozillians who can provide input (optional): @smaug---- @zcorpan
- Description:
UAs are starting to provide writing suggestions to users as they type on various editable fields across the web (see the use case section below). While this is generally useful for users, there are cases when developers may want to turn off UA-provided writing assistance, such as extensions or sites that wish to provide similar functionality on their own.
We propose the addition of a new attribute called writingsuggestions with values on/off that would allow developers to turn on/off browser-provided writing suggestions. This attribute will have a default state per element, as established by the UA. The attribute's state for an element can also be inherited from ancestor elements, thereby allowing developers to control this functionality at a per-element or per-document/sub-document scale.
- Related discussion: whatwg/html#9065
- Dominant language
- HTML
- Stars
- 760
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
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.
More from mozilla/standards-positions
-
topic: WebAssembly venue: W3C
Difficulty 5/5 Over a week Newbie friendliness 35/100
mozilla/standards-positions#1454 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
mozilla/standards-positions#1453 ·
-
topic: HTML venue: WHATWG
mozilla/standards-positions#1452 · 1 comment · 1 assignee ·
-
topic: CSS venue: W3C
mozilla/standards-positions#1450 · 2 comments · 1 assignee ·
-
topic: CSS venue: W3C
Difficulty 5/5 Over a week Newbie friendliness 25/100
mozilla/standards-positions#1448 · 2 comments ·
All issues in mozilla/standards-positions
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
tvOS
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bvaughn/react-resizable-panels#751 · 1 comment ·
-
www.wiwo.de OpenN: AdGuard Browser Extension P3: Medium T: Annoyance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
AdguardTeam/AdguardFilters#242026 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 92/100