GitLab

This CL takes another step toward having selection change logic consider
full selection instead of updating line and state separately with
assumed NORMAL state default. The API is preserved for now but behavior
changes slightly in a way that should, long term, be more efficient
than doing event handling in duplicate. In particular, the goal is to
have result views only update on selection change once instead of once
on line change and then again on state change.

Bug: 1046523
Change-Id: I6c94db73d4997241275e4a1b62b75272611c166a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134917Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Tommy Li <tommycli@chromium.org>
Auto-Submit: Orin Jaworski <orinj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#756433}