Open Bug 1306519 Opened 8 years ago Updated 11 months ago

Reimplement noreferrer/noopener anchor navigations on top of window.open with noopener option or some shared backend

Categories

(Core :: DOM: Navigation, defect, P3)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox52 --- affected

People

(Reporter: bzbarsky, Unassigned)

References

(Depends on 1 open bug)

Details

Attachments

(1 obsolete file)

When we move noopener window.open into a separate process, it woudl be nice if the same thing happened for anchor navigations. This is not as simple as it seems, because we have to propagate a bunch of state over to the navigation. Clearly referrer policy and referrer and whether noreferrer is in use, but probably other things hanging off the anchor element. Maybe the right answer is to share some backend with window.open() instead of reusing it altogether....
Priority: -- → P3
See Also: → 1527287
Component: DOM → DOM: Core & HTML
Component: DOM: Core & HTML → DOM: Navigation
Blocks: 1473858
Depends on: 1550840
Severity: normal → S3
Attachment #9385875 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: