public-fxtf-archive@w3.org from May 2017 by date

Tuesday, 30 May 2017

• [fxtf-drafts] [compositing-1] Lighter compositing operator as a blend mode Franco Bugnano via GitHub
• Closed: [fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions Jihye Hong via GitHub

Monday, 29 May 2017

• Re: [fxtf-drafts] [geometry] Update the Changes section Simon Pieters via GitHub

Saturday, 27 May 2017

• [fxtf-drafts] Pull Request: [motion] Interaction of offset-position and shapes ewilligers via GitHub
• [fxtf-drafts] Pull Request: [motion] Create containing blocks ewilligers via GitHub

Friday, 26 May 2017

• Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? Tab Atkins Jr. via GitHub
• Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? Tab Atkins Jr. via GitHub

Thursday, 25 May 2017

• Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping Fredrik Söderqvist via GitHub
• Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping Taylor Hunt via GitHub
• [fxtf-drafts] [filter-effects] Why can't opacity() filter function every increase opacity Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] [filter-effects] For filter() image function, do you use intrinsic or extrinsic image dimensions Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] Pull Request: [motion] Specify offset-rotate 0deg in examples ewilligers via GitHub
• [fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] Pull Request: [motion] Remove Overview.html ewilligers via GitHub

Wednesday, 24 May 2017

• [fxtf-drafts] [filter-effects][compositing] What is "no-composite" blending? Amelia Bellamy-Royds via GitHub

Monday, 22 May 2017

• Re: [fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation Fredrik Söderqvist via GitHub
• Re: [fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow() Fredrik Söderqvist via GitHub
• [fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow() Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [geometry] Update the Changes section Simon Pieters via GitHub

Saturday, 20 May 2017

• Closed: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string) Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• [fxtf-drafts] [css-masking-1] Clarify how mask-mode & mask-composite behave with layered mask images Amelia Bellamy-Royds via GitHub

Friday, 19 May 2017

• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax L. David Baron via GitHub
• Re: [fxtf-drafts] [css-masking] Support <g> element is clipping paths Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path Roman Dvornov via GitHub
• Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] Pull Request: [geometry] Update the Changes section Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Update the Changes section Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Add a Historical section discussing old interfaces Simon Pieters via GitHub

Thursday, 18 May 2017

• Re: [fxtf-drafts] [css-masking] Percentage for clip-path should be n/a or clarification is needed Roman Dvornov via GitHub
• Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path Roman Dvornov via GitHub
• Re: [fxtf-drafts] [css-masking] Change percentage value of clip-path Amelia Bellamy-Royds via GitHub
• Closed: [fxtf-drafts] [css-masking] Change percentage value of clip-path Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] [css-masking] Change percentage value of clip-path Roman Dvornov via GitHub
• Re: [fxtf-drafts] [geometry] Add a Historical section discussing old interfaces Philip Jägenstedt via GitHub
• [fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Use [LegacyWindowAlias] for SVG* and WebKitCSSMatrix Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases Fredrik Söderqvist via GitHub
• Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Figure out if ClientRect/SVGPoint/SVGRect/SVGMatrix should be aliases Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Add a Historical section discussing old interfaces Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D Simon Pieters via GitHub

Wednesday, 17 May 2017

• Re: [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout Simon Pieters via GitHub
• [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend Paul LeBeau via GitHub
• [fxtf-drafts] Pull Request: [motion] Supply size in ray examples ewilligers via GitHub

Tuesday, 16 May 2017

• Re: [fxtf-drafts] [geometry] "interface DOMRect" should have alias for ClientRect Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Structured serialization should branch on is 2D Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Do not structured serialize -0 for m13 of a 2d matrix Simon Pieters via GitHub
• Closed: [fxtf-drafts] [motion] defining "computed distance" (aka "used distance") Jihye Hong via GitHub

Monday, 15 May 2017

• [fxtf-drafts] [geometry] Structured serialization should branch on is 2D Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Limit DOMMatrix's special stringifier to Window Simon Pieters via GitHub
• [fxtf-drafts] Allow nesting filters instead of using 'in', 'in2' and 'result' attributes Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Philip Jägenstedt via GitHub
• Re: [fxtf-drafts] [geometry] Treat 0 and -0 as equal throughout Simon Pieters via GitHub
• Re: [fxtf-drafts] [motion] none value considerations ewilligers via GitHub
• [fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Treat 0 and -0 as equal throughout Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [motion] Link to Motion Path's size definition ewilligers via GitHub
• [fxtf-drafts] Pull Request: [motion] computed distance now supports calc ewilligers via GitHub
• Re: [fxtf-drafts] [motion] Define 'sides' value for ray size. Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge? Jihye Hong via GitHub

Saturday, 13 May 2017

• [fxtf-drafts] Pull Request: [motion] Define 'sides' value for ray size. ewilligers via GitHub

Friday, 12 May 2017

• [fxtf-drafts] [css-masking] Percentage for clip-path should be n/a or clarification is needed Roman Dvornov via GitHub
• Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D Domenic Denicola via GitHub
• Re: [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D Domenic Denicola via GitHub
• [fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Add Privacy and Security Considerations Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Fernando Serboncini via GitHub
• Re: [fxtf-drafts] [geometry] Parse as CSS 'transform' instead of SVG transform="" Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform="" Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Parse as CSS 'transform' instead of SVG transform="" Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity Simon Pieters via GitHub
• [fxtf-drafts] [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D Simon Pieters via GitHub

Thursday, 11 May 2017

• [fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Limit DOMMatrix's special stringifier to Window Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] " The IDL in this specification is currently in ..." Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Define serialize/deserialize steps Simon Pieters via GitHub
• [fxtf-drafts] [geometry] "Rectangles have the following properties:" Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Philip Jägenstedt via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Chris Harrelson via GitHub

Wednesday, 10 May 2017

• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Fernando Serboncini via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Philip Jägenstedt via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Fernando Serboncini via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [geometry] Remove inline issue about experimental API shape Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Define serialize/deserialize steps Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Define serialize/deserialize steps Simon Pieters via GitHub
• Re: [fxtf-drafts] [paint] "outside stroke" and "group outline" Tobi Reif via GitHub
• [fxtf-drafts] [geometry] DOMMatrix stringifier in workers Simon Pieters via GitHub

Tuesday, 9 May 2017

• Re: [fxtf-drafts] offset-rotate syntax is resolved Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation Jihye Hong via GitHub
• [fxtf-drafts] [geometry] Clarify parsing of new DOMMatrix(string) Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations Simon Pieters via GitHub

Monday, 8 May 2017

• [fxtf-drafts] [geometry] " The IDL in this specification is currently in ..." Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations gogag1 via GitHub

Thursday, 4 May 2017

• Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] stringifier behavior doesn't seem to match implementations Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject] Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: [geometry] Annotate DOMMatrix's mutable methods with [NewObject] Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] Usage of 'none' in DOMMatrix transform lists Simon Pieters via GitHub

Wednesday, 3 May 2017

• Re: [fxtf-drafts] [geometry] DOMMatrix should not depend on the CSS parser Simon Pieters via GitHub
• Closed: [fxtf-drafts] [geometry] Avoid overloading constructor for DOMMatrix Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO… Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO… Anne van Kesteren via GitHub
• Re: [fxtf-drafts] [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO… Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: offset-rotate syntax is resolved ewilligers via GitHub

Last message date: Tuesday, 30 May 2017 12:58:10 UTC