Open
Bug 381286
Opened 19 years ago
Updated 3 years ago
Deleting <treechildren/> doesn't hide scrollbar
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
NEW
People
(Reporter: neil, Unassigned)
Details
Attachments
(1 file)
|
945 bytes,
patch
|
Details | Diff | Splinter Review |
When you append a <treechildren/> to a tree then when the tree body frame ensures its view it updates the scrollbars. However when you remove the <treechildren> the tree body frame doesn't update the scrollbars. I've verified this with a custom view (thread pane), RDFliner and content view.
| Reporter | ||
Comment 1•19 years ago
|
||
Attachment #265382 -
Flags: review?(enndeakin)
Comment 2•19 years ago
|
||
Comment on attachment 265382 [details] [diff] [review]
Proposed patch
Looks OK, but is it s a good idea to fire events while in the frame's Destroy method?
| Reporter | ||
Comment 3•19 years ago
|
||
(In reply to comment #2)
>(From update of attachment 265382 [details] [diff] [review])
>Looks OK, but is it s a good idea to fire events while in the frame's Destroy method?
Probably not, but Smaug may know how to fire them asynchrously (note that GetMinSize could fire events, which may not be a good idea either).
Comment 4•19 years ago
|
||
Could you upload a testcase?
Do you really need to fire any events in this case?
(Well, there is anyway DOMNodeRemoved.)
What happens usually when the child elements of an overflow:auto are removed?
Comment 5•19 years ago
|
||
Hmm, I guess underflow event is dispatched.
Comment 6•19 years ago
|
||
Comment on attachment 265382 [details] [diff] [review]
Proposed patch
You can fire events asynchronously by implementing nsIRunnable as in several places in the menu code.
Attachment #265382 -
Flags: review?(enndeakin)
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: xptoolkit.trees → xptoolkit.widgets
Comment 7•8 years ago
|
||
The plan is to remove the XUL "tree" widget in future (bug 1446335), but this has a patch, so for now I'm not going to wontfix this.
Assignee: jvarga → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•