reloading a fullscreen web page launched from homescreen zeros safe-area-inset env()s
Reported by
davidmax...@gmail.com,
Oct 30
|
|||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3590.0 Safari/537.36
Steps to reproduce the problem:
0. use a phone with notches (eg pixel 3) or enable them ('Simulate a display with a cutout' -> 'double display cutout') in the android developer options
1. in chrome on android, open http://safeareatest.davidmaxwaterman.fastmail.co.uk/
2. add the page to homescreen using the browser menu
3. close browser
4. launch from homescreen
- notice app is fullscreen, the top and bottom text are avoiding the notches, the padding values are shown as '30px' on the text in the centre of the screen
5. swipe down to reload the page
What is the expected behavior?
padding-top and bottom remain at 30px
What went wrong?
I guess reloading the page causes the env(safe-area-inset-*) values to be lost.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 72.0.3590.0 Channel: dev
OS Version:
Flash Version:
My real app is a PWA and much more complicated.
,
Oct 31
Thanks for filing the issue! As per comment# 0 steps to reproduce the problem, issue seems to be related to Android device, hence adding appropriate OS label to it. Thanks!
,
Oct 31
I don't have a device with a cutout. Becca, could you triage this?
,
Oct 31
As mentioned, pixel 2 has this in the development options - I think it's part of Android P, so any phone with Android P?
,
Nov 2
Tested the issue on Android and able to reproduce the issue as per steps mentioned in c#0.On reloading the page padding-top and bottom changing to 0px Chrome versions tested: 64.0.3271.0, 70.0.3538.80(Stable), 72.0.3598.0(Canary) OS: Android 9.0 Android Devices: Pixel 2 XL This seems to be a Non-Regression issue as same behavior is seen since M-64 from introduction of add to home screen feature. Leaving the issue as Untriaged for further input's on this issue. Please navigate to below link for log's -- go/chrome-androidlogs/900154 Thanks!
,
Nov 5
,
Nov 20
Actually, I've just experienced another problem with the safe-area-inset values, and it doesn't seem to happen with a phone with *real* notches, but only with the fake ones in the development tools - a colleague has a Pixel 3 with real notches, but I don't (only a Pixel 2). I did try it on a Huawei Mate 20 Pro in a store, and that put me onto the problem. I'm about to log a bug on that, but perhaps it is related to this one. https://bugs.chromium.org/p/chromium/issues/detail?id=907097
,
Nov 20
Issue 907097 has been merged into this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Oct 30