W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2011

Re: Jan 10 2011 FXTF telcon cancelled

From: Dirk Schulze <vbs85@gmx.de>
Date: Tue, 11 Jan 2011 12:11:44 +0100
Cc: public-fx@w3.org
Message-Id: <BAC12F97-2948-4370-AB96-150F5FB4B606@gmx.de>
To: Erik Dahlstrom <ed@opera.com>

> 
>> Regarding to feDropShadow. The current specification text is talking about the color of the shadow. Don't we need to define new color and opacity attribute? Similar  to feFlood it would be dropShadow-color and dropShadow-opacity.
> 
> Maybe, another option is to use e.g fill and fill-opacity (or flood-color/flood-opacity) for this. I'm not really sure why there's a need to add new custom color properties that can only be used in one place.

Sorry for the confusion. I was more talking about the CSS property 'color', not the content. But I forgot that 'color' can really make a difference (e.g for color: black; flood-color: currentColor;)
'fill' would mean that feDropShadow can take a PaintServer (not only color, but also gradients and patterns) and I don't think that this would be very useful. 'flood-color' would be ok but I wouldn't use it, because the name associates that it belongs to feFlood. What about 'shadow-color'?

> 
>> Also, I saw some discussions about the meaning of stdDeviation and blur radius. It would be great to harmonize all the definitions for CSS shadows, Canvas shadows and feDropShadow.
> 
> Do you have a pointer to that discussion? I agree that it would be good to see if it's possible harmonize the definitions.


Alejandro Castro opened a bug report on W3C bugzilla:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9942

and also take a look at:

https://bugs.webkit.org/show_bug.cgi?id=51446 (comment 3 and 5)

Greetings,
Dirk
Received on Tuesday, 11 January 2011 11:12:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 11:12:19 GMT