Closed
Bug 1862903
Opened 1 year ago
Closed 1 year ago
Registering a property should not affect cascade/parsing
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
121 Branch
Tracking | Status | |
---|---|---|
firefox121 | --- | fixed |
People
(Reporter: fredw, Assigned: zsun)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This is tested by https://wpt.fyi/results/css/css-properties-values-api/property-cascade.html
It used to fail because we don't implement computedStyleMap()
but that was worked around by https://github.com/web-platform-tests/interop/issues/588
Now it seems to be failing because we don't respect what is described in https://drafts.css-houdini.org/css-properties-values-api-1/#the-registerproperty-function
"Registering a custom property must not affect the cascade in any way."
I'm not sure I really understand this now, but see also bug 1858362 which was forcing a re-cascade.
Updated•1 year ago
|
Severity: -- → S3
Updated•1 year ago
|
Attachment #9363312 -
Attachment description: WIP: Bug 1862903 - Registering a property should not affect cascade/parsing. → Bug 1862903 - Registering a property should not affect cascade/parsing. r=zrhoffman,fredw
Pushed by zsun@igalia.com:
https://hg.mozilla.org/integration/autoland/rev/de171a9a6cf2
Registering a property should not affect cascade/parsing. r=zrhoffman,emilio
Comment 3•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Comment 4•1 year ago
|
||
bugherder |
You need to log in
before you can comment on or make changes to this bug.
Description
•