Closed Bug 185153 Opened 23 years ago Closed 23 years ago

NS_ERROR_INVALID_POINTER in DHTML menu code

Categories

(Core :: DOM: Core & HTML, defect, P2)

x86
Windows XP
defect

Tracking

()

RESOLVED FIXED
mozilla1.3alpha

People

(Reporter: zevious, Assigned: peterv)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021210 Phoenix/0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021210 Phoenix/0.5 http://www.dhtmlcentral.com/projects/coolmenus/examples/menu3.html When I visit the above site, I get the following in the Javascript Console and no menus. Using Phoenix from 12/10/02 works fine. Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIDOMNSHTMLElement.innerHTML]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: http://www.dhtmlcentral.com/projects/coolmenus/examples/coolmenus4.js :: cm_divCreate :: line 102" data: no] I didn't see anything off hand in Bugzillz regarding this. Any ideas what might have been checked in to break this? This is a blocker for me as I use this menu for a work project.. Reproducible: Always Steps to Reproduce: 1. Open the url 2. Witness error in javascript console 3. Witness missing menu Actual Results: no menu, error in javascript Expected Results: menu, no error This was working in 121002 but not in today's..
Not sure of the correct component to investigate this, but it's not JavaScript Engine. JS Engine contains no browser or DOM objects, just abstract ones like String(), Number(), Date(), RegExp(), etc. Reassigning to DOM Level 0 for further triage -
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
Fallout from bug 183999. I backed out the error.
Assignee: jst → peterv
Severity: blocker → major
Status: UNCONFIRMED → NEW
Component: DOM Level 0 → DOM Traversal-Range
Ever confirmed: true
Priority: -- → P2
Target Milestone: --- → mozilla1.3alpha
This looks fixed now.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Component: DOM: Traversal-Range → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.