-
-
Notifications
You must be signed in to change notification settings - Fork 235
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
[Feature Request] Chrome extensions support #824
Comments
would probably maybe hopefully enable passkey login with a password manager extension like bitwarden as well |
it doesnt support most of the extension api which makes a lot of extensions not functional this is technically already implemented in vencord (used for react devtools) but has no ui |
By vencord do you mean the version that patches the discord desktop client? |
Other wise patch discord them install vencord is the best option :/ |
i tried googling things like 'chrome extension in electron app' and am seeing some conflicting info about what's actually possible, but it would be sweet to be able to install uBlock Origin in Vesktop. CSS can only take you so far. in particular, CSS can't do selectors like |
you can't. anyway i'll be closing this since there is not any real use case that can't be solved with a plugin. like i said above, most extensions straight up won't work so it's pointless |
Discord Account
No response
Motivation
Since discord is based on chromium, it would be very cool if we are able to include chromium extensions when building. This can make the Experience better.
For example, a better spellcheck like LanguageTool or Grammarly can make correcting spelling easier and suggest better way to structure sentence in discord.
Currently, running discord in a browser is the only way to have these feature with discord at the same time.
Solution
Allow the users to add chromium extensions when building Vesktop
Alternatives
Ctrl+Shift+i
try to navigate to Chrome web store by editing the HTML of the page and adding a link
unable to add an extension :(
Additional context
No response
Request Agreement
The text was updated successfully, but these errors were encountered: