Closed
Bug 1578357
Opened 5 years ago
Closed 4 years ago
Allow user activation visibility on same-origin connected subtree
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla75
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: edgar, Assigned: edgar)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
This bug is filed for tracking same-origin visibility which Chrome added this relax mode for the regression they encounter, see https://bugs.chromium.org/p/chromium/issues/detail?id=947024. They are working on removing this same-origin visibility by introducing a way to transfer activation to a specified frame.
If we encounter same issue, we could consider implementation same thing, but doesn't need it for now.
Assignee | ||
Updated•5 years ago
|
Summary: Consider allowing user activation visibility on same-origin frames → Consider allowing user activation visibility on same-origin connected subtree
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Spec discussion: https://github.com/whatwg/html/pull/3851
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → echen
Assignee | ||
Comment 2•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Summary: Consider allowing user activation visibility on same-origin connected subtree → Allowing user activation visibility on same-origin connected subtree
Assignee | ||
Updated•4 years ago
|
Summary: Allowing user activation visibility on same-origin connected subtree → Allow user activation visibility on same-origin connected subtree
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Comment 4•4 years ago
|
||
Pushed by echen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/970330ac9c44 Allow user activation visibility on same-origin connected subtree; r=smaug
Comment 6•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
You need to log in
before you can comment on or make changes to this bug.
Description
•