Open Bug 1919510 Opened 18 days ago Updated 17 days ago

contentEditable cursor oddities when images have "display:block"

Categories

(Core :: DOM: Editor, defect)

Firefox 130
defect

Tracking

()

People

(Reporter: jitbit, Unassigned)

References

()

Details

(Keywords: parity-chrome)

Steps to reproduce:

I have a content-editable div with an <img> tag inside it. The img tag has "display:block" applied by global CSS file.

Actual results:

There's no way to move the cursor AFTER the image.

Expected results:

I have to be able in insert text after the image, just like in Chrome/Safari.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Editor' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Editor
Product: Firefox → Core

I am quite sure I've seen similar bugs before, i.e, the cursor position is placed at the front rather the end. However, I am not sure how we track them at the moment.

Masayuki, do you mind link this to the correct bug? Or Is it just parity-chrome? Thanks!!

Severity: -- → S3
Flags: needinfo?(masayuki)

Should be same as bug 1674359, but this must be simpler than it.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(masayuki)
Keywords: parity-chrome
OS: Unspecified → All
Hardware: Unspecified → All
See Also: → 1674359

FYI: Putting a <br> after the last block content provides a placeholder to put caret.

You need to log in before you can comment on or make changes to this bug.