User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; .NET CLR 1.0.3705) Build Identifier: Mozilla/5.0 a java script error is displayed while selecting Component drop down attributes Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: I close the pop up and I'm able to edit data over screen Expected Results: solve problem of java script error I'm using the 5.50.4807.2300 version of internet explorer
change assignation test
Not security sensitive, removing flag. Also, this seems like a Bugzilla bug, not Mozilla browser bug, since it is IE that complains on a Bugzilla page. Reassigning.
Assignee: general → myk
Component: Browser-General → Creating/Changing Bugs
Product: Browser → Bugzilla
QA Contact: general → mattyt-bugzilla
Summary: java script error on selecting Component drop down attributes → java script error in IE on selecting Component drop down attributes
Version: Trunk → unspecified
what is the error? Please attach a screenshot of the error message if it's too much to type.
Created attachment 136910 [details] Screenshot of the error message I get this error message when going to the mentioned URL with an IE 6.0 on WXP (version string 6.0.2800.1106.xpsp2.030422-1633) and clicking any of the values in the Component selection box. Every click produces a new error message.
Usual suspects rounded up. Gerv, is this a dupe?
dali: do you get the same problem on this page: http://landfill.bugzilla.org/bugzilla-tip//enter_bug.cgi?product=Spider%20Secretions&format=guided Gerv
I was able to confirm this bug on 2003-12-05 at bmo as said in my comment #5. But today this no longer happens, so something must have fixed since then. I'll look into this.
I could reproduce this on a 2003-03-31 checkout but no longer with a 2003-04-02 checkout. So looks like this bug was fixed by a checkin in bug 192121 and bmo just hadn't picked it up yet. *** This bug has been marked as a duplicate of 192121 ***
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE
Version: unspecified → 2.17.3
You need to log in before you can comment on or make changes to this bug.