Open
Bug 1733044
Opened 3 years ago
Updated 2 years ago
[navigation timing] Navigation Timing should not export connection timing when cross-origin redirects occur
Categories
(Core :: DOM: Performance, enhancement)
Tracking
()
UNCONFIRMED
| Performance Impact | none |
People
(Reporter: noam.j.rosenthal, Assigned: sefeng)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.61 Safari/537.36
Steps to reproduce:
See spec change here: https://github.com/whatwg/html/pull/7105
and new test here: https://github.com/web-platform-tests/wpt/pull/30978
Actual results:
domainLookupTime and other internal navigation timing properties are exposed, even though cross-origin redirects occurred
Expected results:
navigation timing should not expose cross-origin timing information.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Component: Untriaged → Performance
Product: Firefox → Core
|
Assignee | |
Updated•3 years ago
|
Assignee: nobody → sefeng
|
||
Updated•2 years ago
|
Whiteboard: [qf-]
|
||
Updated•2 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
|
||
Updated•2 years ago
|
Component: Performance → DOM: Performance
You need to log in
before you can comment on or make changes to this bug.
Description
•