Closed pixelshaded closed 5 years ago
Currently the disabled attribute isn't widely supported. If you right click the disabled element and add the css cursor: not-allowed; attribute to the example I believe it will give you the behavior you would want.
With this being the case I would assume you would need to apply the css cursor: not-allowed; until the disabled attribute is more widely adopted.
the shorter answer is: we removed cursor: not-allowed
ages ago, but missed this reference in the docs
https://github.com/twbs/bootstrap/commit/7056f702408a97f01cb32bc6075d88ec27cdcf52
can't find the original discussion on this, but basically the rationale is along the same lines as here https://github.com/twbs/bootstrap/pull/23485#pullrequestreview-56624098
https://getbootstrap.com/docs/4.2/components/forms/#default-stacked states
All of these examples have a disabled attribute, yet none of them have the not-allowed cursor. I've tried firefox and chrome. Also not sure what it means by parent label. Aren't all the labels in the example siblings of the input rather than a parent? I'm wondering if this meant putting disabled on the .form-check since this is the parent of both the label and the input.
OS: Windows 10 Enterprise (Build 16299.666) Chrome: 72.0.3626.81 Firefox Quantum: 64.0.2