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

DefaultButton is triggered on ENTER in fields where the ENTER key has been mapped/trapped. #1220

Open
fabriciomurta opened this issue Jan 12, 2016 · 0 comments
Labels
Milestone

Comments

@fabriciomurta
Copy link
Contributor

Related forum issue: Window Close Issue

On the sample the user provided:

  1. Click the '+' button next to P.O.Box textfield.
  2. Focus (or type something) the search textfield on the window that appears
  3. Hit the 'enter' key.

Although the textfield has the 'enter' key bound for something else via KeyMap, it also triggers the window's DefaultButton (which, as it is not defined, is 'Cancel').

The problem is in Container.js, where the overrode Ext.container.Container's fireKey function does not consider any possible key mapping override to the enter key in the current event's target (actually the source where the 'enter' keypress came from).

It is necessary to track down the reason of this override and check if it is still actual. As of version 5.1.1, there are no fireKey on Ext.containter.Container.

@fabriciomurta fabriciomurta added this to the Release 3.3 milestone Jan 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants
@fabriciomurta and others