[wp-trac] [WordPress Trac] #26785: Disabled buttons should not have any pointer events

[WordPress Trac]

#26785: Disabled buttons should not have any pointer events
------------------------------+------------------
 Reporter:  chiragswadia      |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  3.9
Component:  Administration    |     Version:  3.8
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  ui
------------------------------+------------------

Comment (by nacin):

 Replying to [comment:8 chiragswadia]:
 > This is actually a ideal UI convention followed while including disabled
 buttons anywhere on a website. If everybody uses it, then why should
 WordPress core ignore it!
 > Regarding the benefits, this css rule adds something to the disabled
 buttons styling as per the standards.

 Hi, this still isn't quite enough information for us to go on. WordPress
 primary buttons are styled to not react to pointer events, even without
 this line of CSS. (The secondary gray buttons are, which is a bug —
 covered by [attachment:26785.diff].)

 A disabled button in WordPress is already not 'clickable'. It doesn't
 visibly react to hover, focus, or click.

 The spec seems to indicate that, while it has its role in HTML land,
 pointer-events was/is primarily for SVG. While we could use it, I don't
 see an actual tangible benefit in this case.

 It seems like the only benefit would be making it so we don't need to
 specifically style the hover/active states of disabled buttons. But we
 already do that and we would continue to need to do that anyway for
 browsers that don't support this property.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26785#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform