-
Notifications
You must be signed in to change notification settings - Fork 45
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
webbrowser::open
is non-blocking on macOS but blocking on linux
#13
Comments
Note: This only applies when I don't have Firefox already open. If I have a Firefox window open already, then it appears to be non-blocking again... |
Indeed, it seems to be the case. From the looks of it, in Linux, calling But if For the time being, I think I'll keep API compatibility by returning |
@samuela can you confirm this works? |
@amodm Ok, so this kinda works AFAICT. I just upgraded to version 0.5.1. It still works the same way in macOS. It now works on the ubuntu VM (same version and setup as in the first comment). But it still seems to be blocking when SSHing (with X11 forwarding) into the ubuntu box from the macOS machine. Admittedly, I didn't test this case when reporting the issue initially so I'm not sure whether or not this is a regression. |
@amodm Thanks for your great turnaround time btw! |
That's super weird. I just tested on Ubuntu 18.04 (server) and macOS (client, using XQuartz), , and seems to work exactly as it's supposed to locally. Ubuntu to Ubuntu works as well. |
Can you detail out the config you're trying? |
@samuela if you do find time to share the config that can help reproduce the SSH issue, let's track it in a separate issue. |
Documenting here that new consistent behaviour is now enforced. See Consistent Behaviour section for details. Relevant commit: 614cacf |
The title is pretty self-explanatory. I'm on macOS 10.14.2 and Ubuntu 18.10.
This is weird to me because
$BROWSER
is not set andxdg-open
is also non-blocking. I'm not really sure why but in any case it would be nice to have consistent behavior across platforms.The text was updated successfully, but these errors were encountered: