1 of 6

Pointers and Interactions

Evolving input on the web

Rick Byers - Google

@RickByers - Mar 21, 2014

​

Recording from EdgeConf 3�transcript

​

2 of 6

Challenges

Performance

Richness

Rationality

3 of 6

Touch latency is too high

Improvements:

  • Threaded scrolling fast paths
  • Click delay avoidance
    • touch-action: manipulation
  • Better perf tooling
    • Eg. input latency tracking in chromium
  • Implementation improvements

​

Performance

4 of 6

Loss of developer control

  • Can’t faithfully implement scrolling in JS
    • Violates the extensible web manifesto
  • Can’t implement scroll-linked effects in JS
  • Touching while scrolling
    • touchmove absorption in Chrome 35

Richness

5 of 6

Multiple input types

  • Pointer Events
    • Unify all co-ordinate based input with one API
  • Accessible by default
    • low-level input APIs make accessibility harder
  • Enable innovation on new types of input
    • TVs (dpad), Perceptive Pixel, Wii remote, voice,�depth cameras, HUDs, touch+hover, haptics

Rationality

6 of 6

What else is next?

Get in touch!

TouchEvents community group

Pointer Events working group

File bugs against Chrome

​