We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
http://forums.ext.net/showthread.php?27291
update: pending: check if there's an updated Sencha issue on forums or if the issue (that still happens on Ext.NET) applies to ExtJS at all!
The text was updated successfully, but these errors were encountered:
Sencha says it's fixed in 4.2.2.1144. Needs to be tested when 4.2.2.1144 will be included in Ext.NET
Sorry, something went wrong.
Unfortunately, 4.2.2 won't be included to Ext.NET, because it is a private release. Hopefully, there will be any 4.x public release before 5.0.
Update: Sencha issue EXTJS-5957 allegedly fixed in ExtJS by the time ExtJS 6.0.2 was released.
We still have this issue according to recent examples explorer reviews:
So the original Sencha issue http://www.sencha.com/forum/showthread.php?194555 does not apply and we should seek to reproduce again in pure ExtJS or assume the bug is ours.
Removed the sencha issue link from first comment to avoid false alarms that the issue has been fixed.
No branches or pull requests
http://forums.ext.net/showthread.php?27291
update: pending: check if there's an updated Sencha issue on forums or if the issue (that still happens on Ext.NET) applies to ExtJS at all!
The text was updated successfully, but these errors were encountered: