Aleksander Nowodzinski

Pros: * Aligned with the commands pane that also displays whether a command is enabled or not. Cons: * Could be a source of confusion because the user may not...

Can you write this as expected vs actual? I'm having a hard time figuring out what the problem is.

There's no such thing as a selection in the textnode in the model. `foo[]` and `foo[]` are one and the same position. So from this perspective, the inspector does not...

I came upon it and I also find it annoying, so I'm gonna give it some real priority.

Our set/get data utils use the editor view and the writer to generate the stringified data structures. For the inspector to do the same, these utils would need to be...

> * Make Insepector detect _debug_ build with exposed view/model stringifiers. We could bring the `InspectorIntegration` plugin to the editor that exposes some helpers. And these features would be available...

The `isEmptyish` check has been introduced by @scofalik in https://github.com/ckeditor/ckeditor5-engine/commit/6a66f6e5e354792e197227bf88f3c8c1b6d692e8 and solved https://github.com/ckeditor/ckeditor5-engine/issues/1018 which, in turn, was a piece of https://github.com/ckeditor/ckeditor5-engine/issues/1017. Sounds like there was a solid reason for that...

I'm for 2b. 2a would add a `ckeditor5-widget` dependency to `ckeditor5-engine` which we don't need (want?).

This could also land in the readme of the inspector.

What would it look like?