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
I don't have time left to isolate the issue, so I hope it's reproducable...
I ran into this:
Gotta container with focusable-items, where I select one by focusManager.next().
Now, I refresh the container with new content (new focusable items)
I found out the console runs into continous erroring 'TypeError: node is null'
(node-core-debug.js line 347)
I think the error occurs because focusManager.next() calls nextItem.next(itemSelector);
Perhaps the definition inside YUI's internal nodelist is here defined and I ripped it away:
<divid='container'><!-- has focusmanager plugged in --><divid='insidecontainer'><inputtype='text' value='1' /><!-- focusable item --><inputtype='text' value='2' /><!-- focusable item --></div></div>
insidecontainer.destroy();// <-- removing this line will make the error disappearinsidecontainer.setHTML(newContent);
Thus, the error occurs when I manually call insidecontainer.destroy();
The error also does not appear when I focus by mouseclick. This made me think focusManager.next() had some code that interferred.
Regards,
Marco.
The text was updated successfully, but these errors were encountered:
Ryan,
I don't have time left to isolate the issue, so I hope it's reproducable...
I ran into this:
Gotta container with focusable-items, where I select one by focusManager.next().
Now, I refresh the container with new content (new focusable items)
I found out the console runs into continous erroring 'TypeError: node is null'
(node-core-debug.js line 347)
I think the error occurs because focusManager.next() calls nextItem.next(itemSelector);
Perhaps the definition inside YUI's internal nodelist is here defined and I ripped it away:
Thus, the error occurs when I manually call insidecontainer.destroy();
The error also does not appear when I focus by mouseclick. This made me think focusManager.next() had some code that interferred.
Regards,
Marco.
The text was updated successfully, but these errors were encountered: