Gecko treat 'none' as a predefined counter style, while stylo treat it as a separate keyword value

NEW
Unassigned

Status

()

Core
CSS Parsing and Computation
P5
normal
a year ago
6 months ago

People

(Reporter: xidorn, Unassigned)

Tracking

(Blocks: 1 bug, {dev-doc-complete})

Trunk
dev-doc-complete
Points:
---

Firefox Tracking Flags

(firefox57 wontfix, firefox58 wontfix, firefox59 ?)

Details

(Whiteboard: [stylo])

(Reporter)

Description

a year ago
This is a recent spec change from w3c/csswg-drafts#1295.

The only effective difference as far as I can see is that "system" and "fallback" descriptors of @counter-style rule would reject 'none' as a valid value, which is currently valid in Gecko.

Also, there is some inconsistency from this currently, that the counter style rule object is still implemented in Gecko side, which means it still uses the grammar from Gecko. So although the parsing (implemented in Servo) would reject 'none' in those cases, if you set it via CSSOM, that would still be accepted.

This inconsistency would be fixed in the future after we drop the current style system.

This shouldn't cause any real issue, but it is still a behavior change we may want to track.
Whiteboard: [stylo]

Updated

a year ago
Priority: -- → P3
(Reporter)

Updated

a year ago
Priority: P3 → P5
Marking as part of documentation plan for intentional stylo differences
Keywords: dev-doc-needed
Documented: 

https://developer.mozilla.org/en-US/docs/Web/CSS/@counter-style#Quantum_CSS_notes

Is this description OK?
Keywords: dev-doc-needed → dev-doc-complete
(Reporter)

Comment 3

10 months ago
That description is opposite. Gecko allows "none" in those places, while Stylo doesn't. The spec was updated recently to reflect Stylo's behavior.
(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #3)
> That description is opposite. Gecko allows "none" in those places, while
> Stylo doesn't. The spec was updated recently to reflect Stylo's behavior.

Thanks for catching this; I've fixed it now.

Updated

9 months ago
status-firefox57: --- → wontfix
status-firefox58: --- → fix-optional
You need to log in before you can comment on or make changes to this bug.