Amelia Bellamy-Royds via GitHub
- Re: [fxtf-drafts] [filter-effects] SVGFEConvolveMatrixElement misses property for preserveAlpha attribute
- Closed: [fxtf-drafts] [filter-effects] SVGFEConvolveMatrixElement misses property for preserveAlpha attribute
- Re: [fxtf-drafts] Luminance masking is slower than alpha masking
- Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties
- Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties
- Re: [fxtf-drafts] Luminance masking is slower than alpha masking
- [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties
- Re: [fxtf-drafts] [geometry] Gloss "viewport"
- Re: [fxtf-drafts] [css-masking] make the behavior of an invalid mask be consistent with clip-path and filter
- Re: [fxtf-drafts] [transforms-2] Dubious definition of perspective(0)
Anne van Kesteren via GitHub
- Re: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix
- Re: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix
Anthony Ramine via GitHub
Boris Zbarsky via GitHub
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
Brian Birtles via GitHub
Chris Harrelson via GitHub
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
Chris Rebert via GitHub
- Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?
- [fxtf-drafts] [geometry] Cross-references within rectangle properties
- [fxtf-drafts] [geometry] Gloss "viewport"
- [fxtf-drafts] [geometry] "The type of box is specified..."
CSS Meeting Bot via GitHub
- Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties
- Re: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation
- Re: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?
- Re: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
Debarshi Ray via GitHub
Emilio Cobos Álvarez via GitHub
fantasai via GitHub
- Re: [fxtf-drafts] [css-transforms-1] Call out scrolling offsets explicitly in accumulated matrix computation
- Re: [fxtf-drafts] [css-paint-1] Specify the impact of strokes on overflow
- Re: [fxtf-drafts] [css-paint-1] Specify the impact of strokes on overflow
- Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties
- Re: [fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions
gogag1 via GitHub
Jeff Muizelaar via GitHub
- Re: [fxtf-drafts] Luminance masking is slower than alpha masking
- [fxtf-drafts] Luminance masking is slower than alpha masking
Jihye Hong via GitHub
- Re: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?
- Closed: [fxtf-drafts] [motion] contain should modify percentages, not path
- Closed: [fxtf-drafts] [motion] defining "computed distance" (aka "used distance")
L. David Baron via GitHub
Markus Stange via GitHub
- Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties
- Re: [fxtf-drafts] Luminance masking is slower than alpha masking
Philip Jägenstedt via GitHub
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations
Sebastian Zartner via GitHub
- Re: [fxtf-drafts] [filter-effects] SVGFEConvolveMatrixElement misses property for preserveAlpha attribute
- [fxtf-drafts] [filter-effects] List feMergeNode in the TOC
- [fxtf-drafts] [filter-effects] SVGFEConvolveMatrixElement misses property for preserveAlpha attribute
shans via GitHub
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties
- Re: [fxtf-drafts] [motion] defining "computed distance" (aka "used distance")
Simon Pieters via GitHub
- Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO…
- Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO…
- Re: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix
- [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
- Re: [fxtf-drafts] Consider using Typed Arrays for matrices and static transform operations
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser