editor methods which return child at offset should use RangeBoundary instead of a set of container node, offset and child node

ASSIGNED
Assigned to

Status

()

Core
Editor
ASSIGNED
15 days ago
9 days ago

People

(Reporter: masayuki, Assigned: masayuki)

Tracking

(Depends on: 1 bug)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox58 affected)

Details

Such methods may still have regressions and really error prone because of difficult to keep syncing container/offset and child node. We should use EditorDOMPoint which starts to sync these information automatically since bug 1408544. (And maybe this bug needs to change something of RangeBoundaryBase in this bug.)
Depends on: 1414713
EditorBase::FindBetterInsertionPoint(), EditorBase::InsertTextImpl(), WSRunObject::InsertText() (bug 1406482)
EditorBase::GetPriorNode(), EditorBase::GetNextNode(), HTMLEditor::GetPriorHTMLNode(), HTMLEditor::GetNextHTMLNode() (bug 1407305)
DeleteRangeTransaction::CreateTxnsToDeleteBetween() (bug 1407352)
EditorBase::SplitNodeDeep(), HTMLEditor::InsertNodeAtPoint() (bug 1407447)
CreateElementTransaction::CreateElementTransaction(), EditorBase::CreateTxnForCreateElement(), 
EditorBase::CreateNode() (bug 1407854)
InsertNodeTransaction::InsertNodeTransaction(), EditorBase::CreateTxnForInsertNode(), EditorBase::InsertNode() (bug 1408125)
Depends on: 1415062
Depends on: 1415414
Depends on: 1415445
Depends on: 1415509
Depends on: 1415800
Depends on: 1416099
No longer blocks: 1408125
Depends on: 1413181
You need to log in before you can comment on or make changes to this bug.