Open Bug 1874088 Opened 1 year ago

Make `HTMLEditor` adjust selection ranges first if selection is in non-void element but its contents shouldn't be editable

Categories

(Core :: DOM: Editor, defect)

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

People

(Reporter: masayuki, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: parity-chrome)

Like <progress> and <meter>, some container elements are replaced with specific content. Therefore, modifying their content won't show. Additionally, it seems that Chrome selects the element before handling edit action. I think that we should follow it for avoiding complicated situations.

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