[Multi-display ARC] Send local bounds instead of global bounds
When removing display or adding primary display, Chrome sent bounds based on updated display metrics, while on Wayland side, the display metrics is not updated immediately. So when converting the Chrome coordinates to Wayland coordinates, it converts to wrong position. Instead of sending global bounds, send the local bounds with display id to avoid asychronization issue between Chrome and Wayland on bounds and display metrics. There is remaining issue when ARC window in external and removing the external display. It will be fixed separately. Android side: http://ag/7326868 http://ag/7325387 http://ag/7322138 BUG=b:130897153 TEST=Printed the log to see if correct local bounds sent. Change-Id: Ifdb7644cdfcb1a96ba0ace399b8e0f32eb7a6be0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593923Reviewed-by:Mitsuru Oshima (OOO 8/5,6) <oshima@chromium.org> Auto-Submit: Cici Ruan <cuicuiruan@google.com> Commit-Queue: Cici Ruan <cuicuiruan@google.com> Cr-Commit-Position: refs/heads/master@{#683902}
Showing
Please register or sign in to comment