Thank you for reporting this bug. We will make it our priority to review this report.
-
Sencha Premium User
Editable grid tabbing diesn't work as expected
Ext version tested:
Browser versions tested against:
DOCTYPE tested against:
Description:
Steps to reproduce the problem:
- Please take a look at the above fiddle. Click the first column cell in any row and then after editor appeared press TAB key. The editor collapses but new editor doesn't appear.
- In Ext 6.0.1 it happens in IE9/10
- In Ext 6.0.0 it happens in IE9/10/11
The result that was expected:
- New editor for the focused cell should appear
The result that occurs instead:
- Old editor collapsed but new editor never showed
-
Thanks for the report. I see the behavior, but it seems to be related to this line in your test case:
Code:
ed.context.record.set('f4', value + 1);
The onEditComplete() method is private, so I'm thinking this isn't a bug. Tabbing in the cellEditing plugin example works as expected for me in all IE versions tested.
https://fiddle.sencha.com/#fiddle/123h
-
Sencha Premium User
I know it's related to calling record.set() on editing completion. But it's pretty normal scenario that editing of a column might cause chained changes of other fields of the record. And this is not because of using private onEditComplete. I modified the fiddle to use public "edit" event instead. And still the editor gets collapsed.
https://fiddle.sencha.com/#fiddle/120n
-
Yes, I see. Fortunately, it looks like it was fixed a few weeks ago. I can't reproduce with 6.0.2 nightlies after 11/18.
-
Sencha Premium User
Ah, that's good news. Thank you very much.
-
Sencha Premium Member

Originally Posted by
Gary Schlosberg
Yes, I see. Fortunately, it looks like it was fixed a few weeks ago. I can't reproduce with 6.0.2 nightlies after 11/18.
I ran into the same problem, but never had it with Chrome. Now we're short before rollout and we have a lot of IE users. What would you suggest: Switch to latest Nightly Build? Wait for 6.0.2 (ETA?)? Or could you hand out an override for this bug?
Thanks,
Dan