[fxtf-drafts] [compositing-1] Lighter compositing operator as a blend mode
Closed: [fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions
[fxtf-drafts] Pull Request: [motion] Interaction of offset-position and shapes
[fxtf-drafts] Pull Request: [motion] Create containing blocks
[fxtf-drafts] [filter-effects] Why can't opacity() filter function every increase opacity
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity?
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity?
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity?
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity?
[fxtf-drafts] [filter-effects] For filter() image function, do you use intrinsic or extrinsic image dimensions
[fxtf-drafts] Pull Request: [motion] Specify offset-rotate 0deg in examples
[fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default
[fxtf-drafts] Pull Request: [motion] Remove Overview.html
[fxtf-drafts] [filter-effects][compositing] What is "no-composite" blending?
Re: [fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation
[fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow()
[fxtf-drafts] [css-masking-1] Clarify how mask-mode & mask-composite behave with layered mask images
Re: [fxtf-drafts] [css-masking] Support <g> element is clipping paths
[fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping
- Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping
- Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping
- Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping
[fxtf-drafts] Pull Request: [geometry] Update the Changes section
[fxtf-drafts] Pull Request: [geometry] Update the Changes section
- Re: [fxtf-drafts] [geometry] Update the Changes section
- Re: [fxtf-drafts] [geometry] Update the Changes section
Closed: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases
[fxtf-drafts] [css-masking] Change percentage value of clip-path
- Closed: [fxtf-drafts] [css-masking] Change percentage value of clip-path
- Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path
- Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path
- Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path
- Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path
[fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix
[fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix
Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases
- Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases
- Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases
- Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases
[fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces
[fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces
- Re: [fxtf-drafts] [geometry] Add a Historical section discussing old interfaces
- Re: [fxtf-drafts] [geometry] Add a Historical section discussing old interfaces
[fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend
[fxtf-drafts] Pull Request: [motion] Supply size in ray examples
Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect
- Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect
- Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect
Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations
[fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix
[fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix
Closed: [fxtf-drafts] [motion] defining "computed distance" (aka "used distance")
[fxtf-drafts] [geometry] Structured serialization should branch on is 2D
- Re: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D
- Closed: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D
[fxtf-drafts] Allow nesting filters instead of using 'in', 'in2' and 'result' attributes
Re: [fxtf-drafts] [motion] none value considerations
[fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout
[fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout
- Re: [fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout
- Re: [fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout
[fxtf-drafts] Pull Request: [motion] Link to Motion Path's size definition
[fxtf-drafts] Pull Request: [motion] computed distance now supports calc
Closed: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?
[fxtf-drafts] Pull Request: [motion] Define 'sides' value for ray size.
[fxtf-drafts] [css-masking] Percentage for clip-path should be n/a or clarification is needed
[fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations
[fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations
[fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform=""
[fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform=""
[fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D
- Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D
- Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D
- Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D
- Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D
- Closed: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D
[fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window
[fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window
[fxtf-drafts] [geometry] "Rectangles have the following properties:"
[fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
- Closed: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax
Re: [fxtf-drafts] [geometry] Remove inline issue about experimental API shape
[fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity
[fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity
[fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps
[fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps
- Re: [fxtf-drafts] [geometry] Define serialize/deserialize steps
- Re: [fxtf-drafts] [geometry] Define serialize/deserialize steps
Re: [fxtf-drafts] [paint] "outside stroke" and "group outline"
[fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
- Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers
Closed: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation
[fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string)
Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations
[fxtf-drafts] [geometry] " The IDL in this specification is currently in ..."
Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations
- Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations
[fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject]
[fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject]
Re: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists
Closed: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
Closed: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists
Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser
Closed: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix
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] Use union instead of overload for DOMMatrix/DOMMatrixReadO…