Closed
Bug 359486
Opened 18 years ago
Closed 8 years ago
Ranges need to flush the sink when accessed
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: sicking, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: regression)
Since ranges now depend on nsIMutationObserver notifications to update themselves. However since the sink doesn't always send those out we should flush the sink whenever someone accesses a range. However in most cases this won't actually be noticeable because ranges don't react to ContentAppended calls which is what the sink usually generates. However it can sometimes generate ContentInserted calls as well when malformed tables are used.
Reporter | ||
Comment 1•18 years ago
|
||
It may actually be non-trivial to fix this since we may up causing way more reflows if the ranges used in selection are accessed a lot during page load. An alternative solution would be to make sure that we never hold off on ContentInserted calls from the sink.
Updated•15 years ago
|
Assignee: traversal-range → nobody
QA Contact: ian → traversal-range
Assignee | ||
Updated•12 years ago
|
Component: DOM: Traversal-Range → DOM: Core & HTML
Comment 2•8 years ago
|
||
This bug has been tagged for regression and/or closure. Please assist - how can I confirm/test this and proceed.
Flags: needinfo?(jonas)
Comment 3•8 years ago
|
||
Closing as Incomplete: Feel free to reopen the bug if the issue still reproduces on a current build. Please provide detailed Steps, Operating System and Firefox version.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Reporter | ||
Comment 4•8 years ago
|
||
Yeah, I think this is no longer a problem. But I don't remember exactly how to reproduce any more.
Flags: needinfo?(jonas)
You need to log in
before you can comment on or make changes to this bug.
Description
•