Last Call comments

Hi, these comments are from people at Yandex who implemented Pointer  
Events for our services...

The pointer system works well when you have only one input device (one  
mouse, one pen or single-touch-capable screen) and saves some code  
comparing to the Safari Mobile event model. But if you have more than one  
input device, the pointer-oriented code becomes far more complex and less  
obvious compared to the touch-oriented code for Safari Mobile because you  
have to deal with event streams on your own. We should simplify the tough  
case (multi-touch), not just the already simple one (single input device).

Why should the mouse have pointerId == 1? There is no need for this, since  
we have a pointerType for detecting input device type, and it makes it  
impossible to use two mouse devices simultaneously.

The capturing system is a meaningless artifact of IE6, why implement it  
again?

Tilt angles are very difficult to work with, why not use standard  
spherical coordinates?

Preventing browser reaction via a custom css property contradicts both the  
css paradigm (css is not designed to handle user input) and the DOM Event  
paradigm (preventDefault is the normal way to prevent browser behavior);  
furthermore, the idea that browser may have different reactions on mouse  
and touch actions ruins the whole proposal.

cheers

Chaals

-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com

Received on Monday, 18 March 2013 09:23:27 UTC