- From: Simon Pieters <simonp@opera.com>
- Date: Tue, 18 Jun 2013 13:40:19 +0200
- To: Anne van Kesteren <annevk@annevk.nl>
- CC: www-dom@w3.org
On 2/12/13 4:07 PM, Anne van Kesteren wrote: > I think we need to do two things here. > > 1. Move everything from MouseEvent into the UI Events specification. > http://dev.w3.org/csswg/cssom-view/#extensions-to-the-mouseevent-interface > as a distinct definition does not work. I'm happy to remove it from CSSOM View when UI Events is in sync with CSSOM View. > 2. Define offsetX and offsetY as algorithms whose input is the target > node. In particular they are not initialized like the other > attributes, they are computed on getting. This is observable if you > create a synthetic MouseEvent and dispatch it. (CSSOM View does not > get this detail.) Fixed in CSSOM View. > Conversely, offsetX and offsetY should not appear in > the initialization dictionary for this event. Fixed. https://dvcs.w3.org/hg/csswg/rev/39af9667776a > This matters in particular for the shadow tree case where we mutate > the target, but do not want to mutate offsetX and offsetY as that > would require further event-specific caching. > > The subject prefix [D4E] is suggested in the UI Events draft, but I > think that is in error now. > > UI Events: https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm -- Simon Pieters Opera Software
Received on Tuesday, 18 June 2013 11:39:08 UTC