Closed
Bug 59570
Opened 24 years ago
Closed 24 years ago
Access Denied error message not printed correctly
Categories
(Core :: Security: CAPS, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: jruderman, Assigned: security-bugs)
Details
"Access denied" error messages, except for XPConnect errors, aren't being
printed correctly in today's build. I noticed this while testing bug 56053.
Steps to reproduce:
1. Run Mozilla with the -console option.
2. Load a website.
3. Type javascript:void(window.open("http://www.mozilla.org/"));
into the browser window.
4. Type javascript:document.write(opener.location.href);
into the window that opened.
Results (happen in trunk 2000110804)
JavaScript error:
line 0:
JavaScript error:
line 0: uncaught exception: null <-- bad
Expected results (happen in trunk 2000110508)
JavaScript error:
line 0:
JavaScript error:
line 0: uncaught exception: [Exception... "Access to property denied" code: "1
010" nsresult: "0x805303f2 (NS_ERROR_DOM_PROP_ACCESS_DENIED)" location: "<unkno
wn>"]
Assignee | ||
Comment 2•24 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 3•24 years ago
|
||
Marking VERIFIED FIXED on:
- MacOS9 2001-01-09-08-T Commercial
- LinuxRH62 2001-01-09-08-T Commercial
- Win98 2001-01-09-08-T Commercial
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•