-
9 Oct 2012 3:15 AM #1
[4.1.1] Ext.menu.KeyNav continues to swallow key events after clicking an item
[4.1.1] Ext.menu.KeyNav continues to swallow key events after clicking an item
REQUIRED INFORMATION
Ext version tested:- Ext 4.1.1
- Bug present in
- Chrome 23.0.1271.17 beta-m
- Chrome 22.0.1229.79 m
- Chrome 22.0.1229.92 m
- Bug not present in
- Firefox 15.01
- Internet Explorer 9
When you dismiss a menu by clicking on a menu item, the KeyNav object tied to the menu continues to swallow key events. When dismissing the menu by clicking on the modal mask DIV this effect does not occur.
Steps to reproduce the problem:- Go to http://jsfiddle.net/6sDeP/17/
- Repeatedly press the 'up' arrow key
- Note that the events are displayed for both keyUp and keyDown
- Right click to open the Ext context menu.
- Dismiss the menu by clicking a menu item
- Repeatedly press the 'up' arrow key
- The events are displayed for both keyUp and keyDown
- Only the keyUp event appears to be handled
- A breakpoint in the Ext.menu.KeyNav "up" method is hit when the menu is no longer visible
- Setting "enableKeyNav" to false for the menu fixes the problem
- only default ext-all.css
- Windows 7
-
9 Oct 2012 7:52 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,624
- Vote Rating
- 435
Looks like you are mixing jQuery in there, have you tried a Ext JS only test? Also, not able to reproduce using Chrome 22 (stable)
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
9 Oct 2012 8:07 AM #3
I have updated the JSFiddle in the original post with an all Ext version.
Also I can reproduce the bug on Chrome 22.0.1229.79 m, and have added this to the original post.
-
9 Oct 2012 9:21 AM #4Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,624
- Vote Rating
- 435
I still cannot reproduce. I press up 5 times and I see 'keyUp - 9'. I then right-click to get the context menu and click on the first item. I then press up once and I then see 'keyUp - 11' as the keyDown was 10
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
9 Oct 2012 9:47 AM #5
I have added another version of Chrome we have confirmed the bug with
We have also discovered that if you click on the "Result" window after clicking a menu item the problem does not occur. This means that the steps are now- Right click to bring up the context menu
- Click on the menu item
- Do not click the mouse again
- Press the 'up' key again.
-
13 Oct 2012 8:42 AM #6
I can confirm the reported behavior on Chrome 22.0.1229.94 m on Win7/x64.
-
14 Oct 2012 1:48 AM #7
This is fixed in the latest code, and the problem should not occur in the upcoming releases.
Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
-
15 Oct 2012 2:22 AM #8
Verified this in the latest nightly, following the steps in post 5, both events are still handled after clicking the menu item.
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
Looks like we can't reproduce the issue or there's a problem in the test case provided.


Reply With Quote