New issue
Advanced search Search tips

Issue 790857 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

navigator.onLine is incorrectly false

Reported by dylanjha...@gmail.com, Dec 1 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Example URL:

Steps to reproduce the problem:
I am not sure how to reproduce this reliably. These are the steps I took that resulted in the issue.

1. Open Chrome
2. Load any web page
3. Open developer console, check `window.navigator.onLine` see that value is `false`
4. Refresh the page, repeat developer console check, still false
5. Open a new tab, on a new website, same thing
6. Open a new window, on a new website, same thing

What is the expected behavior?
navigator.onLine should be `true` when connected to a network.

What went wrong?
navigator.onLine was `false` when it should be true. When turned off WiFI and reconnected then the issue was no longer happening.

I also confirmed this same issue happening to 5 other people using the same version of Chrome. I am surprised that I was unable to find an existing ticket with some clues as to what might be causing this.

The only similar ticket I found was this one from 2015:

> https://bugs.chromium.org/p/chromium/issues/detail?id=678075

The interesting thing here is that this ticket also mentions firebase, we are using firebase in the web application that first raised this issue.

One key difference from my report vs. 678075 is that 678075 is specific to an extension background page, my case definitely affected every tab and every window in Chrome.

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: stable
OS Version: OS X 10.13.1
Flash Version: 

Unfortunately, I am no longer experiencing this issue, so if no one else can recreate this, and no one has any ideas then this might simply be a dead-end and this can probably be closed but at least if someone else searches they might find this useful and might be able to help come up with reproduction steps.
 
Cc: kebalaji@chromium.org
Labels: Needs-Feedback Needs-Triage-M62
Unable to reproduce the issue on reported version 62.0.3202.94 on Mac 10.13.1 with the stpes mentioned in Comment#0. Attaching screenshot for reference.

@Reporter: Could you please confirm whether the issue still persists or not.

Thanks!
790857.png
221 KB View Download
Thank you for your comment and for trying to reproduce. I am no longer experiencing this issue.
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 4 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kebalaji@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
Components: -Internals>Network
Status: WontFix (was: Unconfirmed)
Closing as WontFix since the issue no longer reproduces.

Sign in to add a comment