Enable numeric separators in release builds

NEW
Unassigned

Status

()

enhancement
P3
normal
2 years ago
7 days ago

People

(Reporter: till, Unassigned)

Tracking

(Blocks 1 bug, {dev-doc-needed, parity-chrome})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox60 affected)

Details

()

... once we're confident there'll be no more churn in the spec.
Blocks: es-proposals-stage-3
No longer blocks: 1435813
Till, can you provide a better description into what this is supposed to be and why firefox 60 (P1) is flagged as affected?
Flags: needinfo?(till)
Priority: -- → P1
FF60 being affected is simply the default for a new bug. It's also true in that FF60 doesn't have this enabled, but, once the blocking bug is fixed, could. That doesn't mean it should be P1 at all.

As for the description, I added a link to the spec proposal as the URL, I hope that's sufficient.
Flags: needinfo?(till)
Priority: P1 → P3

Is the fix in bug 1421400 Nightly-only?

(In reply to j.j. from comment #3)

Is the fix in bug 1421400 Nightly-only?

Answering myself: Yes, seems so.
This should land in Beta 68 for Chrome compat and for 68 ESR and Fennec.

Chrome 75 ships Numeric Separators in two weeks
https://www.chromestatus.com/feature/5829906369871872

Flags: needinfo?(till)

(In reply to j.j. from comment #4)

This should land in Beta 68 for Chrome compat and for 68 ESR and Fennec.

I don't think numeric separators will be used in code shipping to browsers quickly enough that we'd have to worry about Chrome compat here. Even for the ESR I really don't think that this needs to be uplifted.

What would make sense to me is to let it ride the trains either this or the next release—it seems sufficiently low-risk that we don't have to wait very long.

Flags: needinfo?(till)
You need to log in before you can comment on or make changes to this bug.