MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[BackToOpener] Be clearer about developer-observable effects
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
It isn't clear if this proposal is purely user-facing, or also developer-facing.
the opener's URL is added to the destination browsing context's history
which implies that history.length will become 2, and history.back() will navigate back to the opener URL. (In the current browsing context/tab, I guess?)
However, I think it would be better if this feature were solely user-facing. Instead of modifying anything about developer-facing session history, it would solely modify the browser's back button behavior.
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 BackToOpener/explainer.md, especially the Privacy and Security Considerations section linked in the issue, and review the stated effects on session history. Clarify whether history.length and history.back() should change or whether only browser back-button behavior is affected. Done means the explainer explicitly documents the developer-observable behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100