Open Web Telegram as a PWA, scroll down. Once the address bar disappears, white space appears
There shouldn't be any white space and the PWA content should be displayed normally
There is a huge white space left at the place of bottom address bar
OnePlus 7 Pro, running latest Firefox nightly 200420 06:01 on Android 10
UNITO-UNDERSCORE!20200421-081623!Seems to be some larger issues around when the nav bar is shown in PWA. It really shouldn't even be shown in this case.
Demo of problem behavior:

Here is a demo on latest nightly which I updated today via play store.

@Blaze-Thunder Thanks for posting that! I believe that's a separate issue and I'm working with GV to get it fixed. The PWA one is one I can fix now, though ๐
@Blaze-Thunder In #8768 we will address the website issue. I'm going to use this issue to address the PWA version of the fix.
(heads up for QA, please base it off of the steps in this demo https://github.com/mozilla-mobile/fenix/issues/10071#issuecomment-618066737)
Verified as fixed on the latest Nightly build from 5/7 using OnePlus 5T (Android 9).
I've added Web Telegram as a PWA, scrolled the homescreen, no white space displayed.
In Fenix, however, the white space is still displayed, but as Sawyer mentioned here, it will be fixed in a different issue.
Will the fix be delivered late? Because I just downloaded latest Fenix nightly released on 5/7 and still I see the white space on telegram PWA.
@Blaze-Thunder can you send me the screenshot of your About Fenix page and a demo of this bug still happening? I'd also recommend reinstalling the Telegram PWA.
@sblatz If we install it on homescreen as an app and open, there is no address bar at all.
We have to open web telegram in Fenix browser itself. This issue happens then. Attached screenshot of my build and the bug demo on the latest build.


@Blaze-Thunder As I mentioned, the PWA case is fixed, and the website version is not yet. Please follow #8768 for the web based version of this bug as this is a known issue GeckoView is working on.
Got it! Thanks!
Most helpful comment
@Blaze-Thunder Thanks for posting that! I believe that's a separate issue and I'm working with GV to get it fixed. The PWA one is one I can fix now, though ๐