Closed
Bug 1482017
Opened 6 years ago
Closed 6 years ago
Split HTMLEditor::SetCaretAfterElement() for internal use
Categories
(Core :: DOM: Editor, enhancement)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
mozilla63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
No description provided.
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
We need to make it possible nsIHTMLEditor::SetCaretAfterElement() to distinguish
if it's called by outer class or editor itself. Therefore, this patch creates
CollapseSelectionAfter() for internal use.
Comment 4•6 years ago
|
||
Comment on attachment 8999501 [details]
Bug 1482017 - part 1: Create HTMLEditor::CollapseSelectionAfter() for internal use of nsIHTMLEditor::SetCaretAfterElement()
Makoto Kato [:m_kato] has approved the revision.
Attachment #8999501 -
Flags: review+
Comment 5•6 years ago
|
||
Comment on attachment 8999500 [details]
Bug 1482017 - part 0: Add automated tests for nsIHTMLEditor.setCaretAfterElement()
Makoto Kato [:m_kato] has approved the revision.
Attachment #8999500 -
Flags: review+
Assignee | ||
Comment 6•6 years ago
|
||
Assignee | ||
Comment 7•6 years ago
|
||
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/b6f1266dd6c5
part 0: Add automated tests for nsIHTMLEditor.setCaretAfterElement() r=m_kato
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/581fb40d63fb
part 1: Create HTMLEditor::CollapseSelectionAfter() for internal use of nsIHTMLEditor::SetCaretAfterElement() r=m_kato
Comment 10•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b6f1266dd6c5
https://hg.mozilla.org/mozilla-central/rev/581fb40d63fb
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Assignee | ||
Updated•6 years ago
|
Blocks: add-scriptable-editor-API-tests
You need to log in
before you can comment on or make changes to this bug.
Description
•