Maciej

> Although I totally support the whole idea, TBH, I'm not sure where to start. Maybe the editor could expose these utils somewhere and then the inspector would discover whether...

> We cannot merge this without the research as pointed out in [#1749 (comment)](https://github.com/ckeditor/ckeditor5-engine/pull/1749#issuecomment-504986200). Thanks bisect & git log master :D I feel so bad for not digging it properly...

@scofalik & @oleq: OK so after some fiddling I can see that this check is done for markers case mostly. The placeholder must be visible when there are markers in...

After F2F talk with @Reinmar I'll updat this PR with checks in the schema so the `needsPlaceholder()` method will also get `editingController`.

@Reinmar I'm working on the rewrite so the `needsPlaceholder()` function would check model, not the view. This looks like a bigger change because the `enablePlaceholder()` function and some other functions...

Guys, so the `RawElement` would play nice here (https://github.com/ckeditor/ckeditor5-engine/issues/1643). Am I right? From what I can see it would act similarly as `UIElement` - it should allow creating custom HTML...

> What is the status of this PR ? I'm going to implement `RawElement` or whatever it would be called. At the moment the work is staled.

Hello @AnJooCo – you should be able to configure Jest to transpile CKEditor 5. See [here](https://github.com/ckeditor/ckeditor5-angular/issues/217#issuecomment-824874894) or [here](https://stackoverflow.com/questions/66474661/using-ckeditor-with-angular-and-jest/67214872#67214872).

> Also see: #225. Oh, that's an even better one. Pitty that it wasn't the first result in a web search :upside\_down\_face: I wouldn't have to dig into Jest documentation...

Also if I click a button again the button will get invalid state (default) while after a while (500ms or so ;) ) the a11ychecker UI loads: