To ensure scroll customization does not tank native scrolling performance, we want to
know ahead of time which component, user-agent or user scroll customization script,
is going to handle a scroll intent for any given element and gesture.
The proposed design is to use a css property `scroll-customization` which behaves
similar to `touch-action` but for scroll customization. The property may be used
to declare which scroll intents may be consumed by scroll customizer. This
technique is well known, simple to use, and easy to understand.
More detailed discussion here:
https://docs.google.com/a/google.com/document/d/19__0qdiAPT8GOF9TY1x9c1U4Vc4geyqpS08tJ9aqKPc/edit?usp=sharing
Comment 1 by majidvp@chromium.org
, Sep 14 2017