chrome on android too eager to declare localhost pages offline
Reported by
pdk...@gmail.com,
Nov 20 2017
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.137 Safari/537.36 Steps to reproduce the problem: (Ignore the version reported in the header.) Chrome: 63.0.3239.57 Android: M 1. In your desktop Chrome, go to chrome://inspect and enable port forwarding. 2. Run a web server on the port. 3. Disable Wi-Fi on your Android device. 4. Connect the device through USB, so it's listed in chrome://inspect. That's the set-up, now the problem. (All steps onward in mobile Chrome.) 5. Load the page, perhaps at localhost:8080. 6. Move away from the page and Chrome, such as by opening a different app. 7. Return to the page, and refresh it. What is the expected behavior? The page loads as normal. What went wrong? The page is refreshed but not reloaded. It is instead reported as Offline. It is now impossible to reload the page, unless it is opened in a new tab. Did this work before? N/A Chrome version: 57.0.2987.137 Channel: stable OS Version: Ubuntu 14.04 Flash Version:
,
Nov 21 2017
,
Nov 22 2017
@pdknsk -- Thank You for the report. Could you please provide us a screen cast for better understanding of the issue which would help to triage the issue further. Thanks in Advance.
,
Nov 23 2017
I really can't.
,
Nov 23 2017
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 24 2017
Could some one from Dev Tools please look into the issue and provide an update. Thanks in Advance.
,
Nov 27 2017
> 6. Move away from the page and Chrome, such as by opening a different app. It is likely that chrome is being kicked out of memory and newly connected one does not pick the tethering setting. Do you keep your chrome://inspect page open? If not, we are unlikely to restore these settings. If you keep it alive, that's a bug on our side
,
Nov 28 2017
Yes, the page stays open.
,
Dec 1 2017
Adding appropriate component and tagging with a milestone.
,
Dec 11 2017
I've also noticed this in console, which is probably related. > Slow network is detected. Fallback font will be used while loading: http://localhost:8080/fonts/s400R.ttf
,
Dec 11 2017
From the Offline Pages perspective: This works as intended currently, but I agree we could rethink behavior of offline pages on the localhost. We'll definitely not touch it for M64, but I am sending this to out PM. Longer explanation: Because the network connection is not present (or is detected to be very slow), the tab is falling back to a cached offline copy, which is only available for the tab that saved it. That explain why the behavior affects the old tab, but not the newly open one (the cached copy is not available there). Adding Amanda to CC to take a highlight the issue for her, once she is back from travels.
,
Oct 12
,
Dec 14
Reassign per comment #11 above
,
Dec 14
Jian, could you take a look? |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by krajshree@chromium.org
, Nov 21 2017