var node = tree.getNodeById( 'Joe Blow - HR' );
node.ensureVisible();
I've tried working around it by ensuringVisible/expanding all the parents from root down,
before the node itself, but the root+1 level barfs the same as a deeply nested node
(this is the trace above, where ynode-73 is the root id).
Any help/hint appreciated,
--dan
There was one scroll issue with tree a way ago and it was browser dependent. Try to search for it but I guess it has been fixed.
Anyway, post the full code so I can test it and if it's a bug in Ext to file it in the official bug list.
Do you call ensureVisible after the tree is rendered?
Do you call ensureVisible after the tree is rendered?Hey Saki,
Yes, I do, as a callback after rendering.
I've even added a 1 second defer to see if it was latency.. but it wasn't.
The tree in question is 3 levels. The expansions work (visibly, when I manually
scroll after the error), but the scroll doesn't.
The ability to expand/scroll to a certain node is kinda key to the whole
thing I'm doing. If this error/bug is too cryptic, I'd be very interested in any
workarounds you might suggest... unlike most stuff I usually code around,
this I can't let go ... ;)
Many thanks for your help, and looking forward to my V8 moment :D,
--dan
There was one scroll issue with tree a way ago and it was browser dependent. Try to search for it but I guess it has been fixed.
Anyway, post the full code so I can test it and if it's a bug in Ext to file it in the official bug list.Hey Saki,
I'm aware of the key-nav issue with column trees, if that's what you're referring to.
That isn't an issue here.
I cannot post the full code, but here's a simplified example that produces
the same error. You'll only have to edit the paths to Ext ...
The behavior seen is this: tree is rendered into container that is only
tall enough to see the un-expanded first-level children of a non-displayed root.
After 5 seconds, the ensureVisible is called and the path to the node is
expanded, but the scroll to that node is where the aforementioned error occurs.
If there's a flaw in how I'm building the nodes (omitting a required field that
supports scrollTo) or something else amiss, I'd be grateful for the heads-up.
Please let me know if I can provide anything else ...
Your help is appreciated,
--dan