> ________________________________________ > From: ext Simon Fraser [simon.fra...@apple.com] > Sent: Friday, May 07, 2010 5:31 PM > To: Gronholm Kim.1 (Nokia-D/Tampere) > Cc: webkit-dev@lists.webkit.org > Subject: Re: [webkit-dev] TransformAction event > > On May 7, 2010, at 2:07 AM, kim.1.gronh...@nokia.com wrote: > >> Subject: Re: [webkit-dev] TransformAction event >> >>>> The event contains the clientX/Y attributes that can be used as the >>>> origin point for the transforms. >>> >>> clientX and clientY are useless if the element being manipulated is nested >>> within CSS-transformed ancestors. >>> >>> You really need an offsetX/offsetY, which is local to the element. >> >> That's a good point and I agree 100%. I would also like to add pageX/Y >> coordinates as I find them quite useful to have, and remove screenX/Y >> coordinates which are pretty much useless. What do you think? > > I think you should follow MouseEvent as closely as possible. It does > not have pageX/Y, but it does have screenX/Y. offsetX/Y is a non-standard > extension.
Following the MouseEvent was the reason why only client and screen coordinates were specified there but it's just not optimal. Both page and offset coordinates have been defined in the work-in-progress CSS-OM specification (http://www.w3.org/TR/cssom-view/#extensions-to-the-mouseevent-interface) by the CSS Working Group. One option would be to add those without removing anything. Kim > > Simon _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
