Empty inline editables in widgets become inaccessible

[xmo]

Part of: #10974.

I'm not actually sure this is a valid bug as I'm somewhat uncertain the use case is supposed to be supported: inline widgets are supported, but inline editables are not by default although they generally work (and — I think — make sense in an inline widget).

Anyway, if one sets up inline editable parts in a widget and removes said parts's (textual) content, the widget *and part* remain, but the part becomes invisible and essentially un-editable: the usual outline disappears with the last visible character.

See attached document for a test case, inline widget content is the inline editable part, if the cursor is set to its end then the user backspaces until all text is removed it seemingly disappears entirely. Checking the DOM shows the widget and part are still there (and the drag & drop handle remains visible), but there's more or less no way to re-insert content in the widget.

[Piotrek Koszuliński]

That's why using inline nested editables is not supported.

What you could try is a hack with CSS3 :empty:after{ content: '(some invisible char)' } or setting editable's display to inline-block or adding padding.

[Piotrek Koszuliński]

I'm confirming it as a new feature and part of #10974. Maybe one day we'll support inline editables.