Wednesday, 30 November 2016
- [fxtf-drafts] Pull Request: SVGClipPathElement and SVGMaskElement no longer implement SVGUnitTypes.
- [fxtf-drafts] Pull Request: SVGClipPathElement and SVGMaskElement no longer implement SVGUnitTypes.
Sunday, 27 November 2016
- Re: [fxtf-drafts] SVGFilterElement must not implement SVGUnitTypes.
- Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes"
Saturday, 26 November 2016
- Re: [fxtf-drafts] SVGFilterElement must not implement SVGUnitTypes.
- [fxtf-drafts] Pull Request: SVGFilterElement must not implement SVGUnitTypes.
- [fxtf-drafts] Pull Request: SVGFilterElement must not implement SVGUnitTypes.
Friday, 25 November 2016
- Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes"
- Re: [fxtf-drafts] [motion][naming] offset-rotation vs rotate
Thursday, 24 November 2016
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional?
- Re: [fxtf-drafts] allow <mask-mode> value to appear almost anywhere in the mask shorthand (fixes #13)
- Closed: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional?
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional?
Wednesday, 23 November 2016
- Re: [fxtf-drafts] [motion][naming] offset-rotation vs rotate
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional?
Monday, 21 November 2016
- Re: [fxtf-drafts] [motion] Clarify meaning of offset-anchor auto
- Closed: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional?
Thursday, 17 November 2016
Wednesday, 16 November 2016
- Re: [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes"
- [fxtf-drafts] [css-masking-1] [filters] Remove "* implements SVGUnitTypes
- Re: [fxtf-drafts] [motion][naming] offset-rotation vs rotate
- Re: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation
- [fxtf-drafts] Pull Request: Use brackets in offset-path syntax
- Re: [fxtf-drafts] [motion] Airplane rotation example should show unrotated airplane
- Re: [fxtf-drafts] [motion] Better definitions for initial position and initial direction
Tuesday, 15 November 2016
- Closed: [fxtf-drafts] [css-motion] Suggestion that <position> properties not be adjacent in offset shorthand
- Re: [fxtf-drafts] [css-motion] Suggestion that <position> properties not be adjacent in offset shorthand
- Re: [fxtf-drafts] [motion] Should failed references be treated as `none` or as a `0deg` zero-length path?
- Closed: [fxtf-drafts] [css-motion] Grammar corrections
- Closed: [fxtf-drafts] [css-motion] properties should probably apply only to transformable elements
Monday, 14 November 2016
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
- Re: [fxtf-drafts] [motion] Better definitions for initial position and initial direction
- Re: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal
- [fxtf-drafts] Pull Request: [motion] properties apply only to transformable elements
- Closed: [fxtf-drafts] [motion] Note about closest-side seems wrong
- [fxtf-drafts] Pull Request: [motion] Clarify note about closest-side
- Closed: [fxtf-drafts] [motion] <angle> notation should be defined as bearing angles
- Closed: [fxtf-drafts] [motion] Initial position and direction for geometry-box
- [fxtf-drafts] Pull Request: [motion] <angle> notation should be defined as bearing angles
- [fxtf-drafts] Pull Request: [motion] offset-rotation is not a bearing.
Friday, 11 November 2016
Thursday, 10 November 2016
Wednesday, 9 November 2016
- [fxtf-drafts] [css-masking] Example 15's illustration image is wrong
- [fxtf-drafts] Pull Request: [motion] Initial position and direction for geometry-box
- [fxtf-drafts] [motion] Initial position and direction for geometry-box
- [fxtf-drafts] Pull Request: [motion] Clarify meaning of offset-anchor auto
Tuesday, 8 November 2016
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- [fxtf-drafts] Pull Request: [motion] Prevent accidental rotation in examples
- Re: [fxtf-drafts] [motion] contain should modify percentages, not path
Monday, 7 November 2016
Saturday, 5 November 2016
- [fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions
- [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes
- [fxtf-drafts] [motion] Interaction with positioning
- [fxtf-drafts] [motion] Better definitions for initial position and initial direction
- [fxtf-drafts] [motion] Unobfuscating calculating the path transform
- [fxtf-drafts] [motion] defining "computed distance" (aka "used distance")
- Re: [fxtf-drafts] [motion] Editorial Comments
- [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?
- [fxtf-drafts] [motion] Editorial Comments
- Re: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly
- [fxtf-drafts] [motion] Airplane rotation example should show unrotated airplane
- [fxtf-drafts] [motion][naming] offset-rotation vs rotate
- [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation
- [fxtf-drafts] Pull Request: [motion-1] More precise definition of offset-position.
- [fxtf-drafts] Pull Request: [motion-1] More precise definition of offset-position.
- [fxtf-drafts] Pull Request: Editorial improvements to offset-distance
- [fxtf-drafts] Pull Request: Editorial improvements to offset-distance
- [fxtf-drafts] [motion] CSS and SVG box correspondence seems overly-simplistic
- [fxtf-drafts] [motion] Should failed references be treated as `none` or as a `0deg` zero-length path?
- [fxtf-drafts] [motion] none value considerations
- [fxtf-drafts] [motion] <angle> notation should be defined as bearing angles
- [fxtf-drafts] [motion] Note about closest-side seems wrong
- [fxtf-drafts] [motion] contain should modify percentages, not path
Thursday, 3 November 2016
Wednesday, 2 November 2016
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
- Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements
- Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor
- Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor
Tuesday, 1 November 2016
- Re: [fxtf-drafts] [motion-1] examples could be clearer
- [fxtf-drafts] [motion
- Re: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal
- [fxtf-drafts] [css-motion] properties should probably apply only to transformable elements
- [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal