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

IE11 radio button and checkboxes using button plugin don't work correctly when navigating with keyboard #16673

Closed
mynameisstephen opened this issue Jun 19, 2015 · 11 comments

Comments

@mynameisstephen
Copy link

Steps to reproduce

  1. In IE11 tab to a radio button group.
  2. Press right or left to select a different radio button
  3. Tab out of the button group
  4. Unhide the underlining input tags. The selected radio button will differ from the selected input

The left and right keys are triggering the input tags to change however the display is not being updated.

@kkirsche
Copy link
Contributor

Could you post a JSBin demonstrating the isolated issue?

@mynameisstephen
Copy link
Author

@mdo
Copy link
Member

mdo commented Jun 19, 2015

Does this happen in every browser?

@kkirsche
Copy link
Contributor

@animafact please don't post ads / links to third party sites unrelated to the issue.

@mdo I believe so, or at least seems to in Chrome of OS X — Assuming that I understood correctly that left and right moves the active class and prevents the user from selecting the focused element (via space bar) but does not change the actual active radio, which is the behavior I experienced in the JSBin

@mynameisstephen
Copy link
Author

@kkirsche @mdo Hmm Firefox seems to be the only browser working correctly. Looks like Chrome and IE differ in behavior. IE will change the radio button on left and right keys but won't update the display while Chrome will update the display but won't update the radio buttons.

@kkirsche
Copy link
Contributor

My guess is that this is being caused somewhere in https://github.com/twbs/bootstrap/blob/master/js/button.js#L56-L72

Removing the JS solves the value not moving but stops the active class from moving with the value. I'd need to dig in a little deeper to identify the exact cause in this

@kkirsche
Copy link
Contributor

Odd... in a further stripped JSBin where I only load the button JS, this seems to prove opposite. Overlap with another JS component potentially? — http://jsbin.com/tojiro/edit?html,css,js,output

@mynameisstephen
Copy link
Author

Ah, JSBin latest for bootstrap is still pointing to 3.3.4. Here is one that points to 3.3.5 - http://jsbin.com/gehiyohamu/edit?html,css,js,output - Chrome is fixed but IE11 still has the issue.

I'm guessing Chrome wasn't working in 3.3.4.

@mynameisstephen
Copy link
Author

Had a quick look at it, IE11 no longer triggers the click event when the left and right arrows are used (IE10 works fine). So this line in the button-data api is never triggered,

  $(document)
    .on('click.bs.button.data-api', '[data-toggle^="button"]', function (e) {

Might need to listen to a change event on the radio inputs instead.

@cvrebert cvrebert added the js label Jun 19, 2015
@cvrebert cvrebert changed the title IE11 radio button groups display differ from underlining input state IE11 radio button groups display differ from underlying <input> state Jun 19, 2015
@cvrebert cvrebert added the v3 label Aug 19, 2015
@patrickhlauke patrickhlauke self-assigned this Apr 5, 2016
@patrickhlauke patrickhlauke changed the title IE11 radio button groups display differ from underlying <input> state IE11 radio button and checkboxes using button plugin don't work correctly when navigating with keyboard Apr 14, 2016
@patrickhlauke
Copy link
Member

Investigated this a bit further, and - unless I'm missing something - the radio buttons and checkboxes (using the button plugin) work as they should in firefox, chrome and edge, but do fail in IE11 (with a mismatch between what visually is being given the .active class and what is actually checked/enabled. will work on further tests and possible resolution, but for v4 we may move to a much cleaner implementation that's less reliant on brittle JS, as mentioned by @cvrebert ... so for now I'll primarily work on the v3 side of this bug

@mdo
Copy link
Member

mdo commented Sep 5, 2016

Bootstrap 3 is no longer being officially developed or supported.

All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!

<3,
@mdo and team

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

No branches or pull requests

5 participants