Piotrek Koszuliński

> This only occurs with two of many custom elements, the ones for `textarea` and text `input`. These are also the only "empty" elements; the ones that still work are...

Unfortunately I don't remember now what it took to handle input/textarea in the editor. I remember only that the safest way was to have a overlay covering the entire input...

Thanks for the detailed analysis :heart: If you came that far, did you perhaps also implement your solution? Do you know why this specific font creates this problem? Is there...

We discussed this during an internal meeting. Conclusions: * `setSelection()` should validate the input **before** changing anything in the model. Ideally, if you put it in try-catch, it should not...

> I am working on a VS Code extension using CKEditor5 What a cool idea :heart\_eyes: Is the plugin usable already? I'd love to install it.

Let's try this: * Touch only `DocumentSelection`. The `Selection` must allow "virtual" positions. * Add early validation with a clear error message and documentation. For now, we won't be differentiating...

I'd add that there are certainly limits to how large tables can be handled by CKEditor 5, but it's definitely not what the UI allows to insert. The UI offers...

Small status update as it's hard to track the current work based on our activity on GitHub. * It seems that the entire effort will consist of 4 main parts:...

> * Check out the snapshot of the docs from June: https://ckeditor5.github.io/misc/ime-snapshot-220610/ckeditor5/34.1.0/ If you have any feedback, especially for CJK languages, we'll appreciate if you share it here. The earlier...

FYI: the latest work is in branch `ck/11438-beforeinput-ime-research-vol1.1`. Shouldn't this PR be closed?