-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Use real extensions #266
Comments
Kind of, but it's a bit tricky. Hero runs in incognito mode, which makes activating extensions a pain. You can turn off incognito mode, but that restricts each chrome instance to a single Hero session, or you can automate turning on the extension in incognito mode by navigating to the extension pages as the beginning of every Hero session. You'll need to use a plugin (https://ulixee.org/docs/hero/plugins/core-plugins) to add the chrome launch args to activate the extension. You might also need to remove '--disable-extensions' and a few other conflicting ones from the launchArgs.
|
Thank you! I think this does not work
There is no error whatsoever, I can check also in |
Sorry, I used bad args for that example. API signature is should be |
Thank you, it works to load the extension, now an issue is that I can't seem to browse programmatically on chrome://extensions It instantly crash: If typing manually in the address bar, it does access chrome://extensions without issue (it opens a new chrome window without incognito) I have tried as well to await 10 seconds and go directly to |
Is there any other errors in the logs that say why chrome crashed (or hero crashed)? |
That's right after |
If you turn on DEBUG=ulx* on the command line, you should get more verbose logging (this is on core side). I don't see any clues in this snippet. |
|
I've also tried to create another tab first then browse with that tab, automated fake click too... all of them crash the instance right away, except when it's done manually, then it works. |
Hi, I would like to add uBlock origin, is there a way?
The text was updated successfully, but these errors were encountered: