Closed
Bug 1342440
Opened 8 years ago
Closed 8 years ago
wasm: keep wasm disabled in esr52
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox52 | --- | unaffected |
| firefox-esr52 | 52+ | fixed |
| firefox53 | --- | unaffected |
| firefox54 | --- | unaffected |
People
(Reporter: luke, Assigned: luke)
Details
In bug 1342060, wasm was also enabled for esr52 to match release 52. I think it would actually be better to keep it off in esr52. One reason is that there are a few spec fixes (e.g., one piece of bug 1338002) that didn't make 52 because it was fine for the fix to come in the next release, but waiting a whole esr cycle could bake in the spec differences. So, my request is to back out the two csets in bug 1342060 comment 22.
Updated•8 years ago
|
status-firefox-esr52:
--- → affected
tracking-firefox-esr52:
--- → 52+
Comment 1•8 years ago
|
||
a+ from me for the backout in esr52.
Comment 2•8 years ago
|
||
| bugherder uplift | ||
Updated•8 years ago
|
Assignee: nobody → luke
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox52:
--- → unaffected
status-firefox53:
--- → unaffected
status-firefox54:
--- → unaffected
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•