MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[BackToOpener] Make a stronger case for this being opt-in
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
I think the biggest question mark about this proposal is whether it should be opt-in or applied automatically across the entire user agent.
The explainer already discusses this somewhat. However, I don't find its logic that convincing. Many of the arguments, especially in https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/BackToOpener/explainer.md#user-facing-problem, for why this is important to solve, steer me in the direction of it applying everywhere.
Note that some user agents, e.g. Chrome for Android, already apply this behavior across the entire user agent.
I would be most convinced if you had clear examples of cases where this behavior would be confusing or harmful.
Contributor guide
No contributing guide indexed for this repository
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
Read the BackToOpener explainer, especially the User-facing problem section linked in the issue, and review its current reasoning about opt-in versus automatic application. Find clear examples where applying the behavior across the user agent would be confusing or harmful, then use them to strengthen the explainer's case for opt-in behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100