-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ITML <Error>: Invariant Violation: processUpdates(): Unable to find child 0 of element. #13
Comments
let me get back to you later ;) |
Hey @ramitos, any update on this? I'm running into similar issues, where pretty much all dom mutations fail, I either get the same error as above or:
|
+1 |
The issue is that React expects |
Made some progress by using Browserify to inject |
@boffbowsh I haven't had time to look at this, but |
Yes indeed, I think I posted that after a lot of yak shaving. The root issue though is the |
From my experience the DOM implementation looks like it's not completely implemented. Even using list.item(X) syntax, modifying the DOM in some templates doesn't actually reflect itself visually either. This makes sense as the intention behind TVML looks like it encourages you would generate the templates server side and navigate between documents (web 1.0 style). I built the Townske tvOS app using TVML my own React like framework I wrote for it, but will most likely rewrite it in swift (or React Native if proper support is picked up), as the restrictions imposed design wise by TVML and the lack of a fully functional DOM makes it quite difficult to bend it to your own needs. |
At present the whole TVJS seems a lot buggy and half baked when it comes to DOM api implementations. For instance something as trivial as Having said that, the ReactJS concept of virtual DOM and diff to issue partial updates to the DOM, may not work in many cases. The best bet is to regenerate the whole document and use |
I do not know how to check for
.1ljayehovsw.1.0.0.1
, can't find a way to debug this. But all my tags are closed correctly. This happens when I try to render<lockup>
within<section>
in a<grid>
.Snippet:
The text was updated successfully, but these errors were encountered: