Open Bug 1543514 Opened 5 years ago Updated 2 years ago

Enable direct UTF-8 compilation of all web-visible scripts in release

Categories

(Core :: DOM: Core & HTML, enhancement, P3)

enhancement

Tracking

()

Tracking Status
firefox68 --- affected

People

(Reporter: Waldo, Unassigned)

References

(Blocks 1 open bug)

Details

After direct UTF-8 compilation has been turned on for all types of web-visible scripts in nightly/beta, we should turn it on for release.

There's a fair chance we'll enable direct UTF-8 compilation in nightly/beta on a call-by-call basis -- so workers would get opted in at one moment, <script> elements at another, probably controlled by separate temporary prefs.

But to ship in release, we'll want all these to proceed in lockstep: one release should for all callers inflate to UTF-16 as we do now, then the next should for all callers directly compile UTF-8. If there are inconsistencies, much better for behavior to be the same for every web script, than for there to be subtle differences depending on which exact kind of script it happened to be loaded as.

Depends on: 1543517
Type: defect → enhancement
Priority: -- → P2

The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P2'.
:hsinyi, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: jwalden → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(htsai)
Flags: needinfo?(htsai)
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.