Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
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.

Ext.data.TreeStore.filterNodes incorrectly keeps empty nodes in search results #1871

Copy link
Copy link
@fabriciomurta

Description

@fabriciomurta
Issue body actions

Found: 5.3.0
Ext.NET forums' thread: TreePanel filter empty container disappear by click

The Ext.NET's own tree filtering facility overridden in Ext.tree.Panel.filterBy() (ultimately calling Ext.data.TreeStore.filterNodes()) incorrectly keeps empty nodes shown even if they have no matching children in the tree.

This causes the node, if interacted with (expading/collapsing), to refresh and finally "vanish" from the tree, making a filtered tree unreliable.

The issue is bound to an Ext.NET specific feature but it seems to have been introduced due to Sencha's changes in API since at least Ext JS 6.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.