Shane Friedman

You'll have to specifically use `"@nytimes/react-prosemirror": "0.3.0-beta.0"` to get the new architecture!

Darn, ok, thanks for the report! I'll take a look; it's possible that that version just doesn't have the latest code, because I did actually test with Japanese IME input...

Ah! I was able to reproduce this on Chrome; it seems to be a difference in how Chrome and Firefox handle... something! Not sure yet, but this is very helpful....

Oh great, that's good to know! Starting a new line is definitely its own edge case in this situation

That's the plan! But I can't make any promises about timing, unfortunately. We're still working out some significant high level decisions about the approach.

Hey @saranrapjs, while you're at it: @ilyaGurevich took a stab at this a little while back but it seems like there are still issues with IME input in the main...

Thank you for the detailed bug report, @konstantinmuenster! This does make sense; the React/ProseMirror integration renders the node views in a layout effect, so any commands that try to synchronously...

I'm also experiencing this issue. @Shadoxity I don't know if this is happening to you as well, but even after following your workaround, AL doesn't actually adapt the new lights....

Ah yeah, turns out this was actually a separate issue; I was targeting my lights' devices rather than entities with the light.turn_on service, so Adaptive Lighting wasn't intercepting it.

I'm just seeing that it looks like this may have been resolved in `@quasar/[email protected]`; is it possible to backport this upgrade to the stable `v1.9.x` releases, or was there a...