Open
Bug 1714915
(cache-editing-host-first)
Opened 3 years ago
Updated 2 years ago
Make `AutoEditActionDataSetter` cache active editing host at start to handle it
Categories
(Core :: DOM: Editor, enhancement, P3)
Core
DOM: Editor
Tracking
()
NEW
People
(Reporter: masayuki, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
While handling an edit operation/command, focus may be changed by JS. In such case, we may need to modify nodes under different editing host if we compute editing host every method. And the computation cost may not be cheap if editor is in a long branch. Therefore, caching it at start, and recompute it after dispatching beforeinput and clipboard events. Then, we can get rid of redundant argument for passing editing host in various methods.
|
Reporter | |
Comment 1•3 years ago
|
||
Currently, we use different editing host (allow/disallow outside of <body>). So, we cannot fix this after fixing bug 1634351.
Depends on: editing-outside-body
|
|
Reporter | |
Updated•2 years ago
|
Alias: cache-editing-host-first
You need to log in
before you can comment on or make changes to this bug.
Description
•