- From: Rik Cabanier <cabanier@gmail.com>
- Date: Wed, 16 Oct 2013 21:11:46 -0700
- To: Justin Novosad <junov@google.com>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
Yes, Blink, Webkit, IE and Firefox all settled on the current spec for setLineDash. On Wed, Oct 16, 2013 at 10:50 AM, Justin Novosad <junov@google.com> wrote: > Also, I think we may have passed the point of no return on this. > setLineDash is already widely supported as currently spec'ed. > > > On Wed, Oct 16, 2013 at 1:43 PM, Ian Hickson <ian@hixie.ch> wrote: > > > On Wed, 16 Oct 2013, Justin Novosad wrote: > > > > > > No, I don't mean an implied zero. I meant that at every iteration over > > > the dash pattern, the pattern is inverted if it has an odd number of > > > elements (blanks become dashes and vice versa). This would render > > > exactly the same as what is currently in the spec, which is consistent > > > with SVG. The only difference is that there is no doubling of the > > > array. If the array needs to be doubled in order to work with the > > > underlying graphics API, that should be the UA's business and it should > > > be hidden under the hood. > > > > Ah, ok. I'm fine with us changing to that if browsers are able to. I > don't > > think there's much of a problem either way; the advantage of the current > > model is that it leaves no ambiguity in the API about what it means to > set > > an odd-length array. > > > > -- > > Ian Hickson U+1047E )\._.,--....,'``. fL > > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' > > >
Received on Thursday, 17 October 2013 04:12:12 UTC