-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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
form-control: missing cursor if switching off readonly on dblclick [Chrome+Safari] #16022
Comments
Hi @DenisVuyka! You appear to have posted a live example (https://fiddle.jshell.net/dvuyka/htua4ugm/show/light/), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:
You'll need to fix these errors and post a revised example before we can proceed further. (Please note that this is a fully automated comment.) |
The example was updated with readonly="readonly", this does affect the issue though. |
Reposting so as to trigger the validator again: https://jsfiddle.net/dvuyka/htua4ugm/ |
Hi @cvrebert! You appear to have posted a live example (https://fiddle.jshell.net/dvuyka/htua4ugm/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:
You'll need to fix these errors and post a revised example before we can proceed further. (Please note that this is a fully automated comment.) |
Corrected to use latest Bootstrap: https://jsfiddle.net/w16tvcp2/2/ |
OS X Safari is also affected. |
Simplified testcase: https://jsfiddle.net/f8utvj06/2/ |
@cvrebert Thanks for simplified scenario. I've noticed that control starts working when setting "outline: -2px;". I guess this is something to be fixed at 'form-control' side. |
Filed Chrome bug: https://code.google.com/p/chromium/issues/detail?id=465274 |
Discovered a different Firefox bug in the course of investigating your bug; reported it as https://bugzilla.mozilla.org/show_bug.cgi?id=1141011 |
Filed WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=142477 |
Note that this isn't |
These need to be added to the wall of bugs, @cvrebert? |
@zacechola The Chrome bug, yes. The others aren't Bootstrap-specific. |
Add Wall of Browser Bugs entry for #16022
Anything left to do here? |
@mdo Unless you happen to know some relevant CSS magic or were to think this bug is more important than the custom |
* tag 'v3.3.4' of https://github.com/twbs/bootstrap: (281 commits) full grunt BootstrapCDN: v3.3.2 => v3.3.4 Sass: v3.3.3 => v3.3.4 v3.3.2 => v3.3.4 Clarify that role="button" is required for dismiss-on-next-click popovers automatic `grunt dist` Bump bootstrap-sass download link to Sass-specific v3.3.3 automatic `grunt dist` Run `grunt`. Bump devDependencies. Document that .progress-bar-striped doesn't work in IE<=9; fixes twbs#16058 automatic `grunt dist` Remove trailing whitespace in forms.less Fixed proper navigation element selection on backward scrolling (from the bottom to the top) automatic `grunt dist` Increment quick start options to five Add Wall of Browser Bugs entry for twbs#16022 automatic grunt dist automatic grunt dist Affix: $('body') => $(document.body) ...
The issue can be observed here: jsfiddle
Was reproduced with Chrome 41.
Description: when switching off 'readonly' state of the input.form-control on the fly (via dblclick event) element stops showing text caret, however user can still type text. The issue is not reproduced for standard input controls without form-control class (see jsfidlle link above).
The text was updated successfully, but these errors were encountered: