User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081112 Minefield/3.1b2pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081112 Minefield/3.1b2pre Assume you've installed a few extensions, which add items to the Tools menu. Running the following code in an extension: var toolsPopup = document.getElementById("menu_ToolsPopup") will hide those items. But the same effect, coded differently: var toolsPopup = document.getElementById("tools-menu").childNodes; leaves the menu intact. Both methods return a valid XULElement object. I haven't checked whether this happens to other menus besides Tools... Reproducible: Always Steps to Reproduce: 1. Install a few extensions that add Tools menu items (e.g. DOMi, Firebug...) 2. Run the first snippet of code in an extension. 3. Open the Tools menu. 4. Restart Fx, and run the second snippet of code instead. Actual Results: When using the first snipped of code, only the built-in menu items (i.e. those that are defined in chrome://browser/content/browser.xul) stay visible. The rest are hidden. Expected Results: If I understand the two code snippets correctly, the second one should behave the same as the first. The only difference I can see is if menu_ToolsPopup is an overlay target and that somehow messes things up...?
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO. Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME. This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.