Test for "iframe navigations are not observable by the parent, even after history navigations by the parent" fails in Firefox Nightly
Categories
(Core :: DOM: Performance, defect, P3)
Tracking
()
People
(Reporter: proof131072, Unassigned)
References
(Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36
Steps to reproduce:
Firefox Nightly test link: https://wpt.fyi/results/resource-timing/nested-context-navigations-iframe.html?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned
The second link shows that test for "iframe navigations are not observable by the parent, even after history navigations by the parent" fails in Firefox Nightly.
Actual results:
"iframe navigations are not observable by the parent, even after history navigations by the parent" fails in Firefox Nightly.
Expected results:
"iframe navigations are not observable by the parent, even after history navigations by the parent" should result pass on Nightly.
Comment 1•5 years ago
|
||
I think this is just a dupe of bug 1572932, and I don't see any reason to keep it sec-sensitive, but perhaps I'm missing something. Olli?
Updated•5 years ago
|
Comment 2•5 years ago
|
||
The failure is that we expose even less data than other browsers.
Comment 4•5 years ago
|
||
And this is more about Resource Timing
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 13 votes.
:fdoty, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Description
•