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

Fix radio and checkbox keyboard handling in .btn-group #16404

Merged
merged 2 commits into from
May 3, 2015
Merged

Fix radio and checkbox keyboard handling in .btn-group #16404

merged 2 commits into from
May 3, 2015

Conversation

patrickhlauke
Copy link
Member

Fix for problem that emerged from #16226 (.active class not actually
being applied) and expansion of the script to also correctly handle
keyboard interaction with checkboxes in data-toggle="buttons" groups

Also includes removal of an apparently broken/vestigial unit test which tested a scenario not covered by our documentation (and logic)

Fix for problem that emerged from #16226 (`.active` class not actually
being applied) and expansion of the script to also correctly handle
keyboard interaction with checkboxes in `data-toggle="button"` groups
Overall logic for this test appears broken, possibly relating to an
older version of Bootstrap that did not require explicit
`data-toggle="button"` on single toggle buttons?
@patrickhlauke
Copy link
Member Author

/cc @cvrebert @fat for review

@twbs-savage
Copy link

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED

Commit: 0c1daaf
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/60825110

(Please note that this is a fully automated comment.)

@patrickhlauke patrickhlauke added this to the v3.3.5 milestone May 2, 2015
@patrickhlauke
Copy link
Member Author

Ok, I may jump the gun a bit (instead of waiting for review), but as the current state of radio buttons/checkboxes for keyboard users is essentially broken (and not really fixed by my previous PR, which was merged), I'd like to fasttrack this fix (I'm more concerned about potentially removing a unit test that is, in fact, still needed...but from my research above it doesn't appear to; happy to eat humble pie later and undo that particular removal if it turns out I was wrong)

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

Successfully merging this pull request may close these issues.

2 participants