Should TextIterator emit non-empty text with collapsed text range? |
|||
Issue descriptionThere are some cases where TextIterator emits non-empty text, but TextIterator::Range() returns a collapsed range. This can happen regardless of whether the anchor node of the emitted text is a text node or not. We should investigate whether this should be allowed, and if yes, what it means.
,
Jan 10 2018
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by xiaoche...@chromium.org
, Sep 20 2017