Closed Bug 185512 Opened 23 years ago Closed 23 years ago

JScript Error In chrome

Categories

(Core :: Networking: Cookies, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 176999

People

(Reporter: dwat001, Assigned: morse)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Error: element has no properties Source File: chrome://cookie/content/cookieNavigatorOverlay.xul Line: 128 No visual idea or what went wrong. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Please tell us steps to reproduce this.
Assignee: sgehani → morse
Component: XP Apps → Cookies
QA Contact: paw → tever
OK have had more time to track down. On any Page (apparently, I have tested http://bugzilla.mozilla.org/show_bug.cgi?id=185512 , about: , http://slashdot.org/ and a local page which I got down to "<html></html>" with the problem still occuring. This error occurs (appares in the JavaScript Console) when the Tool menu or any of it's children are visulised. Steps 1. Open a new instance of Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Steps 2. Browse to page http://slashdot.org steps 3. Menu->Tools->Web Development->Javascript Console (in my case there are two instancese of the error there already) steps 4. clear all messages steps 5. arrange so you can see both windows (console and browser) steps 6. click on menu->Tools in the browser window ( a error will appare in console) steps 7. Move mouse to menu->Tools-><any with sub menu> in browser an error occurs when any of the sub menus are visulised. Hope that is enough information. all the errors are Error: element has no properties Source File: chrome://cookie/content/cookieNavigatorOverlay.xul Line: 128
dupe of "JavaScript error generated by invoking Tool Menu items {error in cookieNavigatorOverlay.xul}" *** This bug has been marked as a duplicate of 176999 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
David, this bug is fixed in recenrt builds BTW. verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.