Closed
Bug 1664109
Opened 4 years ago
Closed 4 years ago
`!= operator of `EditorDOMRangeBase` is wrong
Categories
(Core :: DOM: Editor, defect, P2)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
82 Branch
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
|
Assignee | |
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P2
|
|
Assignee | |
Comment 1•4 years ago
|
||
This is causes taking back bugs in
WSRunScanner::GetNewInvisibleLeadingWhiteSpaceRangeIfSplittingAt() and
WSRunScanner::GetNewInvisibleTrailingWhiteSpaceRangeIfSplittingAt() (I.e.,
they were fixed by bug 1647556). Therefore, this removes the odd if blocks
which are pointed with XXX comment for avoiding "regressions" (without them,
some WPTs for InputEvents.getTargetRanges() become failure).
Depends on D89582
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/0dcadb7f268f
Fix `!=` operator of `EditorDOMRangeBase` r=m_kato
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•