Closed Bug 70162 Opened 24 years ago Closed 24 years ago

"access denied" error messages should say what access is denied to

Categories

(Core :: Security: CAPS, defect)

x86
Windows 98
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 83131
mozilla1.0

People

(Reporter: jruderman, Assigned: security-bugs)

References

Details

Most of Mozilla's error messages are much more informative that IE's "object error" and "object does not support this property or method". As a result, I always debug my javascript code in Mozilla and then just hope that it works on IE. Mozilla's "access denied" error messages, however, doesn't tell me what access was denied to. 1. javascript:void(x=window.open("http://www.mozillazine.org")); 2. javascript:alert(x.document.images[0]); Current error message: 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>"] It would be nice if the message could specify which property I wasn't allowed to access (for example, "access to property x.document denied"). This would make it much easier to test security-related bugs and would also make it easier for webpage authors to figure out what's going on when Mozilla doesn't let them do something. By the way, why does the "access denied" message above have so much extranous information (error codes and the constant name NS_ERROR_DOM_PROP_ACCESS_DENIED)? Most javascript errors are much shorter: JavaScript error: line 0: document.foopy has no properties
Mass changing milestone to Moz1.0 - stuff targeted for late spring/early summer.
Target Milestone: --- → mozilla1.0
*** Bug 79581 has been marked as a duplicate of this bug. ***
Summary: "access denied" messages should say what access is denied to → "access denied" error messages should say what access is denied to
*** This bug has been marked as a duplicate of 83131 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Marking VERIFIED DUPLICATE.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.