W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 2 Oct 2013 08:15:30 +1300
Message-ID: <CAOp6jLaHd-vJ4TofMhp2c4yE-xSw2p3tQBi=BwXqS85u-oJ1DA@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: www-style <www-style@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Wed, Oct 2, 2013 at 8:11 AM, Simon Pieters <simonp@opera.com> wrote:

> I have moved them to a common interface annotated with [NoInterfaceObject]
> and let DOMRect and DOMRectReadOnly implement it.
> https://dvcs.w3.org/hg/csswg/**rev/3c529183812b<https://dvcs.w3.org/hg/csswg/rev/3c529183812b>
> This approach is used by the DOM spec in similar situations.
> In the JS binding, this is equivalent to what the spec had before.

Now we have three interfaces where only two are needed. Why shouldn't
DOMRect extend DOMRectReadOnly directly?

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Tuesday, 1 October 2013 19:16:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC