Amelia Bellamy-Royds via GitHub
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? (Friday, 26 May)
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? (Friday, 26 May)
- Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping (Thursday, 25 May)
- [fxtf-drafts] [filter-effects] Why can't opacity() filter function every increase opacity (Thursday, 25 May)
- [fxtf-drafts] [filter-effects] For filter() image function, do you use intrinsic or extrinsic image dimensions (Thursday, 25 May)
- [fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default (Thursday, 25 May)
- [fxtf-drafts] [filter-effects][compositing] What is "no-composite" blending? (Wednesday, 24 May)
- Re: [fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation (Monday, 22 May)
- [fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow() (Monday, 22 May)
- [fxtf-drafts] [css-masking-1] Clarify how mask-mode & mask-composite behave with layered mask images (Saturday, 20 May)
- Re: [fxtf-drafts] [css-masking] Support <g> element is clipping paths (Friday, 19 May)
- [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping (Friday, 19 May)
- Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path (Friday, 19 May)
- Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path (Thursday, 18 May)
- Closed: [fxtf-drafts] [css-masking] Change percentage value of clip-path (Thursday, 18 May)
- Re: [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend (Wednesday, 17 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Wednesday, 10 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (Wednesday, 10 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (Wednesday, 10 May)
Anne van Kesteren via GitHub
Chris Harrelson via GitHub
Domenic Denicola via GitHub
ewilligers via GitHub
- [fxtf-drafts] Pull Request: [motion] Interaction of offset-position and shapes (Saturday, 27 May)
- [fxtf-drafts] Pull Request: [motion] Create containing blocks (Saturday, 27 May)
- [fxtf-drafts] Pull Request: [motion] Specify offset-rotate 0deg in examples (Thursday, 25 May)
- [fxtf-drafts] Pull Request: [motion] Remove Overview.html (Thursday, 25 May)
- [fxtf-drafts] Pull Request: [motion] Supply size in ray examples (Wednesday, 17 May)
- Re: [fxtf-drafts] [motion] none value considerations (Monday, 15 May)
- [fxtf-drafts] Pull Request: [motion] Link to Motion Path's size definition (Monday, 15 May)
- [fxtf-drafts] Pull Request: [motion] computed distance now supports calc (Monday, 15 May)
- [fxtf-drafts] Pull Request: [motion] Define 'sides' value for ray size. (Saturday, 13 May)
- [fxtf-drafts] Pull Request: offset-rotate syntax is resolved (Wednesday, 3 May)
Fernando Serboncini via GitHub
Franco Bugnano via GitHub
Fredrik Söderqvist via GitHub
gogag1 via GitHub
Jihye Hong via GitHub
L. David Baron via GitHub
Paul LeBeau via GitHub
Philip Jägenstedt via GitHub
Roman Dvornov via GitHub
Sebastian Zartner via GitHub
Simon Pieters via GitHub
- Re: [fxtf-drafts] [geometry] Update the Changes section (Monday, 29 May)
- Re: [fxtf-drafts] [geometry] Update the Changes section (Monday, 22 May)
- Closed: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Saturday, 20 May)
- Closed: [fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string) (Saturday, 20 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Saturday, 20 May)
- [fxtf-drafts] Pull Request: [geometry] Update the Changes section (Friday, 19 May)
- Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases (Friday, 19 May)
- Closed: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D (Friday, 19 May)
- Closed: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases (Friday, 19 May)
- Re: [fxtf-drafts] [geometry] Add a Historical section discussing old interfaces (Friday, 19 May)
- [fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix (Thursday, 18 May)
- Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases (Thursday, 18 May)
- Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases (Thursday, 18 May)
- [fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces (Thursday, 18 May)
- Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect (Thursday, 18 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 18 May)
- Closed: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D (Thursday, 18 May)
- Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect (Wednesday, 17 May)
- Re: [fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout (Wednesday, 17 May)
- Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect (Tuesday, 16 May)
- Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (Tuesday, 16 May)
- Re: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D (Tuesday, 16 May)
- [fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix (Tuesday, 16 May)
- [fxtf-drafts] [geometry] Structured serialization should branch on is 2D (Monday, 15 May)
- Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers (Monday, 15 May)
- Re: [fxtf-drafts] [geometry] Limit DOMMatrix's special stringifier to Window (Monday, 15 May)
- Re: [fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout (Monday, 15 May)
- [fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout (Monday, 15 May)
- Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D (Monday, 15 May)
- Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D (Monday, 15 May)
- [fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations (Friday, 12 May)
- Re: [fxtf-drafts] [geometry] Parse as CSS 'transform' instead of SVG transform="" (Friday, 12 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Friday, 12 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Friday, 12 May)
- [fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform="" (Friday, 12 May)
- Re: [fxtf-drafts] [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity (Friday, 12 May)
- [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D (Friday, 12 May)
- [fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window (Thursday, 11 May)
- [fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 11 May)
- Closed: [fxtf-drafts] [geometry] " The IDL in this specification is currently in ..." (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] Define serialize/deserialize steps (Thursday, 11 May)
- [fxtf-drafts] [geometry] "Rectangles have the following properties:" (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (Thursday, 11 May)
- Re: [fxtf-drafts] [geometry] Remove inline issue about experimental API shape (Wednesday, 10 May)
- Re: [fxtf-drafts] [geometry] Define serialize/deserialize steps (Wednesday, 10 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (Wednesday, 10 May)
- [fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity (Wednesday, 10 May)
- [fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps (Wednesday, 10 May)
- [fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps (Wednesday, 10 May)
- [fxtf-drafts] [geometry] DOMMatrix stringifier in workers (Wednesday, 10 May)
- [fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string) (Tuesday, 9 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (Tuesday, 9 May)
- [fxtf-drafts] [geometry] " The IDL in this specification is currently in ..." (Monday, 8 May)
- Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations (Thursday, 4 May)
- Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations (Thursday, 4 May)
- [fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject] (Thursday, 4 May)
- Re: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists (Thursday, 4 May)
- Closed: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser (Thursday, 4 May)
- Closed: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists (Thursday, 4 May)
- Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser (Wednesday, 3 May)
- Closed: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix (Wednesday, 3 May)
- Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO… (Wednesday, 3 May)
- Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO… (Wednesday, 3 May)
Tab Atkins Jr. via GitHub
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? (Friday, 26 May)
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? (Friday, 26 May)
- [fxtf-drafts] Pull Request: [geometry] Update the Changes section (Friday, 19 May)
- [fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix (Thursday, 18 May)
- [fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces (Thursday, 18 May)
- [fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix (Tuesday, 16 May)
- [fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout (Monday, 15 May)
- [fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations (Friday, 12 May)
- [fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform="" (Friday, 12 May)
- [fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity (Wednesday, 10 May)
- [fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject] (Thursday, 4 May)
Taylor Hunt via GitHub
Tobi Reif via GitHub
Last message date: Tuesday, 30 May 2017 12:58:10 UTC