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

Friday, 30 August 2019

• Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Eric Willigers via GitHub

Thursday, 29 August 2019

• Re: [fxtf-drafts] Clarify the size of the "input image" (#324) Mike Bremford via GitHub
• [fxtf-drafts] [geometry (#367) Ms2ger via GitHub

Friday, 23 August 2019

• Re: [fxtf-drafts] [geometry] Add default dictionary value (#366) Kagami Sascha Rosylight via GitHub
• [fxtf-drafts] Pull Request: [geometry] Add default dictionary value Kagami Sascha Rosylight via GitHub

Wednesday, 21 August 2019

• Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Stephen McGruer via GitHub
• Closed: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Stephen McGruer via GitHub
• Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Stephen McGruer via GitHub
• Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Stephen McGruer via GitHub
• Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Robert Flack via GitHub
• Re: [fxtf-drafts] [motion-1] Computed value of offset-distance is vague (#365) Stephen McGruer via GitHub
• Re: [fxtf-drafts] Computed value of offset-distance is vague (#365) xidachen via GitHub
• [fxtf-drafts] Computed value of offset-distance is vague (#365) xidachen via GitHub

Monday, 19 August 2019

• Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) Mason Freed via GitHub
• Re: [fxtf-drafts] [filter-effects-1] How to handle feColorMatrix with type=saturate and values outside a 0..1 range? (#364) Amelia Bellamy-Royds via GitHub
• [fxtf-drafts] [filter-effects-1] How to handle feColorMatrix with type=saturate and values outside a 0..1 range? (#364) Evgeniy Reizner via GitHub

Wednesday, 14 August 2019

• Closed: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Boris via GitHub
• Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Boris via GitHub
• Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Boris via GitHub
• Re: [fxtf-drafts] [fill-stroke] Stroke alignment: open & complex paths (#345) Paul LeBeau via GitHub
• Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Eric Willigers via GitHub

Tuesday, 13 August 2019

• [fxtf-drafts] Pull Request: Don't distinguish between unspecified and empty DomQuadInit fields Simon Pieters via GitHub

Sunday, 11 August 2019

• Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) Markus Stange via GitHub

Friday, 9 August 2019

• Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Boris via GitHub
• [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Boris via GitHub
• Re: [fxtf-drafts] [filter-effects-2] Clarify the (non-)creation of a containing block for the root element. (#362) Emilio Cobos Álvarez via GitHub
• [fxtf-drafts] Pull Request: [filter-effects-2] Clarify the (non-)creation of a containing block for the root element. Emilio Cobos Álvarez via GitHub
• Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) Theresa O'Connor via GitHub

Thursday, 8 August 2019

• Re: [fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358) Chris Lilley via GitHub

Tuesday, 6 August 2019

• Re: [fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358) Anne van Kesteren via GitHub

Monday, 5 August 2019

• Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361) Mason Freed via GitHub
• Re: [fxtf-drafts] [css-masking-1] Fetch doesn't define "potentially CORS-enabled fetch" (#358) Chris Lilley via GitHub

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