- From: Dirk Schulze <dschulze@adobe.com>
- Date: Tue, 1 Oct 2013 03:22:24 -0700
- To: Simon Pieters <simonp@opera.com>
- CC: www-style list <www-style@w3.org>
On Oct 1, 2013, at 12:16 PM, Dirk Schulze <dschulze@adobe.com> wrote: > > On Oct 1, 2013, at 11:45 AM, Simon Pieters <simonp@opera.com> wrote: > >> On Thu, 26 Sep 2013 23:20:37 +0200, Dirk Schulze <dschulze@adobe.com> >> wrote: >> >>> Hi, >>> >>> Would it be possible to add alias attributes 'x' and 'y' that point to >>> 'left' and 'top'? That would make it more compatible with SVGRect and >>> the SVG WG could start replacing SVGRect[1] with DOMRect as well for a >>> unified platform. >> >> DOMRect should now be compatible with SVGRect, so SVG can start using it >> (or DOMRectReadOnly). >> >> I added a no-argument constructor to DOMRect in >> https://dvcs.w3.org/hg/csswg/rev/3eb9884be51c >> >> The missing piece would be to alias the window.SVGRect property to >> DOMRect, but do we need to? Is there actually Web content that relies on >> the SVGRect constructor/interface object? (The same question applies to >> SVGMatrix also.) > > Sorry if I add more confusion to it. But my understanding was that all attributes on DOMRect are readonly and DOMRectMutable allows modifications. DOMRectMutable would inherit from DOMRect. The way it is in the spec would be fine with me if the one inherits from the other. Forgot to add the reference to the previous discussion: http://lists.w3.org/Archives/Public/www-style/2013Sep/0825.html > > Greetings, > Dirk > >> >> -- >> Simon Pieters >> Opera Software > >
Received on Tuesday, 1 October 2013 10:22:56 UTC