I have been thinking about this a little bit. Perhaps the interesting thing to me is not that the item-map might have changed some value within it between render and click, it's actually that the line item component is referring to a different item entirely, than the one it rendered.
So even though React has the correct data-reactid based on the key I gave it, and all the rendered information in the display refers to, say, Item #3, the onClick handler is referring to a different item in the list (an adjacent one), as if there's been two render phases - one that built the component from the values, and a second phase that attached the handlers to the dom node. This seems like a subtler problem than "The atom changed between render and click". The approach of pulling out values in the head of the component function seems to work, but I'm wondering if I should instead, always simply refer to items by id, rather than passing around the item "object". -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
