`Open In New Tab` doesn't scroll for text fragments
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
People
(Reporter: sefeng211, Assigned: jjaschke)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
Attachments
(1 file)
STR:
- Open https://github.com/WICG/nav-speculation/issues/368
- Right click the
source
link in the description withOpen In New Tab
A new tab is opened, but Firefox doesn't scroll to the highlight. Chrome does scroll though.
This is 20250321040811 build on Linux
Assignee | ||
Comment 1•2 months ago
|
||
I can repro. This is only if the link is opened via the context menu, and also occurs for Open in New Window
.
about:logging hints that the user involvement check is not working as expected.
Updated•2 months ago
|
Assignee | ||
Comment 2•2 months ago
|
||
Some more context after having a few offline discussions around this:
The immediate reason for not scrolling is that opening a link in a new tab / window first opens about:blank
in the new tab/window, then navigates to the link from there. That means that the triggering principal, which is currently used to check for user involvement, is the null principal (instead of the system principal which one would expect, since the action was triggered from the context menu). Also, it seems that there is a difference between CTRL-Click on a link and Context Menu -> Open in a new Tab w.r.t. user activation (going through context menu = no user activation).
In order to fix this, we need to properly implement User Involvement -- which coincidentally we currently do in our Navigation API work (Bug 1777171 as meta).
Assignee | ||
Updated•27 days ago
|
Updated•25 days ago
|
Assignee | ||
Comment 4•24 days ago
|
||
Updated•24 days ago
|
Updated•23 days ago
|
Comment 6•16 days ago
|
||
bugherder |
Updated•11 days ago
|
Reproducible on a 2025-08-12 Firefox Nightly build on Windows 10.
Verified as fixed on Firefox Nightly 144.0a1 and Firefox 143.0b2 on Windows 10, Ubuntu 22, macOS 15.
Description
•