Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 40017 - Error "Line 63, null is null or not an object" in IE6 when attempt to set Component during guided input of new bug
Summary: Error "Line 63, null is null or not an object" in IE6 when attempt to set Com...
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Hardware: x86 All
: High trivial (vote)
Assignee: Benjamin Coles
URL: http://bugs.gentoo.org/enter_bug.cgi?...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-31 15:15 UTC by Joe Millenbach
Modified: 2011-10-30 23:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Millenbach 2004-01-31 15:15:41 UTC 
Every time I go to enter a bug the second step has (so far) had one item listed for Component.  This has been when entering a bug for LiveCD or for Gentoo Linux Bugzilla.  When I click on that single item I get a pop-up with the error listed in the title (Line 63...).  I realize this is a bug system for a Linux based OS, but if possible it'd be nice not to blow chunks on other browsers too :).  As far as I can tell it doesn't affect functionality (I think the bugs I've added are ok), but it is scary for the first time user of your system.

Reproducible: Always
Steps to Reproduce:
1. View above URL
2. Select "General Bugs" from the component list


Actual Results:  
Get error pop-up (and item is selected)

Expected Results:  
No error/warning...
Comment 1 Benjamin Coles 2004-02-09 11:37:35 UTC 
Can you tell me which version this is happening because I have no problem on my end.
Comment 2 Joe Millenbach 2004-02-11 22:27:44 UTC 
128bit IE v6.0.3790.0 (Windows 2003 Server with current patches)
Comment 3 Benjamin Coles 2004-03-04 13:54:15 UTC 
This happens in no version of MSIE outside of windows 2003 server... I'm not sure what you can do but it sounds like a MSIE problem... gonna close this because I can't fix it.