Amelia Bellamy-Royds via GitHub
- Re: [fxtf-drafts] Luminance masking is slower than alpha masking (Thursday, 29 June)
- Re: [fxtf-drafts] [filter-effects] Luminance coefficients are slightly changed from SVG 1.1 (Wednesday, 28 June)
- [fxtf-drafts] [filter-effects] Luminance coefficients are slightly changed from SVG 1.1 (Wednesday, 28 June)
- [fxtf-drafts] [filter-effects] drop-shadow() null value for interpolation is incorrect (Tuesday, 27 June)
- [fxtf-drafts] [css-masking-1] `clip` applies-to section should mention <marker>, not <mask> (Sunday, 18 June)
- Re: [fxtf-drafts] [filter-effectss-1] All color values/formulas either between 0..1 or 0..255 (Saturday, 10 June)
- Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> (Saturday, 10 June)
- Re: [fxtf-drafts] [filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories (Friday, 9 June)
- Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters (Friday, 9 June)
- Re: [fxtf-drafts] [filters-1] Add animation type to properties (Friday, 9 June)
- Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> (Friday, 9 June)
- Re: [fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation (Thursday, 8 June)
- [fxtf-drafts] [css-masking] Definition of `mask-clip` not compatible with SVG masks (Sunday, 4 June)
Ana Tudor via GitHub
Brian Birtles via GitHub
Chris Lilley via GitHub
Dirk Schulze via GitHub
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Sunday, 11 June)
- Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters (Sunday, 11 June)
- Re: [fxtf-drafts] [filters-1] Add animation type to properties (Sunday, 11 June)
- Re: [fxtf-drafts] [filter-effects] Restore SVGFEConvolveMatrixElement#preserveAlpha IDL attribute (Sunday, 11 June)
- Closed: [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend (Sunday, 11 June)
- Re: [fxtf-drafts] [filter-effects] Clarify mapping of Cs and Cb to in and in2 in feBlend (Sunday, 11 June)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Saturday, 10 June)
- Re: [fxtf-drafts] [filters-effects] Allow nesting filters instead of using 'in', 'in2' and 'result' attributes (Saturday, 10 June)
- Re: [fxtf-drafts] [filters-1] Add animation type to properties (Saturday, 10 June)
- Closed: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC (Saturday, 10 June)
- Closed: [fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default (Saturday, 10 June)
- Re: [fxtf-drafts] [filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects] "standard deviation" versus "blur radius" in blur() and dropshadow() (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity? (Saturday, 10 June)
- Re: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC (Saturday, 10 June)
- Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> (Saturday, 10 June)
- [fxtf-drafts] [filter-effects-1] What happens on feImage without valid resource? (Saturday, 10 June)
- [fxtf-drafts] [filter-effectss-1] All color values/formulas either between 0..1 or 0..255 (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking] Add mask-position-{x,y} (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking] Add mask-repeat-x/y (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking] Define "raw geometry" for `<clipPath>` clipping (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories (Saturday, 10 June)
- Closed: [fxtf-drafts] [css-masking] Percentage for clip-path should be n/a or clarification is needed (Saturday, 10 June)
- Closed: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories (Saturday, 10 June)
- Re: [fxtf-drafts] [css-masking] Example 15's illustration image is wrong (Friday, 9 June)
- Re: [fxtf-drafts] [css-masking-1] Let SVGClipPathElement and SVGMaskElement inherit from SVGGraphicsElement (Friday, 9 June)
- Re: [fxtf-drafts] Luminance masking is slower than alpha masking (Friday, 9 June)
- Re: [fxtf-drafts] [css-masking-1] <clipPath> and <mask> elements are missing categories (Friday, 9 June)
- Re: [fxtf-drafts] [css-masking] Support <g> element is clipping paths (Friday, 9 June)
- Re: [fxtf-drafts] SVGClipPathElement and SVGMaskElement no longer implement SVGUnitTypes. (Thursday, 8 June)
- Re: [fxtf-drafts] [filters-1] Add animation type to properties (Thursday, 8 June)
- Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes" (Thursday, 8 June)
- Closed: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes" (Thursday, 8 June)
- Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes" (Thursday, 8 June)
- Re: [fxtf-drafts] [filter-effects][css-masking] Should x, y, width, height on mask/filter elements map to SVG geometry properties? (Thursday, 8 June)
- Re: [fxtf-drafts] [filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions (Thursday, 8 June)
- Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata> (Thursday, 8 June)
- Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters (Thursday, 8 June)
- Re: [fxtf-drafts] [filter-effects] Are blur parameters to drop-shadow() specifying a "blur radius" or a standard deviation (Thursday, 8 June)
- Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified (Wednesday, 7 June)
- Closed: [fxtf-drafts] [css-masking-1] Replace term masking box with margin box (Wednesday, 7 June)
- Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified (Sunday, 4 June)
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations (Sunday, 4 June)
- Re: [fxtf-drafts] [geometry] "The type of box is specified..." (Sunday, 4 June)
- Re: [fxtf-drafts] [geometry] Gloss "viewport" (Sunday, 4 June)
- Re: [fxtf-drafts] [geometry] "Rectangles have the following properties:" (Sunday, 4 June)
- Re: [fxtf-drafts] [geometry] "Rectangles have the following properties:" (Sunday, 4 June)
- [fxtf-drafts] [css-masking-1] Replace term masking box with margin box (Sunday, 4 June)
- Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties (Friday, 2 June)
- Re: [fxtf-drafts] [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties (Friday, 2 June)
ewilligers via GitHub
- Re: [fxtf-drafts] [motion] Inconsistency in offset-path contain (Wednesday, 28 June)
- [fxtf-drafts] Pull Request: [motion] Clarify meaning of contain (Wednesday, 28 June)
- [fxtf-drafts] Pull Request: Simplify description of initial direction (Sunday, 25 June)
- [fxtf-drafts] Pull Request: Clarify motion path and position interaction (Sunday, 25 June)
- Re: [fxtf-drafts] [motion] Interaction with positioning (Sunday, 25 June)
- [fxtf-drafts] Pull Request: [motion] Use border-box as default reference box (Friday, 23 June)
- [fxtf-drafts] Pull Request: [motion] Add Eric Willigers to Motion Path editors (Wednesday, 21 June)
- Re: [fxtf-drafts] [css-motion] description of offset-position should be clearer (Tuesday, 20 June)
- [fxtf-drafts] [motion] default reference box for basic shape (Friday, 9 June)
- [fxtf-drafts] Pull Request: [motion] Link to definition of ray (Friday, 9 June)
- [fxtf-drafts] Pull Request: [motion] Center numbers in circles (Thursday, 1 June)
Fredrik Söderqvist via GitHub
fuchsia via GitHub
Jeff Muizelaar via GitHub
Jihye Hong via GitHub
- Closed: [fxtf-drafts] [motion] Inconsistency in offset-path contain (Wednesday, 28 June)
- Closed: [fxtf-drafts] [motion] Interaction with positioning (Monday, 26 June)
- Closed: [fxtf-drafts] [css-motion] description of offset-position should be clearer (Monday, 26 June)
- Closed: [fxtf-drafts] [motion] default reference box for basic shape (Monday, 26 June)
- Re: [fxtf-drafts] [motion] Add Eric Willigers to Motion Path editors (Wednesday, 21 June)
- Re: [fxtf-drafts] [motion] Define offset-rotate at sharp path segment boundaries (Monday, 19 June)
- Closed: [fxtf-drafts] [motion] Define offset-rotate at sharp path segment boundaries (Monday, 19 June)
- Re: [fxtf-drafts] [motion] Offset-rotate and zero length paths (Monday, 19 June)
- Closed: [fxtf-drafts] [motion] Offset-rotate and zero length paths (Monday, 19 June)
- Re: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal (Wednesday, 14 June)
- Closed: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal (Wednesday, 14 June)
- Re: [fxtf-drafts] [motion] default reference box for basic shape (Tuesday, 13 June)
- Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties (Friday, 9 June)
- Re: [fxtf-drafts] [motion] Link to definition of ray (Friday, 9 June)
- Closed: [fxtf-drafts] [motion] Editorial Comments (Thursday, 8 June)
- Closed: [fxtf-drafts] [motion] Better definitions for initial position and initial direction (Thursday, 8 June)
- Re: [fxtf-drafts] [motion] Inconsistency in offset-path contain (Friday, 2 June)
- Closed: [fxtf-drafts] [motion] none value considerations (Thursday, 1 June)
- Closed: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes (Thursday, 1 June)
Joseph Orbegoso Pea via GitHub
Paul LeBeau via GitHub
Philip Jägenstedt via GitHub
Roman Dvornov via GitHub
Sebastian Zartner via GitHub
Simon Fraser via GitHub
Simon Pieters via GitHub
- [fxtf-drafts] [geometry] JSON serialization of a DOMRectList (Thursday, 22 June)
- [fxtf-drafts] [geometry] Method to make a DOMPoint homogeneous (Thursday, 15 June)
- Re: [fxtf-drafts] [geometry] DOMMatrix/DOMMatrix could use more methods and helpers. (Thursday, 15 June)
- Re: [fxtf-drafts] [geometry] WebGL API considerations (Thursday, 15 June)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Thursday, 15 June)
- Re: [fxtf-drafts] [geometry] Define better how to transform a point with a matrix (Wednesday, 14 June)
- Re: [fxtf-drafts] [geometry] Define better how to transform a point with a matrix (Tuesday, 13 June)
- Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified (Tuesday, 13 June)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Monday, 12 June)
- Re: [fxtf-drafts] [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (Sunday, 11 June)
- Re: [fxtf-drafts] [geometry] DOMPointReadonly matrixTransform() is poorly specified (Wednesday, 7 June)
- Re: [fxtf-drafts] [geometry] Consider using Typed Arrays for matrices and static transform operations (Monday, 5 June)
- Re: [fxtf-drafts] [geometry] "Rectangles have the following properties:" (Monday, 5 June)
- [fxtf-drafts] Pull Request: Revert "Kill DOMRectList" (Monday, 5 June)
Tab Atkins Jr. via GitHub
Tobie Langel via GitHub
Last message date: Friday, 30 June 2017 14:35:08 UTC