... once we're confident there'll be no more churn in the spec.
Till, can you provide a better description into what this is supposed to be and why firefox 60 (P1) is flagged as affected?
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.
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.