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

Friday, 30 June 2017

• Re: [fxtf-drafts] Revert "Kill DOMRectList" Philip Jägenstedt via GitHub

Thursday, 29 June 2017

• Re: [fxtf-drafts] Luminance masking is slower than alpha masking Amelia Bellamy-Royds via GitHub

Wednesday, 28 June 2017

• Re: [fxtf-drafts] [filter-effects] Luminance coefficients are slightly changed from SVG 1.1 Chris Lilley via GitHub
• Re: [fxtf-drafts] [filter-effects] Luminance coefficients are slightly changed from SVG 1.1 Amelia Bellamy-Royds via GitHub
• Closed: [fxtf-drafts] [motion] Inconsistency in offset-path contain Jihye Hong via GitHub
• Re: [fxtf-drafts] [filter-effects] Luminance coefficients are slightly changed from SVG 1.1 Chris Lilley via GitHub
• [fxtf-drafts] [filter-effects] Luminance coefficients are slightly changed from SVG 1.1 Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [motion] Inconsistency in offset-path contain ewilligers via GitHub
• [fxtf-drafts] Pull Request: [motion] Clarify meaning of contain ewilligers via GitHub

Tuesday, 27 June 2017

• [fxtf-drafts] [filter-effects] drop-shadow() null value for interpolation is incorrect Amelia Bellamy-Royds via GitHub

Monday, 26 June 2017

• Closed: [fxtf-drafts] [motion] Interaction with positioning Jihye Hong via GitHub
• Closed: [fxtf-drafts] [css-motion] description of offset-position should be clearer Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] default reference box for basic shape Jihye Hong via GitHub

Sunday, 25 June 2017

• [fxtf-drafts] Pull Request: Simplify description of initial direction ewilligers via GitHub
• [fxtf-drafts] Pull Request: Clarify motion path and position interaction ewilligers via GitHub
• Re: [fxtf-drafts] [motion] Interaction with positioning ewilligers via GitHub

Friday, 23 June 2017

• [fxtf-drafts] Pull Request: [motion] Use border-box as default reference box ewilligers via GitHub
• [fxtf-drafts] [geometry] WebIDL serializer has been deprecated in favor of toJSON operation Tobie Langel via GitHub

Thursday, 22 June 2017

• Re: [fxtf-drafts] [geometry] JSON serialization of a DOMRectList Tobie Langel via GitHub
• [fxtf-drafts] [geometry] JSON serialization of a DOMRectList Simon Pieters via GitHub

Wednesday, 21 June 2017

• Re: [fxtf-drafts] [motion] Add Eric Willigers to Motion Path editors Jihye Hong via GitHub
• [fxtf-drafts] Pull Request: [motion] Add Eric Willigers to Motion Path editors ewilligers via GitHub

Tuesday, 20 June 2017

• Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [geometry] Method to make a DOMPoint homogeneous fuchsia via GitHub
• Re: [fxtf-drafts] [css-motion] description of offset-position should be clearer ewilligers via GitHub

Monday, 19 June 2017

• Re: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [motion] Define offset-rotate at sharp path segment boundaries Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] Define offset-rotate at sharp path segment boundaries Jihye Hong via GitHub
• Re: [fxtf-drafts] [motion] Offset-rotate and zero length paths Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] Offset-rotate and zero length paths Jihye Hong via GitHub

Sunday, 18 June 2017

• [fxtf-drafts] [css-masking-1] `clip` applies-to section should mention <marker>, not <mask> Amelia Bellamy-Royds via GitHub

Thursday, 15 June 2017

• [fxtf-drafts] [geometry] Method to make a DOMPoint homogeneous Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrix/DOMMatrix could use more methods and helpers. Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] WebGL API considerations Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• [fxtf-drafts] [geometry] WebGL API considerations Joseph Orbegoso Pea via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Joseph Orbegoso Pea via GitHub

Wednesday, 14 June 2017

• Re: [fxtf-drafts] [geometry] Define better how to transform a point with a matrix Simon Pieters via GitHub
• [fxtf-drafts] [geometry] DOMMatrix/DOMMatrix could use more methods and helpers. Joseph Orbegoso Pea via GitHub
• Re: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal Jihye Hong via GitHub
• Re: [fxtf-drafts] Luminance masking is slower than alpha masking Jeff Muizelaar via GitHub

Tuesday, 13 June 2017

• Re: [fxtf-drafts] Luminance masking is slower than alpha masking Ana Tudor via GitHub
• Re: [fxtf-drafts] [geometry] Define better how to transform a point with a matrix Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified Simon Pieters via GitHub
• Re: [fxtf-drafts] [motion] default reference box for basic shape Jihye Hong via GitHub

Monday, 12 June 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] [filters-1] Add animation type to properties Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub

Sunday, 11 June 2017

• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Simon Pieters via GitHub
• Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filters-1] Add animation type to properties Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] Restore SVGFEConvolveMatrixElement#preserveAlpha IDL attribute Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend Dirk Schulze via GitHub

