You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 9, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 9, 2024. It is now read-only.
Calling .getRange() on a buffered Store throws a JavaScript error #1244
I'm afraid the Ext.NET examples affected by this issue have a fixed height set up on them, yet the error was still reproducible at that time. So, as stated by Daniil above, SelectionMemory was disabled for buffered stores, to inhibit this issue from happening.
The ExtJS 6.2.2 and 6.5.0 fixes does not address the issue if the commit here is undone.
So another ExtJS test case and another ExtJS sencha thread would be required to properly track this issue. Reverting this back to "extjs-test-pending" and removing the reference to Sencha forum thread in the initial comment until a proper issue is logged. At least, the Sencha thread mentioned above reproduces the same issue in another situation, so a proper test case would be required.
Original sencha thread being detached from this issue: https://www.sencha.com/forum/showthread.php?304363
The Ext.NET fix (which just disables the functionality if a buffered store is used) will not be reverted, as it worked well this far.
Activity
fabriciomurta commentedon Apr 23, 2016
Update: Issue still open after ExtJS 6.0.2 release.
khchine5 commentedon Sep 24, 2016
Hi all,
Try to set the height of the grid. It could fix the issue.
fabriciomurta commentedon Sep 29, 2016
Hello @khchine5! Thanks for your feedback!
I'm afraid the Ext.NET examples affected by this issue have a fixed height set up on them, yet the error was still reproducible at that time. So, as stated by Daniil above, SelectionMemory was disabled for buffered stores, to inhibit this issue from happening.
fabriciomurta commentedon Jan 6, 2017
Update: Issue still open after ExtJS 6.2.1 release.
fabriciomurta commentedon Jul 22, 2017
Update: Sencha issue EXTJS-23373 allegedly fixed in ExtJS 6.2.2 release.
fabriciomurta commentedon Jul 22, 2017
The ExtJS 6.2.2 and 6.5.0 fixes does not address the issue if the commit here is undone.
So another ExtJS test case and another ExtJS sencha thread would be required to properly track this issue. Reverting this back to "extjs-test-pending" and removing the reference to Sencha forum thread in the initial comment until a proper issue is logged. At least, the Sencha thread mentioned above reproduces the same issue in another situation, so a proper test case would be required.
Original sencha thread being detached from this issue: https://www.sencha.com/forum/showthread.php?304363
The Ext.NET fix (which just disables the functionality if a buffered store is used) will not be reverted, as it worked well this far.