Open
Bug 1550387
Opened 6 years ago
Updated 2 years ago
Support cancelling content JS during navigation for different paths on the same domain
Categories
(Core :: DOM: Navigation, enhancement, P3)
Core
DOM: Navigation
Tracking
()
NEW
People
(Reporter: squib, Unassigned)
References
Details
Currently, we only cancel content JS (see bug 1493225) during navigation when the start and end URLs are different domains. This is to ensure that the navigation triggers a full pageload. We could improve this to include different paths on the same domain, but we need to be sure that the two "pages" weren't the result of a pushState
(or similar) call.
Comment 1•6 years ago
|
||
This bug looks like it belongs somewhere in DOM.
Component: IPC → DOM: Content Processes
Comment 2•5 years ago
|
||
Moving to "DOM: Navigation" component
P3
wait for session history in parent
Component: DOM: Content Processes → DOM: Navigation
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•