public-fxtf-archive@w3.org from November 2016 by thread

[fxtf-drafts] Pull Request: SVGClipPathElement and SVGMaskElement no longer implement SVGUnitTypes. Tab Atkins Jr. via GitHub (Wednesday, 30 November)

[fxtf-drafts] Pull Request: SVGClipPathElement and SVGMaskElement no longer implement SVGUnitTypes. Nikos Andronikos via GitHub (Wednesday, 30 November)

[fxtf-drafts] Pull Request: SVGFilterElement must not implement SVGUnitTypes. Nikos Andronikos via GitHub (Saturday, 26 November)

[fxtf-drafts] Pull Request: SVGFilterElement must not implement SVGUnitTypes. Nikos Andronikos via GitHub (Saturday, 26 November)

Re: [fxtf-drafts] allow <mask-mode> value to appear almost anywhere in the mask shorthand (fixes #13) L. David Baron via GitHub (Thursday, 24 November)

Closed: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional? L. David Baron via GitHub (Thursday, 24 November)

Closed: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly Jihye Hong via GitHub (Monday, 21 November)

Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional? Cameron McCormack via GitHub (Monday, 21 November)

[fxtf-drafts] [filter-effects] A proposal of the definition of the distance between two filter function lists Boris via GitHub (Thursday, 17 November)

[fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes Philip Jägenstedt via GitHub (Wednesday, 16 November)

[fxtf-drafts] Pull Request: Use brackets in offset-path syntax ewilligers via GitHub (Wednesday, 16 November)

Closed: [fxtf-drafts] [css-motion] Suggestion that <position> properties not be adjacent in offset shorthand ewilligers via GitHub (Tuesday, 15 November)

Re: [fxtf-drafts] [css-motion] Suggestion that <position> properties not be adjacent in offset shorthand ewilligers via GitHub (Tuesday, 15 November)

Closed: [fxtf-drafts] [css-motion] Grammar corrections Jihye Hong via GitHub (Tuesday, 15 November)

[fxtf-drafts] Pull Request: [motion] properties apply only to transformable elements ewilligers via GitHub (Monday, 14 November)

[fxtf-drafts] Pull Request: [motion] Clarify note about closest-side ewilligers via GitHub (Monday, 14 November)

[fxtf-drafts] Pull Request: [motion] <angle> notation should be defined as bearing angles ewilligers via GitHub (Monday, 14 November)

[fxtf-drafts] Pull Request: [motion] offset-rotation is not a bearing. ewilligers via GitHub (Monday, 14 November)

Re: [fxtf-drafts] [filters] Backdrop filters should not use BackgroundImage Markus Stange via GitHub (Thursday, 10 November)

[fxtf-drafts] [css-masking] Example 15's illustration image is wrong Markus Stange via GitHub (Wednesday, 9 November)

[fxtf-drafts] Pull Request: [motion] Initial position and direction for geometry-box ewilligers via GitHub (Wednesday, 9 November)

[fxtf-drafts] [motion] Initial position and direction for geometry-box ewilligers via GitHub (Wednesday, 9 November)

[fxtf-drafts] Pull Request: [motion] Clarify meaning of offset-anchor auto ewilligers via GitHub (Wednesday, 9 November)

[fxtf-drafts] Pull Request: [motion] Prevent accidental rotation in examples ewilligers via GitHub (Tuesday, 8 November)

[fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Interaction with positioning fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Better definitions for initial position and initial direction fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Unobfuscating calculating the path transform fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] defining "computed distance" (aka "used distance") fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge? fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Editorial Comments fantasai via GitHub (Saturday, 5 November)

Re: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Airplane rotation example should show unrotated airplane fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion][naming] offset-rotation vs rotate fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] offset-rotation should only do path-relative rotation fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] Pull Request: [motion-1] More precise definition of offset-position. Tab Atkins Jr. via GitHub (Saturday, 5 November)

[fxtf-drafts] Pull Request: [motion-1] More precise definition of offset-position. fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] Pull Request: Editorial improvements to offset-distance Tab Atkins Jr. via GitHub (Saturday, 5 November)

[fxtf-drafts] Pull Request: Editorial improvements to offset-distance fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] CSS and SVG box correspondence seems overly-simplistic fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Should failed references be treated as `none` or as a `0deg` zero-length path? fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] none value considerations fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] <angle> notation should be defined as bearing angles fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] Note about closest-side seems wrong fantasai via GitHub (Saturday, 5 November)

[fxtf-drafts] [motion] contain should modify percentages, not path fantasai via GitHub (Saturday, 5 November)

Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements chrishtr via GitHub (Wednesday, 2 November)

Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor ewilligers via GitHub (Wednesday, 2 November)

[fxtf-drafts] [motion L. David Baron via GitHub (Tuesday, 1 November)

[fxtf-drafts] [css-motion] properties should probably apply only to transformable elements L. David Baron via GitHub (Tuesday, 1 November)

[fxtf-drafts] [motion-1] description of interactions should be a little bit more formal L. David Baron via GitHub (Tuesday, 1 November)

Last message date: Wednesday, 30 November 2016 10:51:18 UTC