[Question] Any plan (possibility) to support general Chrome extensions? about chromext HOT 19 CLOSED

Ik, i was just suggesting ideas to be beneficial for the dev to look into

from chromext.

Oh, then it's best just to wait for Chromium to add support
Thanks for the explanation

from chromext.

No, you misunderstood. WebExtension is the standard notion for what you call browser extensions.

from chromext.

Kiwi Browser has support for extension also i think it's source code can be found in GitHub

from chromext.

Kiwi Browser has support for extension also i think it's source code can be found in GitHub

Yeah but they do not support injecting patches into for example official Google Chrome. Imagine dreams come true so that we can in official Google Chrome or Microsoft Edge gets full chrome extensions support. Not Kiwi Browser, not custom browsers with built-in support - just direct native support inside official browsers using LSPosed/LSPatch/Xposed Framework 🥰

That would be very nice and cool - especially because no one did that and probably no one will ever did that so why some dev cannot be the first who will do it?

from chromext.

Ik, i was just suggesting ideas to be beneficial for the dev to look into

Oh.. you think that the dev can look into Kiwi Browser source code to find out how chromium-based code can have chrome extensions support? That's actually a good idea but I don't think they will agree for allowing their code to be reused for that.

I've just got response by Kiwi Browser owner that said that this support will not happen as the Xposed/LSPosed module. Maybe they just don't want that so maybe dev will be forced to look at other ways to gain valid permission to do this work without getting problems with the owner of the code itself if the dev agree for adding this support.

[Update]: The owner changed his mind but he will not build this thing never-ever but he will allow to any dev who wants to try, they can use the part of his code for that thing to try to implement 🥰❤️✨ - Thanks to the owner for getting an important permission

No one tried that before and maybe no one will ever try it - because they will all find a way to skip coding and say, we have Kiwi Browser instead.

Even if this edit can change the world of modding the official browser itself and add an revolution in chrome extensions for mobile devices using official Chromium browsers like Google Chrome itself.

from chromext.

Thanks for your passionate question.
I once wished so as well. Here are some related questions I have investigated before, which might be helpful for you to understand the situation.

Q: Why extensions are not supported in mobile browsers?
A: Chromium project explicitly disabled it. The related code of extensions is avaiable in the Chroimum project, but is excluded from the build processs of Android Chrome. Somehow, Kiwi adds it back to the build process.

Q: Can we learn from Kiwi and add the extension code back to the build process using Xposed framwork?
A: Barely possible. Xposed framework can hook Java codes, but barely C/C++ codes. And it requires some works on the C/C++ codes to add the extension code back to the build process.

Q: What about rewriting a new implementation of Chrome extensions?
A: Currently, it is difficult. One need to re-implement the whole set of Browser extension APIs.

Q: What is the specific difficulty compared to re-implementing the UserScripts APIs?
A: Running scripts in background. ChromeXt is quite strong with the help of DevTools, but still couldn't handle this problem. Extensions exist mainly for the reason of background scripts.

It is more likely that the Chromium project would change their minds to support extensions for mobile browsers before I could finish the re-implementation.
However, if I have ideas for running scripts in backgroud, the remained stuff won't be difficult anymore.

from chromext.

@JingMatrix Can you support this app : https://play.google.com/store/apps/details?id=org.triple.banana

from chromext.

@JingMatrix Can you support this app : https://play.google.com/store/apps/details?id=org.triple.banana

Please open a new issue.

from chromext.

Mhmm quite interesting, so we can't Patch google chrome either to implement the extension API? Because lspatch also rely on Xposed framework
But what about Revanced they don't rely on Xposed framework is it difficult to do the same like Revanced?

from chromext.

In the setting of current issue, there is no difference between Revanced and Xposed framework. Simply because reverse engineering C/C++ is much harder than reverse engineering Java.

from chromext.

Oh, then it's best just to wait for Chromium to add support
Thanks for the explanation

Chromium or better said, Google itself who created Google Chrome and also open source chromium official browsers will never supports mobile devices about extension support so we need to find a way that if Xposed Framework is not enough powerful, maybe Revanced method of patching can help or anything similar to that.

