Opened 6 years ago

Last modified 6 years ago

#10973 confirmed New Feature

Empty inline editables in widgets become inaccessible

Reported by: xmo Owned by:
Priority: Normal Milestone:
Component: General Version:
Keywords: widgets inline Cc:

Description (last modified by Piotrek Koszuliński)

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.

Attachments (1)

index.html (1.1 KB) - added by xmo 6 years ago.

Download all attachments as: .zip

Change History (3)

Changed 6 years ago by xmo

Attachment: index.html added

comment:1 Changed 6 years ago by 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.

comment:2 Changed 6 years ago by Piotrek Koszuliński

Description: modified (diff)
Status: newconfirmed
Type: BugNew Feature

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

Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy