Re: [pointerevents] Pointer events & disabled form elements

smaug---- do you have a reason why we wouldn't want to fire 
`pointerdown` and `pointerup`?  Certainly consistency between mouse 
and pointer events is one argument.  But is there any reason (other 
than annoying web compat legacy) why disabled form controls should 
swallow `mousedown` and `mouseup`?

It looks like Firefox also suppresses `touchstart` and `touchend` on 
disabled form controls where Chrome does not (trying to test Safari 
now but my iPhone is not cooporating).  Depending on the conclusion we
 reach here, we may want to file a TouchEvents-specific spec issue as 
well.

-- 
GitHub Notification of comment by RByers
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/177#issuecomment-282870383
 using your GitHub account

Received on Monday, 27 February 2017 22:01:23 UTC