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

Vimium does not work in Strict Site Isolation mode #2911

Closed
wichtounet opened this issue Jan 12, 2018 · 4 comments
Closed

Vimium does not work in Strict Site Isolation mode #2911

wichtounet opened this issue Jan 12, 2018 · 4 comments

Comments

@wichtounet
Copy link

Hi,

I'm not sure this is really a bug, but I've tried to use Strict Site Isolation on Vivaldi (Chromium engine) and it does not work.

For instance, t opens correctly the input search box but I cannot write inside.

I don't know how Strict Site Isolation mode works, so maybe this is completely expected, I just wanted to report it in case you didn't know ;)

Thanks

Baptiste

System

  • Vivaldi | 1.13.1008.40 (Stable channel) (64-bit)
  • Linux
  • Vimium 1.62.4
@wichtounet wichtounet changed the title Vimium in Strict Site Isolation mode Vimium does not work in Strict Site Isolation mode Jan 12, 2018
@smblott-github
Copy link
Collaborator

Cannot reproduce in Chrome. Anybody else?

@wichtounet Are there any error messages in the console?

@wichtounet
Copy link
Author

@smblott-github The Console in the web tools ? Nothing here related to vimium.

@gdh1995
Copy link
Contributor

gdh1995 commented Jan 25, 2018

I've reproduced this on Vivaldi with the flag #enable-site-per-process enabled, and I think it's a bug of Vivaldi and there's few things we can do about it.

In fact, #enable-site-per-process is a highly experimental feature of Chrome (also Chromium-kind browsers) for a long time, and there're some bugs caused by it on old versions of browsers. For example, Chrome whose version <= 48 will break Vimium if only the flag is enabled, because the Window.postMessage API is implemented bugly.

So I suggest that you disable the feature - Chromium browsers are usually safe enough with default settings.

@wichtounet
Copy link
Author

@gdh1995 Thanks for the investigation :)

I've already disabled the feature, I was mostly testing it but I don't really mind not having it.

If it's a problem related to some versions of browsers, it's indeed not your problem 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants