stylo: Make sure we don't unintentionally ship new CSS features when we ship stylo

RESOLVED WORKSFORME

Status

()

P5
normal
RESOLVED WORKSFORME
2 years ago
18 days ago

People

(Reporter: bobbyholley, Unassigned)

Tracking

unspecified
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox57 wontfix)

Details

See bug 1337068 comment 3.

In general, Gecko's CSS engine is much more feature-complete than Servo's, but we have no reason to believe it's a strict super-set. We need to audit before shipping.
Priority: -- → P3
No longer depends on: 1361044
No longer depends on: 1362333
Blocks: 1374034
No longer blocks: 1243581
Depends on: 1377311
Priority: P3 → --
Priority: -- → P5
Depends on: 1363971
Depends on: 1374902
I don't think stylo still supports unprefixed :read-only and :read-write now.
No longer depends on: 312971
Depends on: 1386871
Depends on: 1389187
No longer depends on: 1350857
No longer depends on: 1350739

Comment 2

2 years ago
Adding dev-doc-needed keyword and ni'ing teoli (who works on CSS and DOM docs IIRC) to keep him informed.
Is there or will these be a way to know the complete list of features stylo has implemented that Gecko didn't have?
Flags: needinfo?(jypenator)
Keywords: dev-doc-needed
Flags: needinfo?(jypenator) → needinfo?(cmills)
As far as I was aware, there is very little stylo implements that Gecko didn't have at all. I've already been in discussion with engineering about differences between Gecko and Stylo, and we've started recording them like this:

https://developer.mozilla.org/en-US/Firefox/Releases/57#Quantum_CSS_notes

I'd like to be involved in the audit mentioned in this bug, so I can document any differences as necessary.
Flags: needinfo?(cmills)
status-firefox57=wontfix unless someone thinks this bug should block 57
status-firefox57: --- → wontfix
Depends on: 1421645

Comment 5

4 months ago
All the dependent bugs are closed
Is there something else to do here?
Nope
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.