Ah, I wonder if it is only a problem if you have keys. I have definitely run into a problem where react complained that it was different than it expected, but those elements had keys if I remember correctly.
Thanks Diogo. On 21 November 2014 19:50, Diogo Almeida <diogo...@gmail.com> wrote: > My (complete) guess would be that it has to do with React's diffing algorithm > and how it updates the DOM. Does it matter if the virtual DOM is different > from the real DOM if it behaves essentially the same way? I imagine there > would be some changes that would mess up floatThread, such as removing and > re-adding the table, and some that wouldn't, such as changing the data in the > table. > > On a side note, this also can cause issues. For example if your floatThread > table was replaced by another table, it might still have the floatThread > changes, even if that was unintended. > > -- > Note that posts from new members are moderated - please be patient with your > first post. > --- > You received this message because you are subscribed to a topic in the Google > Groups "ClojureScript" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/clojurescript/ZBdiNQFCJHI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > clojurescript+unsubscr...@googlegroups.com. > To post to this group, send email to clojurescript@googlegroups.com. > Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
