W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2013

Re: Transformed Pointer Coordinates?

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 11 Feb 2013 20:07:12 -0800
To: "robert@ocallahan.org" <robert@ocallahan.org>
CC: Jacob Rossi <Jacob.Rossi@microsoft.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Simon Fraser <smfr@me.com>, Doug Schepers <schepers@w3.org>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>, "public-fx@w3.org" <public-fx@w3.org>, www-style list <www-style@w3.org>
Message-ID: <BA1728E1-A5D5-4690-B6E9-A011578A54FE@adobe.com>

On Feb 11, 2013, at 6:59 PM, Robert O'Callahan <robert@ocallahan.org> wrote:

> Maybe I'm wrong but I feel like it would be best to keep 2D points and 3D points as separate interfaces. We don't want Web authors to wonder what "z" and "w" mean for the result of convertPointFromNode.

I trust web authors to understand what z is for. w might be a bit more difficult but might not even be necessary to specify. If we add a new element into the web platform we should think beyond the current needs. I believe that this interface would be useful for other situations like 3D transforms or WebGL contexts. Especially CSS Transforms have a lot of situations where you get from a 2D context into a 3D context. You may would need to return different object types depending on the current transformation, this seems to be difficult in the long term.

Greetings,
Dirk 

> 
> Rob
> -- 
> Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir — whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28]
Received on Tuesday, 12 February 2013 04:07:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 February 2013 04:07:48 GMT