Closed
Bug 1572386
Opened 6 years ago
Closed 5 years ago
Editor shouldn't modify selection before deletion
Categories
(Core :: DOM: Editor, task, P3)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
mozilla80
People
(Reporter: masayuki, Assigned: masayuki)
References
(Blocks 1 open bug)
Details
Currently, when editor removes around selection, it may extend selection with nsISelectionController::CharacterExtendForDelete(), nsISelectionController::CharacterExtendForBackspace(), nsISelectionController::WordExtendForDelete() and nsISelectionController::InterLineMove().
Except the last one, they are editor specific API and not used by comm-central nor BlueGriffon so that we can move the logic into editor.
This improve performance and makes better compatibility for beforeinput event listeners since when beforeinput event is fired, selection is not modified on Chrome. However, web apps can know the range with InputEvent.getTargetRanges() unless the editor is <input> or <textarea>.
|
||
Updated•6 years ago
|
Priority: -- → P3
|
Assignee | |
Comment 1•5 years ago
|
||
Fixed by bug 1657269.
Status: NEW → RESOLVED
Closed: 5 years ago
Depends on: 1657269
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in
before you can comment on or make changes to this bug.
Description
•