Transact!! Only updates the one component. For the cursor jumping there were some options about raw /wrapped inputs I don't remember. Pejska someone knows...

Jakub is right about the targeted rendering. The only way it can work is to render just the component target. The internals of transact!! keep the calling thread and use React/setState behind the scenes, so it should be equivalent to using component local state. That said, the “accepted” React answer is to use Component local state (or hooks useState). If that still doesn’t work, perhaps React doesn’t yet work well with contenteditable? I’d try component local state, and if that doesn’t work, I’d look for React issues/stack overflow questions.

You can certainly skip the UI refresh and update the db atom with a swap if you want to. There are no hard rules as long as you know what you’re doing. The trick is that if something else (async load finishes from some other interaction) happens you may get a render anyway.

I assume you watched the grokking fulcro video on inputs? I mean, it sounds like you understand it well enough.

I did watch the video, but probably a lot I still don't understand. I didn't get that :refresh cannot work with transact!!, thanks. > The trick is that if something else (async load finishes from some other interaction) happens you may get a render anyway. Hm, thanks, going to keep that in mind. So, no way to tell Fulcro something like: "refresh all components with this ident except the one I'm calling this function from?" 🙂 Ah, probably going to have to deal with the cursor manually, anyway.

You can only refresh subtrees. Depending on your choice of renderer, you can tell Fulcro to do a targeted refresh by ident, but it will be the subtree of every component with that ident.

or you can plug your own renderer, which is pretty simple, and do whatever you want…but I think this is more a React problem than a Fulcro one.

Thank you, Tony.

welcome

one thing to double check is that your'e not using wrapped inputs (shadow config: :compiler-options {:external-config {:fulcro {:wrap-inputs? false}}}

contenteditable isn't an input @U051V5LLP

and wrap-inputs doesn't actually matter if it were. The transact!! does synchronous processing, which means that the props come back to the component immediately. Using wrapped inputs in that case is fine, it's just you can shave off a very small amount of processing in your rendering if you use raw inputs...but in hindsight it is so small as to be insignificant, and the option is kinda useless 😛

ooh right, whoops