Open
Bug 1909699
Opened 2 months ago
Updated 1 month ago
Restore text fragment directive in case of client/server side redirects
Categories
(Core :: DOM: Navigation, enhancement)
Core
DOM: Navigation
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox128 | --- | unaffected |
firefox129 | --- | unaffected |
firefox130 | --- | disabled |
People
(Reporter: phorea, Unassigned)
References
(Blocks 2 open bugs)
Details
Found in
- Nightly 130.0a1;
Affected versions
- Nightly 130.0a;
Tested platforms
- Ubuntu 22;
- macOS 14;
- Windows 10;
Affected platforms
- Ubuntu 22;
- macOS 14;
- Windows 10;
Preconditions
- Have dom.text_fragments.enabled to TRUE
Steps to reproduce
- Access https://github.com/WICG/scroll-to-text-fragment/issues/233#:~:text=As%20for%20case
- Observe the address bar link
- Access Browsing History
Expected result
- Text fragments directive is available in history/address bar after load
- Browsing history is deduped
- This doesn’t seem to be scoped for the first version
Actual result
- Text fragments directive is available address bar after load in what the guess is that is removed client/server side
Regression range
- Not a regression.
Additional notes
- In Chrome the same behavior can be reproduced
You need to log in
before you can comment on or make changes to this bug.
Description
•