Disabled checkboxes and buttons do not have the accompanying cursor

[JustinDrake]

Disabled inputs, selects and links have cursor: not-allowed. Not so for checkboxes and buttons. Is the inconsistency on purpose?

[cvrebert]

@mdo What's the story behind

bootstrap/less/buttons.less

Line 40 in c38b720

cursor: default;

(which is still in the current code)?

[JustinDrake]

@mdo @cvrebert Still not fixed for buttons.

[JustinDrake]

@cvrebert @mdo Also, the checkbox cursor doesn't work properly. It seems to only work right outside the checkbox only.

[cvrebert]

Tracking checkbox issue separately as #9614.

[cvrebert]

We are properly setting cursor: not-allowed;, but pointer-events: none; is interfering with it. We want both of those, so not sure what to do here.

[mdo]

The buttons will have to stay without the cursor I think—I'm onboard with the pointer events I think. Fixed the checkbox thing though.

[tkrotoff]

We are properly setting cursor: not-allowed;, but pointer-events: none; is interfering with it

I've tested under Chrome 35, IE11 and Firefox 28; they all have the same behavior :/
(issue on StackOverflow: http://stackoverflow.com/questions/17877535/css-pointer-events-and-cursor-style).

I think it is a bug in current browser implementations.
The specification just says pointer-events none The given element does not receive pointer events; it does not say that the cursor should be forced to default.
See https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events
See http://www.w3.org/TR/SVG11/interact.html#PointerEventsProperty

[hnrch02]

@tkrotoff There is no specification for pointer-events on HTML elements yet, it has been pushed to CSS Basic User Interface Module Level 4.

Its extension to HTML elements, though present in early drafts of CSS Basic User Interface Module Level 3, has been pushed to its level 4.

https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events#Specifications

Also, it can be argued that setting cursor on an element happens on hover, and because pointer-events: none prevents the element from firing any mouse related events, it is thusly the correct behavior.