public-fxtf-archive@w3.org from August 2019 by author

Amelia Bellamy-Royds via GitHub

Re: [fxtf-drafts] [filter-effects-1] How to handle feColorMatrix with type=saturate and values outside a 0..1 range? (#364) (Monday, 19 August)

Anne van Kesteren via GitHub

Re: [fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358) (Tuesday, 6 August)

Boris via GitHub

Closed: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) (Wednesday, 14 August)
Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) (Wednesday, 14 August)
Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) (Wednesday, 14 August)
Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) (Friday, 9 August)
[fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) (Friday, 9 August)

Chris Lilley via GitHub

Re: [fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358) (Thursday, 8 August)
Re: [fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358) (Monday, 5 August)

Emilio Cobos Álvarez via GitHub

Eric Willigers via GitHub

Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Friday, 30 August)
Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) (Wednesday, 14 August)

Evgeniy Reizner via GitHub

[fxtf-drafts] [filter-effects-1] How to handle feColorMatrix with type=saturate and values outside a 0..1 range? (#364) (Monday, 19 August)

Kagami Sascha Rosylight via GitHub

Re: [fxtf-drafts] [geometry] Add default dictionary value (#366) (Friday, 23 August)
[fxtf-drafts] Pull Request: [geometry] Add default dictionary value (Friday, 23 August)

Markus Stange via GitHub

Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) (Sunday, 11 August)

Mason Freed via GitHub

Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) (Monday, 19 August)
Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) (Monday, 5 August)

Mike Bremford via GitHub

Re: [fxtf-drafts] Clarify the size of the "input image" (#324) (Thursday, 29 August)

Ms2ger via GitHub

[fxtf-drafts] [geometry (#367) (Thursday, 29 August)

Paul LeBeau via GitHub

Re: [fxtf-drafts] [fill-stroke] Stroke alignment: open & complex paths (#345) (Wednesday, 14 August)

Robert Flack via GitHub

Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)

Simon Pieters via GitHub

[fxtf-drafts] Pull Request: Don't distinguish between unspecified and empty DomQuadInit fields (Tuesday, 13 August)

Stephen McGruer via GitHub

Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)
Closed: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)
Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)
Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)
Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)

Theresa O'Connor via GitHub

Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) (Friday, 9 August)

xidachen via GitHub

Re: [fxtf-drafts] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)
[fxtf-drafts] Computed value of offset-distance is vague (#365) (Wednesday, 21 August)

Last message date: Friday, 30 August 2019 07:09:50 UTC