Closed
Bug 207273
Opened 22 years ago
Closed 3 years ago
CAPS error messages misspell |window| as "Window"
Categories
(Core :: Security: CAPS, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: pschwartau, Unassigned)
Details
The |window| object is referred to as "Window" in CAPS error messages.
Since JS is case-sensitive, this should be spelled as "window" instead.
For an example, see bug 207271, where the user got this error message:
Error: uncaught exception: Permission denied to get property Window.check
I'm guessing that this message is generated from CAPS code; if not,
please reassign as necessary; thanks -
Comment 1•22 years ago
|
||
It's from CAPS all right, but Window refers to the Window class, not the window
object being accessed. The error message is reporting the class name. Do you
think it would make more sense to report the name of the object being accessed,
rather than its class? We could probably do this, but it would require more JS
engine tricks.
Status: NEW → ASSIGNED
Comment 2•21 years ago
|
||
Yes, report the object -- the property does not belong to the Window constructor
object, after all.
/be
brendan: i was hoping for hints
var _window=window;
_window.openDialog();
does anything even know the 'right' name for _window?
Assignee: security-bugs → caillon
Comment 4•21 years ago
|
||
So I think I need to use js_DecompileValueGenerator from the caps code which
generates the error. The only thing is I'm not quite sure how to use it just
yet. Still working on that... ;-)
Updated•17 years ago
|
Severity: normal → trivial
Updated•15 years ago
|
QA Contact: carosendahl → caps
Comment 5•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:ckerschb, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: caillon → nobody
Flags: needinfo?(ckerschb)
Comment 6•3 years ago
|
||
Searchfox tells me that this code is gone completely.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(ckerschb)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•