Fixed
Status Update
Comments
tr...@google.com <tr...@google.com> #2
Actually, a multiplier of 8.67 gets me back to the approximate position it should be.
er...@google.com <er...@google.com> #3
This bug was fixed in 2.1.1. Thanks for the report!
bu...@google.com <bu...@google.com> #4
While the behavior has changed, it is still incorrect, IIUC. Now the view is shifted up too much for the values entered. For instance, when I enter a bottom inset of 200, which is less than half of the total height (509) of the map, and so should have no effect on the default centering behavior, the marker is actually centered at 354.5 points from the bottom, which is the center of the map plus half of the bottom inset. This seems incorrect per my understanding of that API.
er...@google.com <er...@google.com> #5
354.5 sounds exactly right to me.
bu...@google.com <bu...@google.com>
er...@google.com <er...@google.com> #7
Bugjuggler:
bu...@google.com <bu...@google.com> #8
Hi. I've received your bug and will wait for b/146048690 to be fixed and then assign the bug to ericng@google.com.
bu...@google.com <bu...@google.com>
er...@google.com <er...@google.com> #9
Bugjuggler: wait until next month
bu...@google.com <bu...@google.com> #10
Hi. I've received your bug and will wait until 2020-02-01 00:00 -0800 PST and then assign the bug to ericng@google.com.
bu...@google.com <bu...@google.com>
er...@google.com <er...@google.com> #11
er...@google.com <er...@google.com> #12
This will be included in the Alpha10 release. Marking as fixed. Thanks!
Description
This is a Known Issue.
Currently some apps using PreviewView may have a stretched/incorrect aspect ratio preview after pause / resume on some FULL devices like pixel2.
ETA will be posted once we root cause and schedule a fix.