Open
Bug 769189
Opened 12 years ago
Updated 2 years ago
[BrowserAPI] Differentiate between regular locationchange and "error locationchange" events
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: justin.lebar+bug, Unassigned)
References
Details
nsIWebProgressListener's locationchange can either be a "normal" locationchange or an "error" locationchange.
The latter case occurs when, for example, we can't resolve a domain. We still send a locationchange to that domain, but we indicate that it's of type error.
Embedders care about this because: Suppose I visit nytimes.com and I'm not connected to the network. We'll get a locationchange of type error to nytimes.com, and then a titlechange saying "page not available" (or whatever). The embedder shouldn't save this title as the canonical title for nytimes.com, e.g. in the history. (Desktop Firefox has this bug.)
It might be less of a footgun to modify the title/iconchange events so that they indicate whether they're for a normal page or an error page. But we should probably modify the locationchange event too.
Assignee | ||
Updated•12 years ago
|
Component: DOM: Mozilla Extensions → DOM
Comment 1•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•