- From: Dirk Schulze <dschulze@adobe.com>
- Date: Fri, 27 Dec 2013 09:59:47 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: Robert O'Callahan <robert@ocallahan.org>, public-fx <public-fx@w3.org>, www-style list <www-style@w3.org>
On Dec 26, 2013, at 11:45 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> On Tue Dec 24 2013 at 11:55:47 AM, Dirk Schulze <dschulze@adobe.com> wrote: >> I really wish to have currentColor behave in a way that it does not reveal any secured information. >> >> If we do not find an agreement, a way to limit the security restriction further would be to the following: >> >> For feFlood and feDropShadow: If the value for the ‘flood-color’ property computes to ‘inherit’ or ‘currentColor’ the feFlood filter primitive must be marked as tainted. >> >> For fe*Lighting: If the value for the ‘lighting-color’ property computes to ‘inherit’ or ‘currentColor’ the feFlood filter primitive must be marked as tainted. > > 'inherit' disappears by computed-value time - it's processed into the value it represents at specified-value time. <http://dev.w3.org/csswg/css-cascade/#inherit> I read css3-cascade and still was confused. I wasn’t sure if specified value was the value of the current style sheet or the last value in the cascade. From your explanation it seems to be the latter. > > Note that "flood-color: inherit;" doesn't expose anything, anyway - it resolves to the value of 'flood-color' on the <feFlood>'s parent. It has no connection to the graphics element that uses the filter containing an <feFlood> element. Not quite right. The parent of <feFlood> could use ‘currentColor’. Greetings, Dirk > > ~TJ
Received on Friday, 27 December 2013 10:00:36 UTC