Closed
Bug 1947109
Opened 29 days ago
Closed 20 days ago
Add some API to `nsTextFragment`
Categories
(Core :: DOM: Editor, enhancement)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
137 Branch
Tracking | Status | |
---|---|---|
firefox137 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(1 file)
nsTextFrament
has 2 different storage. Therefore, scanning its content with nsTextFrame::CharAt
is slow. Additionally, it's really useful if there are APIs which return the first char and the last char for the editor.
Assignee | ||
Comment 1•29 days ago
|
||
nsTextFragment
has 2 different storage. Therefore, scanning its content with
nsTextFragment::CharAt()
is slow. Additionally, it's really useful if there
are APIs which return the first char and the last char for the editor.
Updated•29 days ago
|
Assignee: nobody → masayuki
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/e95f3e6f1e26
Add some APIs to `nsTextFragment` to make its users easier to read r=jjaschke,dom-core
Comment 3•20 days ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 20 days ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•