Amelia Bellamy-Royds via GitHub
Boris via GitHub
Cameron McCormack via GitHub
chrishtr via GitHub
ewilligers via GitHub
- [fxtf-drafts] Pull Request: Use brackets in offset-path syntax (Wednesday, 16 November)
- Closed: [fxtf-drafts] [css-motion] Suggestion that <position> properties not be adjacent in offset shorthand (Tuesday, 15 November)
- Re: [fxtf-drafts] [css-motion] Suggestion that <position> properties not be adjacent in offset shorthand (Tuesday, 15 November)
- Re: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal (Monday, 14 November)
- [fxtf-drafts] Pull Request: [motion] properties apply only to transformable elements (Monday, 14 November)
- [fxtf-drafts] Pull Request: [motion] Clarify note about closest-side (Monday, 14 November)
- [fxtf-drafts] Pull Request: [motion] <angle> notation should be defined as bearing angles (Monday, 14 November)
- [fxtf-drafts] Pull Request: [motion] offset-rotation is not a bearing. (Monday, 14 November)
- Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor (Friday, 11 November)
- [fxtf-drafts] Pull Request: [motion] Initial position and direction for geometry-box (Wednesday, 9 November)
- [fxtf-drafts] [motion] Initial position and direction for geometry-box (Wednesday, 9 November)
- [fxtf-drafts] Pull Request: [motion] Clarify meaning of offset-anchor auto (Wednesday, 9 November)
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes (Tuesday, 8 November)
- Re: [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes (Tuesday, 8 November)
- [fxtf-drafts] Pull Request: [motion] Prevent accidental rotation in examples (Tuesday, 8 November)
- Re: [fxtf-drafts] [motion] contain should modify percentages, not path (Tuesday, 8 November)
- Re: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly (Monday, 7 November)
- Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor (Thursday, 3 November)
- Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor (Wednesday, 2 November)
- Re: [fxtf-drafts] [css-motion] offset shorthand may be position / anchor (Wednesday, 2 November)
fantasai via GitHub
- [fxtf-drafts] [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions (Saturday, 5 November)
- [fxtf-drafts] [motion] No model for interaction of `offset-position` and shapes (Saturday, 5 November)
- [fxtf-drafts] [motion] Interaction with positioning (Saturday, 5 November)
- [fxtf-drafts] [motion] Better definitions for initial position and initial direction (Saturday, 5 November)
- [fxtf-drafts] [motion] Unobfuscating calculating the path transform (Saturday, 5 November)
- [fxtf-drafts] [motion] defining "computed distance" (aka "used distance") (Saturday, 5 November)
- Re: [fxtf-drafts] [motion] Editorial Comments (Saturday, 5 November)
- [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge? (Saturday, 5 November)
- [fxtf-drafts] [motion] Editorial Comments (Saturday, 5 November)
- Re: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly (Saturday, 5 November)
- [fxtf-drafts] [motion] Airplane rotation example should show unrotated airplane (Saturday, 5 November)
- [fxtf-drafts] [motion][naming] offset-rotation vs rotate (Saturday, 5 November)
- [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation (Saturday, 5 November)
- [fxtf-drafts] Pull Request: [motion-1] More precise definition of offset-position. (Saturday, 5 November)
- [fxtf-drafts] Pull Request: Editorial improvements to offset-distance (Saturday, 5 November)
- [fxtf-drafts] [motion] CSS and SVG box correspondence seems overly-simplistic (Saturday, 5 November)
- [fxtf-drafts] [motion] Should failed references be treated as `none` or as a `0deg` zero-length path? (Saturday, 5 November)
- [fxtf-drafts] [motion] none value considerations (Saturday, 5 November)
- [fxtf-drafts] [motion] <angle> notation should be defined as bearing angles (Saturday, 5 November)
- [fxtf-drafts] [motion] Note about closest-side seems wrong (Saturday, 5 November)
- [fxtf-drafts] [motion] contain should modify percentages, not path (Saturday, 5 November)
Jihye Hong via GitHub
- Re: [fxtf-drafts] [motion][naming] offset-rotation vs rotate (Friday, 25 November)
- Re: [fxtf-drafts] [motion] Clarify meaning of offset-anchor auto (Monday, 21 November)
- Closed: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly (Monday, 21 November)
- Re: [fxtf-drafts] [motion][naming] offset-rotation vs rotate (Wednesday, 16 November)
- Re: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation (Wednesday, 16 November)
- Re: [fxtf-drafts] [motion] Airplane rotation example should show unrotated airplane (Wednesday, 16 November)
- Re: [fxtf-drafts] [motion] Better definitions for initial position and initial direction (Wednesday, 16 November)
- Re: [fxtf-drafts] [motion] Should failed references be treated as `none` or as a `0deg` zero-length path? (Tuesday, 15 November)
- Closed: [fxtf-drafts] [css-motion] Grammar corrections (Tuesday, 15 November)
- Closed: [fxtf-drafts] [css-motion] properties should probably apply only to transformable elements (Tuesday, 15 November)
- Re: [fxtf-drafts] [motion] Better definitions for initial position and initial direction (Monday, 14 November)
- Closed: [fxtf-drafts] [motion] Note about closest-side seems wrong (Monday, 14 November)
- Closed: [fxtf-drafts] [motion] <angle> notation should be defined as bearing angles (Monday, 14 November)
- Closed: [fxtf-drafts] [motion] Initial position and direction for geometry-box (Monday, 14 November)
L. David Baron via GitHub
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional? (Thursday, 24 November)
- Re: [fxtf-drafts] allow <mask-mode> value to appear almost anywhere in the mask shorthand (fixes #13) (Thursday, 24 November)
- Closed: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional? (Thursday, 24 November)
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional? (Thursday, 24 November)
- Re: [fxtf-drafts] [css-masking-1] was the position of 'mask-mode' in the 'mask' shorthand intentional? (Wednesday, 23 November)
- Re: [fxtf-drafts] [motion-1] examples could be clearer (Tuesday, 1 November)
- [fxtf-drafts] [motion (Tuesday, 1 November)
- Re: [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal (Tuesday, 1 November)
- [fxtf-drafts] [css-motion] properties should probably apply only to transformable elements (Tuesday, 1 November)
- [fxtf-drafts] [motion-1] description of interactions should be a little bit more formal (Tuesday, 1 November)
Markus Stange via GitHub
Nikos Andronikos via GitHub
Philip Jägenstedt via GitHub
Richard Schwerdtfeger via GitHub
Rossen Atanassov via GitHub
shans via GitHub
Tab Atkins Jr. via GitHub
Last message date: Wednesday, 30 November 2016 10:51:18 UTC