Re: Expected behavior for stroke-dasharray="0"

Hi Amelia,

The browser in question is Firefox 37 (currently beta). I already filed a bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1149516) because I thought is was a clear violation of the spec. 

But, as you can see from the comments to the bug ticket  above, some people interpreted the 

"then the stroke is rendered as if a value of none were specified"

to refer to the stroke property instead of the stroke-dasharray property.

Cheers,
Thomas

> Am 02.04.2015 um 02:31 schrieb Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>:
> 
> Hi Thomas,
> 
> As you mentioned, the SVG 1.1 specs say:
>> If the sum of the values is zero, then the stroke is rendered as if a value of none were specified.
> http://www.w3.org/TR/SVG/painting.html#StrokeDasharrayProperty
> 
> Which makes the behavior you mention definitely a bug.  Out of curiosity, which browser is not currently displaying the stroke in this case? 
> 
> The SVG 2 draft includes much more detailed implementation instructions for stroking to deal with additional edge cases; these reinforce the above expectation, if you follow through the algorithms carefully.
> https://svgwg.org/svg2-draft/painting.html#StrokeShape
> 
> Amelia BR
> 
> 
>> On 31 March 2015 at 16:15, Thomas Zimmermann <thomaszimmermann1@gmail.com> wrote:
>> I'm looking for clarification regarding the special case of setting the stroke-dasharray property to "0" for SVG shapes like paths or circles.
>> 
>> From the related part of the SVG1.1 spec (http://www.w3.org/TR/SVG/painting.html#StrokeDasharrayProperty), it seemed to me that the behavior should be the same as if stroke-dasharray="none" was specified, i.e. to render a solid line.
>> 
>> However, I recently came across a browser implementation that displayed no stroke at all in that case. So maybe you could give me your opinions on this to find out if that's intended behavior or a bug that needs to be addressed.
>> 
>> Cheers,
>> Thomas
>