1733503 - redirectStart and redirectEnd should not be exposed when there's a cross origin redirect for PerformanceNavigationTiming

Status: RESOLVED FIXED

(Core :: Performance, defect)

Description

[Sean Feng [:sefeng]]

Currently there are a couple github issues that are discussing about PerformanceNavigationTiming with cross origin redirects. See https://github.com/w3c/navigation-timing/issues/160 and https://github.com/whatwg/html/pull/7105. So we might need to change this again in the future, like to respect the TAO header.

However, I think at the moment, we should comply with existing expected behaviour, to not expose these 2 timings.

Comment 1

[Sean Feng [:sefeng]]

Attachment: Bug 1733503 - Don't expose redirectStart and redirectEnd when there's a cross-origin redirect for PerformanceNavigationTiming r=smaug

The actual text for hiding these information is actually missing at the
moment. This is the pending PR https://github.com/whatwg/html/pull/7105
which should fix it.

In addition to this PR, the obsolete (obsolete, but still accurate) definition
for redirectStart and redirectEnd has specified that when there's a
cross-origin redirect, these timings should not be exposed.

Obsolete definition: https://w3c.github.io/navigation-timing/#dom-performancetiming-redirectstart

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f9bfbe44d85f
Don't expose redirectStart and redirectEnd when there's a cross-origin redirect for PerformanceNavigationTiming r=smaug

Comment 3

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/f9bfbe44d85f