Please find logs and Video @ http://go/chrome-androidlogs1/6/651410

fgorski@, Can you please take a look at this bug, Thanks!

Moving to M55.
I'll look into it.

Does not reproduce on 55.0.2874.0 ...
I am building ToT to see if the problem appears there.

@fgorski From the above mentioned steps, i was able to reproduce this on 55.0.2874.0 as well

Can u upload a quick screen rec for the same (if possible) with build 55.0.2874.0? Thanks! :)

For recording, please email me instructions on how to do that.

I just tested ToT on Nexus 7 (55.0.2876.0) and snackbar appears as well there. (Prior test was on N5X)

Perhaps I am doing something wrong. What do you mean by "Chrome is kept in background"?

Also I noticed that the snackbar may take longer (getting on wifi may not be immediate).

What i mean by "Keep Chrome in background" is that minimize chrome so that it remains in the device's Recent apps list. Disconnect your WiFi > open the web app > Reconnect to your WiFi. After these, you will see that the snackbar never appears. 

I waited for a good 5 minutes of duration just to check if snackbar appears or not and, it doesn't.

For expected behavior, make sure you do not have Chrome under device's Recent apps list. Disconnect your WiFi > open the web app > Reconnect to your WiFi. After this, you will see that the snackbar does appears that too within a second.

I hope this helps you with reproducing the bug. Thanks!

I have also mailed you the instruction to get a record of your device's screen

OK. It seems that this page is opening from the homescreen link with no Chrome UI (omnibox missing and no snackbar). User has no way of knowing whether they are looking at an offline page or live page.

The only way to move from there is to pull down to refresh once online.

This behavior does not happen on a lot of other pages, like wikipedia.

This page does not seem to have a service worker or a manifest, yet when added to home screen it is treated as a standalone page, with no UI.

Tal, Rachel, as you are already thinking of dealing with UI that does not give enough clues about being offline, can you advice with this one?

And properly assigning to Tal. See #9 for my comments and a question.

You can also reproduce this issue with another web page m.timesofindia.com

Ah, got it. Interesting – I hadn't thought of the use case of opening in full screen. Other than a link from a home screen icon, are there other ways people go into full screen?

This is not about going full screen as much as opening a web app, where the omnibox and snackbar are not present.

I don't know about other ways of opening the web apps. Do you know who owns that area?

Need UI

Fixit update:
(Tal): Given that the snackbar is in the content area, do we not show that if the user re-connects?

I think my current preference here would be not to do anything. Full screen mode is intentionally for not showing Chrome UI and presumably if a developer wanted a more robust experience, they could support offline in their application with SW.

(dewittj):  This might not work as well as you'd hope since (I think) we intervene with offline pages before the service worker has a chance to run.

(tal): So that means that if the user has an offline version of a page that has a SW enabled, they can never get to the SW version? (ie. refreshing results in showing the same offline snapshot assuming the user is still offline?). Do we have a sense of what the latency costs would be with seeing if there's a SW before loading the offline page?

SW does not seem to be the problem here, it takes precedence over showing of the offline copy.

To my knowledge showing any UI is not available right now as Omnibox is not present and snackbars are not available.

This would require framework level work.

Got it. I think this can be a lower priority. In general, my preference would be to be able to show the "you're viewing an offline page snackbar" when in full screen mode, but I don't think this needs to be in the fixit.

+ted for general thoughts on what it would take to support showing a snackbar in full screen.

Snackbars should be supported in all web page viewing activities already.  No additional eng work "should" be required.

Thanks, Ted, for some reason I missed that earlier.
Snackbars are supported and the one that we show when device is reconnected: "Viewing on offline copy of this page [RELOAD]" appears properly.
(Verified on Stable M57).

SW works properly per #17.

Tal, do you want to do anything extra for this case? Like showing the snackbar, when offline page gets loaded in full screen, to compensate for lack of Omnibox and OIB?

We are comfortable with the current behavior. No changes are necessary.