Has anyone had this problem or know what it might be about: https://groups.google.com/forum/?fromgroups#!topic/reagent-project/hB3ZLgqdD4M

@mikethompson looks like @yogthos has solved the issue?

yeah it was caused by an old React version in devcards

Not sure if this is the right place to ask, but with this library

https://github.com/cljsjs/packages/tree/master/semantic-ui-react

controlled inputs fields move the cursor to the end of the input on every edit

Does anyone know what might be going on?

it doesn't seem to be an issue here, in the example at the bottom of the page with a controlled form

https://react.semantic-ui.com/collections/form

@urbank I’ve noticed that calling reagent/flush after you store the input in the atom usually solves the issue

I’ve had a similar issue with the material ui library

@mihaelkonjevic Hm, yup that solved it. Any idea what would be causing this? It isn't an issue with a regular :input element

@urbank it's the common problem with React inputs and async rendering, explained here for example: https://stackoverflow.com/questions/28922275/in-reactjs-why-does-setstate-behave-differently-when-called-synchronously/28922465#28922465

and Reagent has some built-in magic that fixes :input

I'm using React-bootstrap and had to write the helper like this to make inputs work: https://gist.github.com/metametadata/3b4e9d5d767dfdfe85ad7f3773696a60

@metametadata I see. Hm, might have to do something like that. Or I suppose reagent/flush

does the react render order has anything to do with z-index?

I find the components are drown on top of other elements with higher z-index

@metametadata thanks for sharing that gist, that type of solution could solve a bunch of input related problems

same with react-native inputs