-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Initialized select input with readonly="true" attribute displays cursor on Safari mobile (iPhone6) #2448
Comments
Hi, I did the change in my PR to write readonly="readonly" . |
The problem isn't the readonly attribute, but rather I think it isn't being On Mon, Dec 28, 2015 at 8:55 PM, TyrionGraphiste notifications@github.com
Doggy sends his greetings from Mars. |
It seems the problem is the cursor which stays in the input after its focus, under IE it does exactly the same behavior even if the dropdown has a z-index. So I think it's rather a web-browser bug, I'll see for a CSS fix. |
user-select: none; fixed it for me in Safari |
The readonly attribute on touch inputs hides the keyboard, but recently the cursor started appearing. Adding touch events removes the flashing cursor. Dogfalo/materialize#2448
The readonly attribute on touch inputs hides the keyboard, but recently the cursor started appearing. Adding touch events removes the flashing cursor. Dogfalo/materialize#2448 Also moved unprefixed properties last
The readonly attribute on touch inputs hides the keyboard, but recently the cursor started appearing. Adding touch events removes the flashing cursor. Dogfalo/materialize#2448 Also moved unprefixed properties last
@Dogfalo did you check it? |
I'm stilling having this issue where the multi select can't be closed in Chrome on iOS... Stopped the cursor blinking with |
@Dogfalo Was this ever fixed for the disabled attribute? I have a select dropdown that I need to toggle the disabled attribute on with two buttons.
|
The readonly attribute on touch inputs hides the keyboard, but recently the cursor started appearing. Adding touch events removes the flashing cursor. Dogfalo/materialize#2448 Also moved unprefixed properties last
The readonly attribute on touch inputs hides the keyboard, but recently the cursor started appearing. Adding touch events removes the flashing cursor. Dogfalo/materialize#2448 Also moved unprefixed properties last
The element is initialized with materialize_select function and transformed to <input> with readonly="true" attribute. When clicked on iPhone6, the text in this element can't be edited but there is displayed a cursor. I think it may be caused by readonly="true" syntax instead of readonly, readonly="" or readonly="readonly" suggested by W3C. Is there any reason other than readability to choose readonly="true" above any of them?
The text was updated successfully, but these errors were encountered: