Replies: 3 comments 6 replies
-
Not for the regular releases. Also I know that my own extension implementation isn't documented at all, this is because it is very limited for now and needs major rewrite to be functional enough. There's a lot of the work to be done, as I want to make extensions a secure way of injecting the code – so the users may know what extensions want to do and what type of the access it needs. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, these are broken as well. That is because Electron supports itself loading the unpacked extensions, where I coded that it should open the packed ones. So yea, that's actually the reason why it fails... |
Beta Was this translation helpful? Give feedback.
-
A few important changes were announced in commit 9ed84b7 – there's now an actual way to load at least some of Chrome/Chromium extensions in WebCord. The implementation is not finished yet, through – there's no GUI implemented to both load unpacked and |
Beta Was this translation helpful? Give feedback.
-
Never mind, I just read that it doesn't allow for code injection yet. So I guess we'll just write a small Chrome Extension.
Edit: Do Chrome Extensions need special permissions for WebCord or fulfill certain criteria? I just hacked a small extension together which works fine on Chrome, but when I load it with WebCord nothing happens..
Beta Was this translation helpful? Give feedback.
All reactions