Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround/fix for Chromium issue #41007340 #2791

Closed
3 tasks
AgentSmith0 opened this issue Apr 7, 2024 · 3 comments
Closed
3 tasks

Workaround/fix for Chromium issue #41007340 #2791

AgentSmith0 opened this issue Apr 7, 2024 · 3 comments
Labels
bug need info Need feedback to proceed Stale

Comments

@AgentSmith0
Copy link

OS/Platform

Arch Linux

Installed

https://ungoogled-software.github.io/ungoogled-chromium-binaries/

Version

123.0.6312.105

Have you tested that this is not an upstream issue or an issue with your configuration?

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

navigator.onLine returns true when VMware network adapters exist

How to Reproduce?

  1. Launch some VM software (e.g. Oracle VM, waydroid, anbox, etc.)
  2. Read navigator.onLine in console
  3. See navigator.onLine gives false positives

Actual behaviour

navigator.onLine returns false positives

Expected behaviour

navigator.onLine returns the correct online status of the system, even when VM software is running.

Since there is no work going on in the Chromium repository to fix this issue (https://issues.chromium.org/issues/41007340), is it possible to implement some workaround or fix inside ungoogled-chromium?

Relevant log output

No response

Additional context

Chromium issue: https://issues.chromium.org/issues/41007340

@AgentSmith0 AgentSmith0 added the bug label Apr 7, 2024
@PF4Public
Copy link
Contributor

I doubt we could and should fix this particular issue if Chromium developers are not very eager in fixing it.

I'll leave it open for some time just to gather more opinions.

@PF4Public PF4Public added the need info Need feedback to proceed label Apr 8, 2024
Copy link

github-actions bot commented May 9, 2024

This issue has been automatically marked as stale as there has been no recent activity in response to our request for more information. Please respond so that we can proceed with this issue.

@github-actions github-actions bot added the Stale label May 9, 2024
Copy link

This issue has been automatically closed as sufficient information hasn't been provided on the issue for further actions to be taken. Feel free to add more information.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug need info Need feedback to proceed Stale
Projects
None yet
Development

No branches or pull requests

2 participants