css-houdini-drafts
css-houdini-drafts copied to clipboard
w3c
Mirror of https://hg.css-houdini.org/drafts
I'm writing the spec for color values right now, and the overall structure is straightforward: a CSSColorValue superclass, and subclasses for each type of color function. I'm struggling a bit...
Currently, the Typed OM is not meant to be author-extensible. The style-setting functions only accept Typed OM classes, and tho theoretically you could subclass one of them, there's nothing defined...
Given that the entire set of numeric types is represented by a single `CSSUnitValue` class, I was surprised to see the class hierarchy of `CSSColorValue`. Is this complexity and rigidity...
The serialization of CSSUnparsedValue is [specified](https://drafts.css-houdini.org/css-typed-om-1/#unparsedvalue-serialization) as: > For each `item` in `this`’s `[[tokens]]` internal slot: > If `item` is a `USVString`, append it to `s`. So `CSSUnparsedValue(['1', 'px'])` will...
This sounds like a pretty good fit for the current API that we have exposed. E.g. you could imaging something like: ```js const node = new LayoutChild('lots of text'); const...
Per https://drafts.css-houdini.org/css-paint-api/#2d-rendering-context there shouldn't be a `filter` attributes on `PaintRenderingContext2D`, because there's no `PaintRenderingContext2D includes CanvasFilters` statements or similar that would make it so. But Chromium does have a `filters`...
[Original question](https://stackoverflow.com/questions/53797901/how-to-manipulate-pixel-data-of-css-paintworklet-context) PaintRenderingContext2D does not have `putImageData` and an `ImageData` interface. If `PaintWorklet` allowed pixel manipulation with `CanvasRenderingContext2D`, it would be possible to create beautiful placeholders (e.g. using BlurHash algorithm)....
Many useful effects running inside animation worklet may need to know about specific values from main thread, e.g., size of window or bounding client rects of various objects. We allow...
Added repaint related detail based on the discussion from [issue #741](https://github.com/w3c/css-houdini-drafts/issues/741).
This adds a note that user-agents must introduce some non-determinism into the selection process for a paint worklet global scope. This came up in blinks intent-to-ship thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Jex3idOld48 Issue: #471
