W3C home > Mailing lists > Public > www-style@w3.org > May 2012

[cssom-view] Resolving clientX/clientY in CSSOM vs DOM Levels 2/3 Events

From: Dan Beam <dbeam@google.com>
Date: Tue, 1 May 2012 19:39:06 -0700
Message-ID: <CANpe7K1J-9q52ekEe3W65MRTP_Z4Vocyp1urVXK05yp9U9U+KQ@mail.gmail.com>
To: www-style@w3.org
Cc: shans@google.com, glenn.adams@cox.com
Hello www-stylers and CSSOM View editors,

It seems there's a small conflict between the CSSOM working draft and
DOM Level 2/3 Events.  The CSSOM View working draft and editor's draft
claim to introduce some attributes to MouseEvent,
(http://www.w3.org/TR/cssom-view/#extensions-to-the-mouseevent-interface,
http://dev.w3.org/csswg/cssom-view/#extensions-to-the-mouseevent-interface).
 Here's the abridged version with the conflicters:

  MouseEvent {
    readonly attribute long screenX;
    readonly attribute long screenY;
    readonly attribute long clientX;
    readonly attribute long clientY;
  };

But these attributes are already present and defined in DOM Level 2
Events (http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-MouseEvent)
and DOM Level 3 Events
(http://www.w3.org/TR/DOM-Level-3-Events/#webidl-events-MouseEvent).

Because all attributes seem exactly the same in CSSOM View and their
documentation doesn't seem to add/mandate any behavioral changes,
couldn't they simply be removed from this document?  It doesn't seem
that they're being added if they've been present since around in DOM
Level 2 Events since Nov. 2000 (11 years prior).

Just an observation,

Dan Beam
dbeam@google.com
Received on Wednesday, 2 May 2012 02:39:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:53 GMT