[css-properties-values-api] Let css-properties-values-api ride the trains
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: zrhoffman, Assigned: emilio)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
Once css-properties-values-api is in a usable state, we should enable it by default.
| Updated•1 year ago
           | 
| Reporter | ||
| Comment 1•1 year ago
           | ||
Depending on bug 1856522 explicitly, since bug 1856524 was resolved without having completed bug 1856522.
| Reporter | ||
| Updated•1 year ago
           | 
| Assignee | ||
| Comment 3•1 year ago
           | ||
Our implementation is in a reasonably good state. Only test failures
are:
- Long-standing bug 1533327.
- A test / spec issue that is covered by D211871 (the animation works
 correctly).
- TypedOM
So I don't see a reason to keep gating this to nightly-only.
| Updated•1 year ago
           | 
| Reporter | ||
| Comment 5•1 year ago
          • | ||
Release Note Request (optional, but appreciated)
[Why is this notable]: Registered custom properties in animations and transitions are smoothly interpolated, and registered custom properties are type-safe, can have default values, and can be specified to or not to inherit, regardless of where they are used.
[Affects Firefox for Android]: Yes
[Suggested wording]: Support for CSS @property / properties-and-values API is enabled by default.
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/API/CSS_Properties_and_Values_API
| Comment 6•1 year ago
           | ||
| bugherder | ||
| Comment 8•1 year ago
           | ||
Description
•