Looks like we cannot reproduce this. Please provide another test case to reproduce this issue.
-
Sencha User
When Ext.FocusManager enabled, selecting checkbox/radiobutton in Chrome doesn't work.
Ext version tested:
- ext-5.0.0.736
- ext-4.2.1.883
Browser versions tested against:
- Chrome/Chromium 33 (Linux) (BUG), Chrome 34 Windows 7 (BUG)
- FF 28 (WORKS FINE)
Description:
- When Ext.FocusManager is enabled for keyboard navigation, then checkboxes and radiobuttons can't be selected with spacebar/enter on Chrome browser. When FocusManager is disabled, then everything works fine. Not really sure if this is Ext bug or Browser bug, but anyway doesn't work on all of the latest ExtJs versions. On Firefox everything works just fine.
- Fiddle: https://fiddle.sencha.com/#fiddle/529
Steps to reproduce the problem:
- Create checkbox or radiobutton group
- Enable FocusManager
- Click on created element, navigate with arrows, select element with spacebar/enter
The result that was expected:
- The checkbox/radiobutton gets selected.
The result that occurs instead:
- Nothing happens on Chrome browser
This is a critical bug for me, because I need keyboard naviagation in my appliaction. I am using 4.2.1, but reported for 5.0 in case you won't fix the old Extjs versions.Can someone suggest a workaround? Thank you.
-
Using Chrome 34 on Windows 7 I am able to change the value by clicking.
Screen Shot 2014-04-18 at 9.36.39 AM.png
-
Sencha User
Yes, of course you can select it by clicking, but I explicitly said that you can't do it with keyboard (the main reason why FocusManager is needed)....
When Ext.FocusManager is enabled for keyboard navigation, then checkboxes and radiobuttons can't be selected with spacebar
-
Sencha User
BUMP. This is reprodusable, please use keyboard navigation and try to select WITH KEYBOARD not mouse.
-
Sencha User
https://fiddle.sencha.com/#fiddle/afb
1. put the focus on the text field
2. press Tab
Result: nothing happens.Expected: should move the focus.
-

Originally Posted by
iceteagroup
I'd classify that as a separate issue. Please open a new thread.