Skip to content
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

Jump to bottom

Readonly input should not have a not-allowed cursor #15683

Closed
andre-d opened this issue Jan 27, 2015 · 1 comment
Closed

Readonly input should not have a not-allowed cursor #15683

andre-d opened this issue Jan 27, 2015 · 1 comment
Labels
css
Milestone
v3.3.4

Comments

@andre-d
Copy link

andre-d commented Jan 27, 2015

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?
@cvrebert cvrebert added the css label Jan 27, 2015
@kkirsche kkirsche mentioned this issue Jan 29, 2015
Merged
kkirsche added a commit to kkirsche/bootstrap that referenced this issue Feb 3, 2015
@kkirsche
[Fix Issue twbs#15683] readonly input should not have a not-allowed…
2dfc58f 
… 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
@cvrebert cvrebert mentioned this issue Feb 17, 2015
Closed
mdo added a commit that referenced this issue Feb 17, 2015
@mdo
Merge pull request #15703 from kkirsche/patch-9
a7a6e7f 
[Fix Issue #15683] `readonly` input should not have a not-allowed cursor
@cvrebert cvrebert added this to the v3.3.4 milestone Feb 27, 2015
@cvrebert
Copy link
Collaborator

This was fixed by #15703.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
css
Projects
None yet
Milestone
v3.3.4
Development

No branches or pull requests
2 participants
@cvrebert @andre-d