Clarify emulator computation and don't rely on emulator state for it
This splits apart the computation of each emulated field and makes more clear the intended outcome for desktop vs mobile cases. We remove the applied_widget_rect_ state, which can be computed from other inputs, and the scale_ state which is already stored in the emulation_params_. When the scale is not used, it used to store it as 0 and multiply the context menu coordinates by 0. Now we store a 1 when the scale is not used. R=avi@chromium.org TBR=caseq Bug: 1006052 Change-Id: I9c9aabca73d7d73f946e5889444004e00e181bec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834080 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#702235}
Showing
Please register or sign in to comment