This bug has been introduced in ExtJS 4.2.0 and automatically came to Ext.NET v2.2. It is fixed in ExtJS 4.2.1 and, accordingly, will be fixed in the next Ext.NET v2.3 release, which should appear soon.
Here you can find some details about the bug and thoughts about a possible solution.