New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not Allowed Cursor Missing on Disabled Inputs #28181

Closed
pixelshaded opened this Issue Feb 5, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@pixelshaded
Copy link

pixelshaded commented Feb 5, 2019

https://getbootstrap.com/docs/4.2/components/forms/#default-stacked states

Disabled checkboxes and radios are supported, but to provide a not-allowed cursor on hover of the parent , you’ll need to add the disabled attribute to the .form-check-input. The disabled attribute will apply a lighter color to help indicate the input’s state.

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

@GoRateInfo

This comment has been minimized.

Copy link

GoRateInfo commented Feb 6, 2019

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.

@patrickhlauke

This comment has been minimized.

Copy link
Member

patrickhlauke commented Feb 6, 2019

the shorter answer is: we removed cursor: not-allowed ages ago, but missed this reference in the docs

7056f70

@patrickhlauke

This comment has been minimized.

Copy link
Member

patrickhlauke commented Feb 6, 2019

can't find the original discussion on this, but basically the rationale is along the same lines as here #23485 (review)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment