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

Re: [geometry] Should DOMRect have a serializer

From: Simon Pieters <simonp@opera.com>
Date: Wed, 20 Jan 2016 18:30:39 +0100
To: public-fx@w3.org, "Boris Zbarsky" <bzbarsky@mit.edu>
Cc: "Domenic Denicola" <d@domenic.me>
Message-ID: <op.ybjr9dd1idj3kv@simons-mbp>
On Tue, 19 Jan 2016 09:58:35 +0100, Simon Pieters <simonp@opera.com> wrote:

>>>> For DOMMatrix, I guess it makes sense to serialize an array with the
>>>> elements. We could either always serialize all of them or only  
>>>> serialize
>>>> 6 elements when is2D returns true.
>>>
>>> Yeah, I'm not sure what's best here.
>>
>> OK. Always serializing 16 elements is simpler.
>
> Went with this for now. I don't remember now why I thought an array made  
> sense; it can be used for constructing a new matrix but it can't be  
> passed in directly to e.g. multiplySelf(). Should I change  
> DOMMatrixReadOnly's serializer to an object?

Changed to an object with all attributes in  
https://github.com/w3c/fxtf-drafts/commit/7b5664a99dff3a3c3afd5085c65fea7ad7791d9c

-- 
Simon Pieters
Opera Software
Received on Wednesday, 20 January 2016 17:31:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 20 January 2016 17:31:12 UTC