Closed
Bug 292978
Opened 20 years ago
Closed 2 years ago
Firing restore events can mutate the docshell tree
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
INCOMPLETE
mozilla1.9alpha1
People
(Reporter: bzbarsky, Unassigned)
References
Details
FireRestoreEvents can trigger docshell tree mutations by event handlers. Since we're iterating mChildList, which can change during said mutations, we need to figure out exactly what behavior we want here.
| Reporter | ||
Updated•20 years ago
|
Blocks: blazinglyfastback
Comment 1•19 years ago
|
||
The code isn't quite the same as when this was filed. Now, the events are dispatched when FinishRestore is called, which happens on a plevent. There may still be a situation where handling a restore for one docshell removes elements from the child list such that a later docshell doesn't get restore called on it at all. We could probably solve this by building up the list of children to fire restore before we actually walk the list. I don't think this is likely to be a problem on the web though, since these events are brand-new. I think this is probably something we can fix in a point release.
Target Milestone: --- → mozilla1.9alpha
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
Comment 2•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
Lacks steps to repro.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•