Closed
Bug 155327
Opened 23 years ago
Closed 23 years ago
nsViewManager and nsPresShell are unaware of stacked event queues
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 155328
People
(Reporter: rginda, Assigned: roc)
References
()
Details
nsViewManager and nsPresShell do not deal with the fact that the queue that was
active when they were initialized may not be the queue they should always post
events to.
In the case where an event queue us pushed, reflow and invalidate events end up
stuck in the previous queue, and parts of the UI (the parts that intialized
before the new queue) no longer paint.
The simplest testcase is to load netscape.com in one window, and
"javascript:void setTimeout(alert, 0, 1)" in another (see the URL of this bug.)
When the setTimeout executes, you'll notice that the netscape.com marquee stops
animating.
This problem is much more serious in the js debugger, where the debugger UI
stops repainting properly when the user stops in a timeout.
I'm not exactly sure why we only see this problem in timeouts. I suspect, for
non-timeouts, something else comes along to force us to update. Perhaps related
in some way to native or idle events.
Dupe of bug 155328 (seeing that one has a patch attached)?
Comment 2•23 years ago
|
||
*** This bug has been marked as a duplicate of 155328 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•23 years ago
|
||
Ooops. The first time I submitted this bug I got an error due to a bogus CC
address. I suspect a bug in bugzilla.
Updated•6 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•