Don't optimize NGInlineNode::SetTextWithOffset() when text content contains bidi control codes
This patch changes |NGInlineNode::SetTextWithOffset()| not to reuse existing data because we can't figure out insert position of bidi control codes before/after editing. Example: For <pre><b dir=ltr>\nXYZ</b></pre>, we have \u2066\u2069\n\u2066XYZ\u2069 after removing "\n", we have \u2066XYZ\u2069 Bug: 1039143 Change-Id: Iba443f0228bece9e8b08fc8f49d827565073d159 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991037 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Auto-Submit: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#729669}
Showing
Please register or sign in to comment