Installed PWAs get crippled to save bandwidth |
|||||||||||
Issue descriptionDevice name: Google Pixel From "Settings > About Chrome" Application version: 60.0.3112.116 Operating system: 8.0.0 URLs (if applicable): facebook.com Steps to reproduce: (1) log in on facebook.com (2) install facebook on your homescreen ("Add to Homescreen") (3) I'm not sure what step three is, maybe "be on a crappy 2g network"? Expected result: facebook pwa loads Actual result: facebook looks crippled and I get a small infobar at the buttom that tells me that bandwidth was saved and gives me to option to show the original Also note that it doesn't give me a way to learn more about this feature, nor a way to disable it globally.
,
Sep 5 2017
shouldn't data saver not affect https sites?
,
Sep 5 2017
This might be the client-side Lo-Fi experiment, but it's not possible to tell from the bug description. It would help if you could explain what you mean by "crippled" or at least provide a screenshot. This isn't a very useful bug report otherwise.
,
Sep 5 2017
i'll add a screenshot next time it triggers. It looked like stylesheets were only partially loaded.
,
Sep 5 2017
,
Sep 6 2017
Assigning to bengr@. The behavior you described would be surprising to me, but Ben would know best (a) what we should expect and (b) possibly what combination of flags we can use to reproduce.
,
Sep 14 2017
A screenshot would be helpful. We have only two 'previews' optimizations that operate on HTTPS pages. The first shows the offline version of a page if one is available. It could be that the offline snapshot is bad. The second is client-side Lo-Fi, which replaces images with grey rectangles with an icon in the center.
,
Nov 3 2017
jochen: Could you send a screenshot?
,
Dec 19 2017
Even without a screenshot, I take your point that we should look specifically at the interaction between PWAs and Data Saver optimizations. Reassigning to ryansturm@ to investigate.
,
Dec 19 2017
,
Feb 7 2018
,
Feb 7 2018
,
Feb 28 2018
I looked at M64 with LoFi and DataSaver enabled with slow network and do see image placeholders when I launch the browser from a Facebook home screen icon. And I do see the "Saved data. Show original" info bar at the bottom. It looks like WAI as far as I can tell. Attaching screenshot for the LoFi treatment and for the result of then choosing "Show original" Does this look like the same experience as originally asked about?
,
Feb 28 2018
That seems off still. PWAs are when you click "Add To Home Screen", and they very much seem like a native app instead of the Chrome app in a few ways (they don't have omnibox or ... menu). IMO, we should prevent previews on PWAs, custom tabs, web view, etc. Everything outside of Chrome app should not see Previews.
,
Feb 28 2018
Yeah, I did "Add to Home Screen" but I seem to have more of a shortcut than PWA.
,
Mar 1 2018
PWAs actually don't always need to look different from chrome, as they can set different displays in their manifest: https://developer.mozilla.org/en-US/docs/Web/Manifest#display I believe everything except "browser" should stop showing previews.
,
Mar 1 2018
This demo can install a fullscreen PWA, and provides links to standalone and minimal-ui demos. https://piotrswigon.github.io/pwa-demo/fullscreen/
,
Mar 27 2018
,
Jun 22 2018
,
Jul 23
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by morlovich@chromium.org
, Sep 5 2017Status: Untriaged (was: Unconfirmed)