24095 2013-12-13 17:48:44 +0000 MouseEvent and TouchEvent co-ordinate types should be kept in-sync 2014-04-09 21:48:27 +0000 1 1 1 Unclassified CSS CSSOM View unspecified PC All NEW P2 normal --- 1 rbyers zcorpan public-css-bugzilla oldest_to_newest 97607 0 rbyers 2013-12-13 17:48:44 +0000 http://dev.w3.org/csswg/cssom-view/#extensions-to-the-mouseevent-interface changes the type of the co-ordinates on MouseEvent from int to double. To be consistent, the co-ordinates of TouchEvent (http://www.w3.org/TR/touch-events/#attributes) should probably change at the same time. Can we just specify corresponding changes to the Touch object here too? 103591 1 zcorpan 2014-04-09 08:12:48 +0000 Currently http://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html has: [[ partial interface Document { Touch createTouch (WindowProxy view, EventTarget target, long identifier, long pageX, long pageY, long screenX, long screenY); TouchList createTouchList (Touch... touches); }; interface Touch { readonly attribute long identifier; readonly attribute EventTarget target; readonly attribute long screenX; readonly attribute long screenY; readonly attribute long clientX; readonly attribute long clientY; readonly attribute long pageX; readonly attribute long pageY; }; ]] The proposal is to change it to: [[ partial interface Document { Touch createTouch (WindowProxy view, EventTarget target, long identifier, double pageX, double pageY, double screenX, double screenY); TouchList createTouchList (Touch... touches); }; interface Touch { readonly attribute long identifier; readonly attribute EventTarget target; readonly attribute double screenX; readonly attribute double screenY; readonly attribute double clientX; readonly attribute double clientY; readonly attribute double pageX; readonly attribute double pageY; }; ]] ? What about pageX/pageY/x/y/offsetX/offsetY? What about using a constructor for Touch with a TouchInit dict instead of (or in addition to) a factory function? 103592 2 zcorpan 2014-04-09 08:15:44 +0000 I can't find Web Events/Touch Events in W3C bugzilla, but please raise this issue on public-webevents@w3.org - it would be good if CSSOM View didn't have to monkey patch it. 103598 3 rbyers 2014-04-09 16:47:29 +0000 I'm trying to figure out where best to address this. I was a member of webevents, but that WG has been closed having completed it's charter. At the moment there is no vehicle for TouchEvents spec changes (due to lack of interest from vendors). This may be a job for the TouchEvents community group (public-touchevents). 103636 4 zcorpan 2014-04-09 21:48:27 +0000 Ah, OK. I'm happy to put something in CSSOM View in the meantime if you need this soon.