wasm: keep wasm disabled in esr52

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
6 months ago
6 months ago

People

(Reporter: luke, Assigned: luke)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(firefox52 unaffected, firefox-esr5252+ fixed, firefox53 unaffected, firefox54 unaffected)

Details

(Assignee)

Description

6 months ago
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.
status-firefox-esr52: --- → affected
tracking-firefox-esr52: --- → 52+
a+ from me for the backout in esr52.

Comment 2

6 months ago
bugherderuplift
https://hg.mozilla.org/releases/mozilla-esr52/rev/e07850f191a0
status-firefox-esr52: affected → fixed
Assignee: nobody → luke
Status: NEW → RESOLVED
Last Resolved: 6 months 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.