Closed
Bug 1657270
Opened 4 years ago
Closed 4 years ago
Redesign `HTMLEditor::MayDeleteTopMostEmptyAncestor()`
Categories
(Core :: DOM: Editor, task, P2)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
81 Branch
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(5 files)
No description provided.
Assignee | ||
Comment 1•4 years ago
|
||
Depends on D85965
Assignee | ||
Comment 2•4 years ago
|
||
Depends on D85995
Assignee | ||
Comment 3•4 years ago
|
||
Depends on D85996
Assignee | ||
Comment 4•4 years ago
|
||
Depends on D85997
Assignee | ||
Comment 5•4 years ago
|
||
Depends on D85998
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/d179ec4f3379
part 1: Move `HTMLEditor::MaybeDeleteTopMostEmptyAncestor()` into new stack only class r=m_kato
https://hg.mozilla.org/integration/autoland/rev/2fc29f6624da
part 2: Split `AutoEmptyBlockAncestorDeleter::Run()` to scanning the target part and touching the DOM tree part r=m_kato
https://hg.mozilla.org/integration/autoland/rev/6017922d5be0
part 3: Split `<br>` element insertion part for empty list element off from `AutoEmptyBlockAncestorDeleter::Run()` r=m_kato
https://hg.mozilla.org/integration/autoland/rev/cc5bca926704
part 4: Split caret computation part off from `AutoEmptyBlockAncestorDeleter::Run()` r=m_kato
https://hg.mozilla.org/integration/autoland/rev/ac2c3f906e9d
part 5: Guarantee that `AutoEmptyBlockAncestorDeleter` did nothing if it returns "not handled" or an error at the caller r=m_kato
Comment 7•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d179ec4f3379
https://hg.mozilla.org/mozilla-central/rev/2fc29f6624da
https://hg.mozilla.org/mozilla-central/rev/6017922d5be0
https://hg.mozilla.org/mozilla-central/rev/cc5bca926704
https://hg.mozilla.org/mozilla-central/rev/ac2c3f906e9d
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox81:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•