Results 1 to 2 of 2

Thread: [CLOSED][3.??] TreePanel:Using "/" as id for node conflicts with select/expandPath

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Ext User
    Join Date
    Jun 2009
    Vote Rating

    Default [CLOSED][3.??] TreePanel:Using "/" as id for node conflicts with select/expandPath


    I have a simple tree I dynamically load by using Ajax calls. I prefer to have the root be called either nothing (empty string "" or null), or "/". In the former case, ExtJS will assign a name to it anyway (xnode-3 or something similar). In the latter case, the name is correctly assigns but the expandPath() and selectPath() functions do not work properly. Obviously this is because I use "/" as path separator as well and the split() functions can't distinguish.

    This isn't any major problem, but just wanted to point out this might be confusing for people. Is it an idea to allow root nodes be called ""? So that if I have nodes "A" and "B", their paths become "/A" and "/B"?

  2. #2
    Sencha Premium User evant's Avatar
    Join Date
    Apr 2007
    Sydney, Australia
    Vote Rating


    The tree uses the id under the hood for a number of things, which is why nodes require an id. As you've suggested, using "/" as the id for a node isn't a good idea. At this point I wouldn't consider this a bug, just a behaviour to be aware of. Going to mark this as closed.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts