Don't ignore CascadeOrigin::kNone for <summary> use-counter
I forgot to handle CascadeOrigin::kNone, which means the subsequent call to priority.GetPosition() would always return zero, and we would access the wrong value (and possibly crash). Handle that case, and add a more detailed test which verifies each origin. Fixed: 1108019 Change-Id: I298c12ed56231b27f3ce505911db5e3fe0c2a16e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310535Reviewed-by:Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#790979}
Showing
Please register or sign in to comment