Open
Bug 480245
Opened 16 years ago
Updated 2 years ago
evalInSandbox doesn't respect javascript.options.strict (Strict warnings do not appear for Greasemonkey scripts)
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: jruderman, Unassigned)
References
Details
1. Set javascript.options.strict to true 2. Create a Greasemonkey script with if(rq=3){} 3. Let it run. Expected: strict warnings * test for equality (==) mistyped as assignment (=) * assignment to undeclared variable rq Result: no strict warnings appear
Comment 1•16 years ago
|
||
Jesse, I think this is a dupe of bug 476967 -- can you verify with tomorrow's builds (or a recent hourly)?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•16 years ago
|
||
I was testing with a build that included that patch. This affects multiple strict warnings, not just "assignment to undeclared".
Reporter | ||
Updated•16 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 3•16 years ago
|
||
For what it's worth, that bug ended up not being "assignment to undeclared" specific (which is why I was so eager to call this a dupe).
Comment 4•16 years ago
|
||
This is because evalInSandbox doesn't respect javascript.options.strict.
Updated•16 years ago
|
Status: REOPENED → NEW
Updated•15 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Summary: Strict warnings do not appear for Greasemonkey scripts → evalInSandbox doesn't respect javascript.options.strict (Strict warnings do not appear for Greasemonkey scripts)
Comment 5•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•