- From: Chris Lilley <chris@w3.org>
- Date: Tue, 1 Nov 2011 19:29:23 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: Vincent Hardy <vhardy@adobe.com>, Patrick Dengler <patd@microsoft.com>, Dirk Schulze <vbs85@gmx.de>, Dean Jackson <dino@apple.com>, "public-fx@w3.org" <public-fx@w3.org>
On Tuesday, November 1, 2011, 1:35:00 AM, Tab wrote: TAJ> On Mon, Oct 31, 2011 at 5:29 PM, Chris Lilley <chris@w3.org> wrote: >> On Tuesday, November 1, 2011, 1:18:10 AM, Tab wrote: >> TAJ> Fragment shaders can do arbitrary pixel transformations. >> TAJ> There is no way, even theoretically, to make pointing respond to that. >> TAJ> Some existing Filters *could* so so (like feOffset), but we've >> TAJ> resolved to keep them consistent and have them not affect pointing. >> I don't recall such a resolution. I do recall some discussions, which did not reach a conclusion, about whether it would make for more intuitive for users if mouse pointer picking was affected by feOffset (for example) so that what you *think* you are clicking on is what actually gets clicked. TAJ> feOffset is used for things like drop shadows, though, which TAJ> definitely *shouldn't* affect pointing. There are cases where you want it to affect positioning and cases where you don't. For drop shadow, it depends how you use it. The regular shadow behind filled text, you don't want it to, I agree. -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Tuesday, 1 November 2011 18:30:23 UTC