Re: [pointerevents] Pointer events & disabled form elements

I verified Safari fires touch events on disabled form controls, so 
Gecko's deviation there definitely seems like [a 
bug]( to me.

If the only concern is web compat, then it seems to me like Pointer 
Events is the best chance we'll ever get to fix this and we should at 
least try.  It seems unlikely that sites will depend on the pointer 
and mouse events matching perfectly (code will typically pay attention
 to one or the other, not both).  I suppose it's possible (even 
likely) that when updating a site to use Pointer Events, the existing 
code could be surprised to receive events from disabled form controls.
  But to me it seems worth the cost/risk to try to fix this.  
@smaug---- do you disagree?  What's the alternative for solving the 
issues Jake, Scott and Dave mention above?

@patrickkettner can you check whether the Edge behavior here was 
intentional for some reason, or just a carry-over form how mouse 
events already behaved?  Would you consider removing it if Chrome 
ships our fix to stable successfully?

GitHub Notification of comment by RByers
Please view or discuss this issue at
 using your GitHub account

Received on Tuesday, 28 February 2017 14:59:57 UTC