Make ComputePositionForNodeRemoval() to work correctly for after node/children position
This patch changes |ComputePositionForNodeRemoval()| to work correctly for after node/children position to make |SelectionEditor| relocates base and extent positions correctly. Before this patch |ComputePositionForNodeRemoval()| returns position after removed node as child index in parent, e.g. parent@child+1. After this patch |ComputePositionForNodeRemoval()| returns parent@child. Example: <div><a></a><b></b></div> remove <a> <div><b></b></div> When removing <a>, position after <a> should be relocated to <div>@0. Bug: 1145595 Change-Id: Ibd5f30b52cb10ba066dfeca3fbf9f1d5bef6c77b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558123 Auto-Submit: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#830898}
Showing
Please register or sign in to comment