r0man
r0man
@FreekPaans The IE bug should be fixed in the next version of React. Then we can remove the workaround code and this should behave as expected. There's also a similar...
@DjebbZ No, not yet. I haven't investigated if the IE fix is already in the latest version of React, or if this will ship with version 16.
@gfredericks I can't reproduce this. Your example works for me. Do you have the proper externs for React in place?
@gfredericks Then this might be the problem? sablono itself doesn't have any annotations that could be picked up by `:infer-externs`. Did you try `:pseudo-names true` to find out which variable/fn...
@pedrorgirardi Yes, if you have a good idea how to fix this, and can test this in multiple browsers I would love to get help on this. I don't have...
@pedrorgirardi If I remember correctly this was needed for libraries like om that render on requestAnimationFrame. I'm afraid I don't remember all the details. Do you have a link to...
@pedrorgirardi As @piranha mentioned I think we should keep the wrapped inputs to support libs that use RAF for rendering. I'm afraid I don't have time to look into this...
@rauhs I thought about this as well. I think it's also possible in React versions before 0.14, provided the object literals have a key called `$$typeof` with the symbol `Symbol.for("react.element")`....
@rauhs I'm not sure about this "light" namespace. I think supporting a 3rd way to build React nodes is a bit too much. However, I'm still interested in the object...
@timothypratley patch welcome!