You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am sure this has been brought up before, but is there a design reason why read-only fields have a not-allowed cursor? Semantically the "not-allowed" cursor often indicates "stay away" or "do not touch". However, read only input fields are often intended for interaction: selection, copy, etc. Although the "not-allowed" cursor makes sense for a disabled state input, I do not feel it is proper for a readonly field.
For example: Github is using a readonly field for the "clone url" box, is this sort of usage discouraged in bootstrap?
The text was updated successfully, but these errors were encountered:
… cursor
[Fix Issue twbs#15683] `readonly` input should not have a `not-allowed` cursor. Instead, this pull request displays a standard cursor and only displays the not-allowed cursor on disabled items.
Revise docs wording to clarify cursor display
I am sure this has been brought up before, but is there a design reason why read-only fields have a not-allowed cursor? Semantically the "not-allowed" cursor often indicates "stay away" or "do not touch". However, read only input fields are often intended for interaction: selection, copy, etc. Although the "not-allowed" cursor makes sense for a disabled state input, I do not feel it is proper for a readonly field.
For example: Github is using a readonly field for the "clone url" box, is this sort of usage discouraged in bootstrap?
The text was updated successfully, but these errors were encountered: