Guidance on site and/or UA override UI for the effect of this feature
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
In #2 we discussed a bit the idea of browser's having a setting to let users override the value, and this is what chromium has implemented:
@tunetheweb and I were discussing this a bit in the TAG issue. Let's use this issue for aligning on the question of what the spec should say about this and/or guidance for site developers on ensuring users have control over their experience.
Maybe the spec should focus on the developer guidance of letting users customize behavior, but also mention that user agents may want to consider providing an override as well? Personally I'd hope (and actually expect) that the browser-level override is entirely unnecessary and unused, hopefully that's something we can test with the Chrome implementation.
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 issue #2 and the linked TAG design-review discussion to understand the existing proposal and questions about user-agent overrides. Done means reaching agreement on what the specification should say and whether developer guidance is needed for user control.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100