On Wed, Nov 21, 2012 at 2:42 PM, Rick Byers <span dir="ltr"><<a href="mailto:rbyers@chromium.org" target="_blank">rbyers@chromium.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Outside of the design details, are there any thoughts or concerns<br>
about WebKit getting an implementation of pointer events at some<br>
point?<br></blockquote><div><br></div><p style="margin:0px;font-size:13px;font-family:Arial">In my opinion, the pointer events spec is a bad idea (at least, in its current state). I think adding it to WebKit would be hurting both the Web and WebKit.</p>
<p style="margin:0px;font-size:13px;font-family:Arial;min-height:15px"><br></p>
<p style="margin:0px;font-size:13px;font-family:Arial">The premise of the specification is that using mouse event and touch events interchangeably is needed. In reality, nobody was really asking for that because it is a terrible idea. You can already easily unify pen, touch and mouse by writing very little JavaScript, but it is only useful in very few cases.</p>
<p style="margin:0px;font-size:13px;font-family:Arial;min-height:15px"><br></p>
<p style="margin:0px;font-size:13px;font-family:Arial">For the common case, where you want to use touch and mouse events differently, the pointer events makes it harder to write correct code. Each event have a set of attributes with different meaning depending on the event type.</p>
<div><br></div><div>I also think there are some serious issues with the spec.</div><div><br></div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
In particular, having apps state clearly and<br>declaratively [3] whether a touch that starts on an element should<br>result in browser behavior like scrolling or events which can be<br>handled from JavaScript is potentially a big win for touch scrolling<br>
performance (something we struggle with in Chrome).<br></blockquote><div><br></div><div>This is a straw man.</div><div>Chromium has implementation issues there, adding a new spec is not the solution to your problems.</div>
<div><br></div><div>Having touch-action == "auto", the default, will have the exact same issues as you have today.</div><div>Having touch-action == "none" does not buy you much since it would have been implemented today by responding to the very first event.</div>
</div><div><br></div><div>Benjamin </div></div>