- From: Jet Villegas W3C <w3c@junglecode.net>
- Date: Wed, 1 May 2013 22:20:05 -0700
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Doug Schepers <schepers@w3.org>, public-pointer-events@w3.org, public-fx@w3.org, www-style@w3.org
- Message-ID: <CAP82YM506Xj5v+jja4ZfF8yTPSv=_9Q1TLr_BY-VFSJ=6gqpnQ@mail.gmail.com>
Yes, the 'Pref' entry is mozilla specific and is how we enable experimental features without prefixes. --Jet On Wed, May 1, 2013 at 10:16 PM, Rik Cabanier <cabanier@gmail.com> wrote: > That looks good. > I assume the 'Pref' entry is just mozilla specific and won't be part of > the spec. > > > On Wed, May 1, 2013 at 10:11 PM, Jet Villegas W3C <w3c@junglecode.net>wrote: > >> I've started hacking this up for Gecko[1]. The DOMPoint IDL source >> currently looks like this: >> >> [Constructor(optional float x = 0, optional float y = 0),Pref="layout.css.dompoint.enabled"] >> dictionary DOMPoint { >> float x = 0; >> float y = 0; >> }; >> >> I'd like to ratify the IDL in the appropriate spec before moving on to >> the coord-space-conversion methods. Do we have consensus? >> >> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=850805 >> >> --Jet >> >> >> On Tue, Jan 29, 2013 at 9:28 AM, Doug Schepers <schepers@w3.org> wrote: >> >>> Hi, folks- >>> >>> When elements are transformed (shifted X/y through translate, larger or >>> smaller through scale, etc.) using CSS transforms or SVG, dealing with >>> pointer events becomes more complicated and unintuitive... things just >>> aren't where they appear to be. >>> >>> This leads to all sorts of confusion for authors in positioning >>> things... dragging, repositioning, or creating elements based on pointer >>> position. (To a lesser extent, this is a general problem with positioning >>> relative to transformed elements, but nesting context takes care of most >>> non-pointer-position cases.) >>> >>> Jonathan Watt (Mozilla) has a handy script library [1] that helps >>> authors solve this in SVG, but unless someone knows about that script, it >>> is frustrating. I think this should be solved in a spec, perhaps as a >>> method to get the relative transformed coordinates in the appropriate >>> coordinate space. >>> >>> I started to address this in DOM3 Events [2][3], but we decided to defer >>> it, or to address it in CSSOM or the CSS Transforms spec. >>> >>> I'm raising this here to ask where it is most appropriate to address >>> this: the Pointer Events v2 spec (still in the future), the CSS Transforms >>> spec, or the CSSOM spec? >>> >>> [1] http://jwatt.org/svg/tmp/**mouse-relative-positioning.svg<http://jwatt.org/svg/tmp/mouse-relative-positioning.svg> >>> [2] http://www.w3.org/2009/09/16-**webapps-minutes.html#item09<http://www.w3.org/2009/09/16-webapps-minutes.html#item09> >>> [3] http://www.w3.org/2010/10/13-**webapps-minutes.html#item01<http://www.w3.org/2010/10/13-webapps-minutes.html#item01> >>> >>> Regards- >>> -Doug >>> >>> >> >
Received on Thursday, 2 May 2013 05:20:35 UTC