Closed
Bug 327886
Opened 19 years ago
Closed 17 years ago
tabbrowser depends on random menus in browser.xul
Categories
(Toolkit :: XUL Widgets, defect)
Toolkit
XUL Widgets
Tracking
()
RESOLVED
INVALID
People
(Reporter: Mook, Unassigned)
References
()
Details
(See URL)
If the elements menu_closeWindow and menu_close don't exist, setStripVisibilityTo() would throw. Kinda hit me when using <tabbrowser> in my XulRunner app...
Would be nice if they fired an event instead of knowing about the surrounding XUL, but a temporary workaround would be to make it look before leaping (by making sure those elements exist)...
Workaround: make sure elements with those ids exist in the surrounding XUL. They just have to be DOM elements, not even XUL :)
Comment 1•18 years ago
|
||
(tabbrowser will likely be moved out of toolkit eventually - bug 339964)
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Comment 2•18 years ago
|
||
*** Bug 361489 has been marked as a duplicate of this bug. ***
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•