You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When viewing the camera screen on a Galaxy Tab S2 (1536 x 2048 pixels) in Chrome, portrait view, the camera capture button and submit buttons were obscured. I had to scroll down to view these controls.
To Reproduce
View the camera screen from creating a purchase request. Observe that the camera controls are clipped at the bottom and are only reachable by scrolling.
It's difficult to reproduce this behavior in desktop Chrome, because the cameras installed in laptops use landscape dimensions (which fit just fine in this screen). Running on an emulator or a physical device may be the only way to replicate this clipping.
Expected behavior
Camera controls stay within the viewport without scrolling to find them.
Screenshots
Device (please complete the following information):
Device Model: Galaxy Tab S2
Environment:
Which environment(s) is this bug located in?
Describe the bug
When viewing the camera screen on a Galaxy Tab S2 (1536 x 2048 pixels) in Chrome, portrait view, the camera capture button and submit buttons were obscured. I had to scroll down to view these controls.
To Reproduce
View the camera screen from creating a purchase request. Observe that the camera controls are clipped at the bottom and are only reachable by scrolling.
It's difficult to reproduce this behavior in desktop Chrome, because the cameras installed in laptops use landscape dimensions (which fit just fine in this screen). Running on an emulator or a physical device may be the only way to replicate this clipping.
Expected behavior
Camera controls stay within the viewport without scrolling to find them.
Screenshots
![image](https://user-images.githubusercontent.com/2977329/115163107-17b36400-a05c-11eb-85b9-3a9644f3c090.png)
Device (please complete the following information):
Environment:
Which environment(s) is this bug located in?
CC: @julianrkung
The text was updated successfully, but these errors were encountered: