Closed
Bug 282104
Opened 20 years ago
Closed 20 years ago
BoxObject's InvalidatePresentationStuff needs ability to tell document to remove it from its boxobject table
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
VERIFIED
DUPLICATE
of bug 282105
People
(Reporter: bugs, Unassigned)
Details
We can get into situations where an element's box object becomes useless because
of some sequence of events like this: frames are destroyed (e.g. in response to
opacity changes (?)), InvalidatePresentationStuff is called on the box object in
question, but the document still holds it in its boxobject table, so that when
script attempts to subsequently access boxobject methods, the busted boxobject
with null mPresShell etc is used, and none of the methods work.
This was noted in earlier testing versions of my new prefwindow where I had a
listbox and was attempting to access properties on it after the pane was faded in.
The solution appears to be that in some cases when InvalidatePresentationStuff
is called, we want to tell the document to take it out of the boxobject table,
which is what this patch does. See also the patch in 282103, which updates the
call sites in nsXULDocument.
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 282105 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•