I'm open for every suggestions about getting something I can use to inject/patch easly any chromium based browsers to get chrome extensions support (web store, installing extensions...) - even if that requires some other method of patching it instead Xposed Framework (module method).

Everything is welcome except suggestions about just using unofficial-supported-browsers or like "build your own/write from scratch/develop the patches by yourself" stuff...

But everything else is welcome 🥰

from chromext.

Thanks for your passionate question.
I once wished so as well. Here are some related questions I have investigated before, which might be helpful for you to understand the situation.

Q: Why extensions are not supported in mobile browsers?
A: Chromium project explicitly disabled it. The related code of extensions is avaiable in the Chroimum project, but is excluded from the build processs of Android Chrome. Somehow, Kiwi adds it back to the build process.

Q: Can we learn from Kiwi and add the extension code back to the build process using Xposed framwork?
A: Barely possible. Xposed framework can hook Java codes, but barely C/C++ codes. And it requires some works on the C/C++ codes to add the extension code back to the build process.

Q: What about rewriting a new implementation of Chrome extensions?
A: Currently, it is difficult. One need to re-implement the whole set of Browser extension APIs.

Q: What is the specific difficulty compared to re-implementing the UserScripts APIs?
A: Running scripts in background. ChromeXt is quite strong with the help of DevTools, but still couldn't handle this problem. Extensions exist mainly for the reason of background scripts.

It is more likely that the Chromium project would change their minds to support extensions for mobile browsers before I could finish the re-implementation.
However, if I have ideas for running scripts in backgroud, the remained stuff won't be difficult anymore.

Nice - I'm ready to wait as long as it requires for the module/tool for patching the official browsers because I currently believe after many many years, Google just don't want and not just Google, the whole Chromium don't want Chrome extensions to be able to mobile devices so I believe that they will never add it. Especially because of Adblockers and many other extensions that exist on desktop devices can be found on Android/iOS devices as an alternative app or something.

So there is many reasons why they will probably never add an official support but with your work of implementation (patching methods like mentioned above or something similar to that), this could be changed unofficially to official without forcing them to support mobile devices like desktop devices.

Even Firefox stopped native support of extensions that was used for desktop and make something similar to be only for mobile devices because of safety and etc... and that also says that they literally all working on limiting somehow mobile devices from desktop features. But the most reasons are security and safety for their customers/users.

So only unofficial projects can give to us an official support on mobile devices we all want and deserve ❤️🥰🫂

Happy work our dear dev! And good luck with the revolution of chrome extensions support ✨

from chromext.

I did a quick digging o found this
https://github.com/wchen342/chromium-android-extension
Are they useable? They're for Chromium i don't know if it's reliable for google chrome

from chromext.

Thanks for your searches. Basically, you can imagine the Kiwi project as an updating version of what you found.
The project adds extension codes back to the build process of Android Chrome.

from chromext.

Oh, ok thanks for checking

from chromext.

Now I get an idea of supporting background scripts.
In the future, ChromeXt will allow users to install WebExtentions.

Be patient, the plan is to re-implement the whole set of WebExtentions APIs.
You can keep track of development plans to see how much is / will be done of supporting WebExtentions.

I close this issue since the answer is clearly given.

from chromext.

Now I get an idea of supporting background scripts.
In the future, ChromeXt will allow users to install WebExtentions.

Be patient, the plan is to re-implement the whole set of WebExtentions APIs.
You can keep track of development plans to see how much is / will be done of supporting WebExtentions.

I close this issue since the answer is clearly given.

wait... WebExtensions Cross-Platform Extensions will be only supported? There's no way to implement the whole support of Chrome Extensions API and support into the module? This also means no chrome web store nor Edge Web Store... sorry if I misunderstood this.

from chromext.

No, you misunderstood. WebExtension is the standard notion for what you call browser extensions.

Oh so... you mean that Chrome API and Chrome Extension will be supported (and that includes Chrome Web Store) 🥰 - Wow! Internet just make me to misunderstood due to reading about thing called WebExtension by mozilla.org but those docs requires modifications by dev to port extension to WebExtension to work but it's good to know that in this case, that is not the same 🫂 - Thank you dev so much for the future of Chrome Extensions on official chromium browsers 🥰🫂

from chromext.