Closed bmblb closed 1 year ago
This is another one that is on locker service rather than this library. As you can see, that's a SecureElement target in the screenshot above, that indicates that this is coming from Locker, which is not doing the proper unwrapping of those proxies before calling the underlaying DOM api. Feel free to open a bug for that team.
Could you please tell me where to report that problem?
cc @seksenov
Closing this as it is unrelated to LWC, please open a Salesforce Stack Exchange question or Salesforce Case if you're still experiencing this issue.
Description
Failed to set the 'currentNode' property on 'TreeWalker': The provided value is not of type 'Node'
Steps to Reproduce
Expected Results
Current node element should cycle item 1 -> item 2 -> item 3 -> item 1 -> ...
Actual Results
stops on item 3
Browsers Affected
Doesn't look browser-specific
Version
Possible Solution
Additional context/Screenshots raw is original TreeWalker class, but value is an element wrapper. Smth like this is probably missing somewhere: