Re: Browsers, Developers and Pointer Events Meeting Notes

Our primary concern with pointer events is the fragmentation problem - that
we'd have to support two models for the foreseeable future, without any
clear path to deprecate one with the other.  This doesn't change that.

One thing that could is if, over time, we see the majority of web
developers coding to pointer events polyfills.  This is why this meeting
was focused around how we can help ensure the success of a good PE
polyfill.  scroll-delay is potentially helpful is enabling PE polyfills
with the performance properties the PE model is designed for.  Eg. maybe
scroll-delay is something developers never use (or we discourage developers
from using) directly, but it is used by a few input frameworks (such as the
Polymer PE polyfill) to enable the input model they want.

Rick


On Thu, Aug 28, 2014 at 4:17 PM, Arthur Stolyar <nekr.fabula@gmail.com>
wrote:

>
> 2014-08-28 20:50 GMT+03:00 Rick Byers <rbyers@chromium.org>:
>
>> I've got a rough proposal for exactly that sort of thing (I called it
>> "scroll-delay") here:
>> https://docs.google.com/a/chromium.org/document/d/1aOQRw76C0enLBd0mCG_-IM6bso7DxXwvqTiRWgNdTn8/edit.
>>  I personally don't see any reason why carefully engineered apps shouldn't
>> be allowed to opt-in to 'scroll-delay: pointermove' causing scrolling to be
>> synchronous with event handling.  I'd love any feedback folks have on the
>> proposal.
>>
>
> It would be good to have functionality/css property like this. Can it
> change your position about PE? Or you now plan this as an extension to
> TouchEvents?
>
> --
> @nekrtemplar <https://twitter.com/nekrtemplar>
>