Closed
Description
History records the redirected-to URL and triggering history.back() on an iframe creates a ResourceTiming object with name attribute set to said URL.
- PoC: http://vwzq.net/lab/xreadurl/ - FF, IE, Chrome all have the same issue.
- Chrome bug: https://code.google.com/p/chromium/issues/detail?id=511616
- History traversal: https://html.spec.whatwg.org/multipage/browsers.html#traverse-the-history-by-a-delta
name: This attribute must return the resolved URL of the requested resource. This attribute must not change even if the fetch redirected to a different URL -- current definition.
Similarly, our processing section records the resolved URL of the requested resource. As such, I don't believe this is a RT spec bug, but the fact that all implementations are subject to this does indicate that we may want to add some language to make this explicit.
Metadata
Metadata
Assignees
Labels
No labels