- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 18 Sep 2013 15:16:44 +0200
- To: "Dirk Schulze" <dschulze@adobe.com>, "Robert O'Callahan" <robert@ocallahan.org>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "Rik Cabanier" <cabanier@gmail.com>, "Simon Fraser" <smfr@me.com>, "Andrew Dupont" <w3@andrewdupont.net>, www-style <www-style@w3.org>
On Sun, 15 Sep 2013 23:45:36 +0200, Robert O'Callahan <robert@ocallahan.org> wrote: > On Sun, Sep 15, 2013 at 6:23 PM, Dirk Schulze <dschulze@adobe.com> wrote: > >> On Sep 15, 2013, at 7:59 AM, Robert O'Callahan <robert@ocallahan.org> >> wrote: >> >> > On Thu, Aug 29, 2013 at 2:12 PM, Robert O'Callahan >> <robert@ocallahan.org> >> wrote: >> > Alright, DOMPoint/DOMRect/DOMQuad works for me until someone else >> objects... >> > >> > My understanding is that there's a consensus to rename >> ClientRect(List) >> to DOMRect(List) and use DOMMatrix/DOMPoint/DOMQuad. Is this recorded >> anywhere? If not, can someone please record it :-). >> >> Yes, we resolved that the CSS WG prefers DOM prefixes for geometric >> APIs. >> [1] >> > > OK, but that doesn't explicitly address renaming ClientRect(List), which > unlike the APIs discussed in that chat log has some (probably miniscule) > compatibility risk. On Wed, 18 Sep 2013 13:59:24 +0200, Robert O'Callahan <robert@ocallahan.org> wrote: > On Wed, Sep 18, 2013 at 11:38 PM, Dirk Schulze <dschulze@adobe.com> > wrote: > >> Well, ClientRect has a specific boundary to an object in the first >> place, >> while other geometry terms like Matrix, Point, Quad don't need to have >> this. It looks strange to me to prefix the latter terms with Client. >> > > Yeah, I don't really want to go that way. OK. I've renamed ClientRect/ClientRectList to DOMRect/DOMRectList. https://dvcs.w3.org/hg/csswg/rev/202bc4a6fe01 -- Simon Pieters Opera Software
Received on Wednesday, 18 September 2013 13:17:37 UTC