Saturday, 10 June 2017

• Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filters-effects] Allow nesting filters instead of using 'in', 'in2' and 'result' attributes Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filters-1] Add animation type to properties Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? Fredrik Söderqvist via GitHub
• Re: [fxtf-drafts] [filter-effectss-1] All color values/formulas either between 0..1 or 0..255 Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? 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-1] What happens on feImage without valid resource? Paul LeBeau via GitHub
• Re: [fxtf-drafts] [filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow() Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC Dirk Schulze via GitHub
• Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> Dirk Schulze via GitHub
• [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? Dirk Schulze via GitHub
• [fxtf-drafts] [filter-effectss-1] All color values/formulas either between 0..1 or 0..255 Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking] Add mask-position-{x,y} Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking] Add mask-repeat-x/y Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [css-masking] Percentage for clip-path should be n/a or clarification is needed Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories Dirk Schulze via GitHub

Friday, 9 June 2017

• Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories Amelia Bellamy-Royds via GitHub
• Closed: [fxtf-drafts] [css-logical-props] Naming of inset-* properties prefix Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [css-logical-props] Naming of inset-* properties prefix Sebastian Zartner via GitHub
• [fxtf-drafts] [css-logical-props] Naming of inset-* properties prefix Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [css-motion][css-logical-props] offset-* property names collide with logical properties Sebastian Zartner via GitHub
• Closed: [fxtf-drafts] [css-motion][css-logical-props] offset-* property names collide with logical properties Sebastian Zartner via GitHub
• Re: [fxtf-drafts] [css-masking] Example 15's illustration image is wrong Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking-1] Let SVGClipPathElement and SVGMaskElement inherit from SVGGraphicsElement Dirk Schulze via GitHub
• Re: [fxtf-drafts] Luminance masking is slower than alpha masking Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking] Support <g> element is clipping paths Dirk Schulze via GitHub
• [fxtf-drafts] [motion] default reference box for basic shape ewilligers via GitHub
• Re: [fxtf-drafts] [filters-1] Add animation type to properties Brian Birtles via GitHub
• Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties Jihye Hong via GitHub
• Re: [fxtf-drafts] [motion] Link to definition of ray Jihye Hong via GitHub
• Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filters-1] Add animation type to properties Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] Pull Request: [motion] Link to definition of ray ewilligers via GitHub
• Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [filters-1] Add animation type to properties Brian Birtles via GitHub

Thursday, 8 June 2017

• Re: [fxtf-drafts] SVGClipPathElement and SVGMaskElement no longer implement SVGUnitTypes. Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filters-1] Add animation type to properties Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes" Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes" Dirk Schulze via GitHub
• Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes" Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects][css-masking] Should x, y, width, height on mask/filter elements map to SVG geometry properties? Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters Tab Atkins Jr. via GitHub
• Re: [fxtf-drafts] [filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions Dirk Schulze via GitHub
• Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> Dirk Schulze via GitHub
• Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters Dirk Schulze 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] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [motion] Editorial Comments Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] Better definitions for initial position and initial direction Jihye Hong via GitHub

Wednesday, 7 June 2017

• Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified Dirk Schulze via GitHub
• Closed: [fxtf-drafts] [css-masking-1] Replace term masking box with margin box Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified Simon Pieters via GitHub

Monday, 5 June 2017

• Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations Simon Pieters via GitHub
• Re: [fxtf-drafts] [geometry] "Rectangles have the following properties:" Simon Pieters via GitHub
• [fxtf-drafts] Pull Request: Revert "Kill DOMRectList" Tab Atkins Jr. via GitHub
• [fxtf-drafts] Pull Request: Revert "Kill DOMRectList" Simon Pieters via GitHub

Sunday, 4 June 2017

• [fxtf-drafts] [css-masking] Definition of `mask-clip` not compatible with SVG masks Amelia Bellamy-Royds via GitHub
• Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] "The type of box is specified..." Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] Gloss "viewport" Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] "Rectangles have the following properties:" Dirk Schulze via GitHub
• Re: [fxtf-drafts] [geometry] "Rectangles have the following properties:" Dirk Schulze via GitHub
• [fxtf-drafts] [css-masking-1] Replace term masking box with margin box Dirk Schulze via GitHub

Saturday, 3 June 2017

• [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified Simon Fraser via GitHub

Friday, 2 June 2017

• Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties Dirk Schulze via GitHub
• Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties Dirk Schulze via GitHub
• Re: [fxtf-drafts] [motion] Inconsistency in offset-path contain Jihye Hong via GitHub

Thursday, 1 June 2017

• Closed: [fxtf-drafts] [motion] none value considerations Jihye Hong via GitHub
• Closed: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes Jihye Hong via GitHub
• [fxtf-drafts] Pull Request: [motion] Center numbers in circles ewilligers via GitHub

Last message date: Friday, 30 June 2017 14:35:08 UTC