Krzysztof Krztoń

> All looks great 🎉 but after recent decision of changing the css file names please change all imports from: > > ``` > import 'ckeditor5/index.css'; > import 'ckeditor5-premium-features/index.css'; >...

Closing in favor of #40, all the work will be concluded there.

> @Witoso I suspect that it's reproducible on old installation methods, actually. Needs to be verified. Yes, I checked with old installation methods and stable `ckeditor5-react` package and there is...

I stumbled upon this same issue today. I prepared demo for rerepo and then found this issue... Anyway, I'll share it, maybe it could be helpful - https://stackblitz.com/edit/1haefu?file=main.js. https://github.com/user-attachments/assets/575164a2-a75f-4135-bc86-d88175111a74 **What'...

I started looking into this PR and the logic in general (well, wanted to understand what's going on before looking into changes itself). Couple of general remarks (not related to...

Found another issue while testing. Not related to the changes from this PR though, reproducible on `master` too - https://github.com/ckeditor/ckeditor5/issues/16648.

> Fix (find-and-replace): Do not replace only the first found word when using it with `Track Changes` plugin. > > MINOR BREAKING CHANGE (find-and-replace): The `FindCommand#execute` now accepts a `findCallback`...

I stumbled upon this issue when working on new collaboration samples. But for me it happens when leaving "revision history view/editor" back to editor content (both when using "Back to...

@Mati365 I can confirm it work fine with #480 👍🎉