caret and characters insertion are erratic in a contenteditable with tinyMCE on Android
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
People
(Reporter: karlcow, Assigned: m_kato)
References
()
Details
(Whiteboard: [webcompat][geckoview])
Attachments
(2 files)
This is https://webcompat.com/issues/17764
- With Firefox 68 Nightly on Android
- Go to https://minecraft.curseforge.com/projects/better-builders-wands
- sign in (top right menu. Creating an account with twitch is free)
- scroll down the page until reaching the comment section.
- click on Reply on one of the comment.
- Notice that the caret is set automatically on the line after the In reply to…
- Request the focus to get the keyboard
- Type a couple of characters
Expected:
The text is added like in Chrome on Android.
Actual:
The caret is jumping to the first character of the first line.
Any subsequent character input happens in random order.
This is NOT reproducible on
- Chrome Android,
- Firefox Desktop,
- Firefox Desktop + Firefox Android UA + RDM.
Assignee | ||
Comment 1•6 years ago
|
||
I guess that GeckoEditable doesn't insert text to valid position. This is GeckoEditable in Android, not editor issue.
Comment 2•6 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Comment 3•6 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Assignee | ||
Comment 4•5 years ago
|
||
This might not Android issue. GekocEditable listens selection change via editor, but no received. When debugging desktop too, selection change isn't fired to widget. Root cause is editor? But I cannot create easy test case yet...
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
After editor is attached, if pres shell is re-created, this issue occurs. editor already attaches to selection, but selection is re-created by new pres shell. So editor must attach new selection. (or tear down editor on destroying pres shell)
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
Comment 9•5 years ago
|
||
bugherder |
Comment 10•5 years ago
|
||
I think we can let this ride the trains given that it's not a new issue.
Description
•