"import window.null" changes during round-trip

RESOLVED WORKSFORME

Status

()

Core
JavaScript Engine
--
minor
RESOLVED WORKSFORME
12 years ago
10 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

(Blocks: 1 bug, {testcase})

Trunk
testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
> function() { import window.null }
function () { import window['null']; }

> function () { import window['null']; }
function () { import window["null"]; }
Jesse, I'd like to not worry about this for a while.  It's correct, just a bother for you to avoid a false positive, right?

/be
(Reporter)

Comment 2

12 years ago
Ok.  I've tagged the import/export things in the fuzzer with "mismatchok", so this bug and other mismatches with import/export won't trigger an alert.  The fuzzer can still test for completely bogus decompilation, crashes when executing, etc.

Comment 3

12 years ago
This is fixed by the patch for bug 355736, too:

js> "" + function f() { import window.null }
function f() {
    import window.null;
}
Depends on: 355736
OS: Mac OS X → All
Hardware: Macintosh → All
(Reporter)

Comment 4

10 years ago
This bug is irrelevant now that import/export have been removed (bug 447713).
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.