- From: Dean Jackson <dino@apple.com>
- Date: Thu, 9 Apr 2015 07:49:01 +1000
- To: Arthur Barstow <art.barstow@gmail.com>
- Cc: public-pointer-events@w3.org, Edward O'Connor <eoconnor@apple.com>
> On 8 Apr 2015, at 9:50 pm, Arthur Barstow <art.barstow@gmail.com> wrote: > > On 3/26/15 2:47 PM, Dean Jackson wrote: >>> Does anyone know what is "the user agent’s default force click features"? >> Apps (such as Safari) can have different behaviours for actions that are beyond the strength of a normal click. This is not the same as a context menu. For example, Safari shows a popover of a map when you force click on an address, a popover to dial when you force click on a phone number, and a popover preview of a page if you force click on a link. It's actually a bit more complex than that, because the reveal animation of the popover is tied to the amount of pressure the user is applying. >> >> What we were talking about in that patch was a way to prevent this default action (while still allowing the regular click events to fire). >> >> While I'm replying, what has landed now is experimental (and hence has a prefix). I suggest not considering anything final until we make a proposal to a standards body. > > Dean - can you please give us at least a rough guestimate on when such a proposal will be Public? Sorry, I can't (Apple policy). What I can say is that we've been considering a number of different ways to go about exposing this hardware, and we're starting to settle on something we think works. Dean
Received on Wednesday, 8 April 2015 21:49:34 UTC