Skip to content
This repository was archived by the owner on Aug 9, 2024. It is now read-only.
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

Open

Description

@DaniilVeriga

#1217.81-83

(ExtJS proper issue pending. Add the URL for the sencha thread here once it is created/found)

For now, SelectionMemory has been disabled for buffered Stores (it should be disabled), but the original issue might be wider. So, leaving it open.

Activity

  1. self-assigned this
    on Jan 25, 2016
  2. fabriciomurta commented on Apr 23, 2016

    @fabriciomurta

    Update: Issue still open after ExtJS 6.0.2 release.

  3. khchine5 commented on Sep 24, 2016

    @khchine5

    Hi all,
    Try to set the height of the grid. It could fix the issue.

  4. fabriciomurta commented on Sep 29, 2016

    @fabriciomurta

    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.

  5. fabriciomurta commented on Jan 6, 2017

    @fabriciomurta

    Update: Issue still open after ExtJS 6.2.1 release.

  6. fabriciomurta commented on Jul 22, 2017

    @fabriciomurta

    Update: Sencha issue EXTJS-23373 allegedly fixed in ExtJS 6.2.2 release.

  7. fabriciomurta commented on Jul 22, 2017

    @fabriciomurta

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions