Closed Bug 1575437 Opened 6 years ago Closed 1 year ago

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 APIs, defect, P3)

Product:
Core
Component:
DOM: Performance APIs
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

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 test link: https://wpt.fyi/results/resource-timing/nested-context-navigations-iframe.html?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox&product=safari%5Bexperimental%5D&aligned

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.

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?

Group: firefox-core-security → dom-core-security
Component: Untriaged → Document Navigation
Flags: needinfo?(bugs)
Product: Firefox → Core
Regressed by: 1563587
See Also: → 1572932
Version: other → unspecified
Keywords: regression

The failure is that we expose even less data than other browsers.

Group: dom-core-security
Flags: needinfo?(bugs)

right.

And this is more about Resource Timing

Component: Document Navigation → Performance
Priority: -- → P3
Has Regression Range: --- → yes
Component: Performance → DOM: Performance
Severity: normal → S3

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.

Flags: needinfo?(fdoty)
Flags: needinfo?(fdoty)

yes

Bug 1572932 is fixed - is there more left to do in this bug?

Flags: needinfo?(smaug)

Looks like the wpts pass now.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(smaug)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.