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)

defect

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.

Severity: -- → S3
Assignee: nobody → zsun
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
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: