SUMMARY Chrome and Firefox extension support on Falkon would be great way to extend its the functionality. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Operating System: Kubuntu 18.10 KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 Kernel Version: 4.18.0-15-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION * uBlock Origin instead AdBlock * Currently have the Snap version installed
Forgot to mention I noticed that the Flatpak & Appimage are listed as separate platforms. Snap isn't part of the list.
(In reply to techxgames from comment #0) > SUMMARY > Chrome and Firefox extension support on Falkon would be great way to extend > its functionality. It appears from my research that being able to add Chromium (Chrome) extensions to Falkon depends on QtWebEngine adding this functionality, which it currently does not have. Here is a link to a QtWebEngine request which received this reply dated 19 Mar 2019: "Tentatively considered for Qt 5.14." https://bugreports.qt.io/browse/QTBUG-61676 Hopefully we will get this capability eventually.
Does this involve making a basic layer for building extensions or going as far as adding extension support as outlined by Mozilla?[1] One could just go for the one outlined by the W3C community group[2] [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions [2]: https://browserext.github.io/browserext/
it would be great +1 any news?
*** Bug 428832 has been marked as a duplicate of this bug. ***
Any updates about this?
Updates?
It would be great to have the extensions from Chrome and Firefox work in Falkon - I would speed up the development and adoption of Falkon
Having Chrome and Firefox extensions work in Falkon would help speed up development and adoption of Falkon browser.
*** Bug 491653 has been marked as a duplicate of this bug. ***
I successfully implemented Chome extensions support for Falkon. I am just waiting my KDE Identity to be approved so I can push my git branch to https://invent.kde.org/network/falkon What made the extension support possible was the new class QWebEngineExtensionManager introduced in Qt 6.10 I just created a new tab in Preferences dialog, with a button to add a local extension file, and a button to remove a selected extension. All my modifications have conditional compiling and are only compiled in systems that have Qt 6.10+ The Google Chome Web Store blocks Falkon to download the extensions directly from there, because Falkon TLS fingerprint doesn't match with Google browser family (Chrome, Chromium) even using QtWebEngine which uses Chromium. I post a new comment here when I push it to KDE Invent.
It would be great, if true.
Nice, that sounds cool!
My work is ready to be reviewed at https://invent.kde.org/danielvarella/falkon Remember that this feature only compiles with Qt 6.10+ I need your feedback. Tell me what can be improved. It supports Chrome extensions to be installed only using a local file for now. Installing and updating Chrome-like extensions will only be possible if they are hosted in a website, for example store.falkon.org I volunteer to implement the client-side.
Falkon developers will have the highest chance of seeing your work if you submit it as a merge request. Can you do that? Thanks a lot!
I have some bad news... I implemented everything needed for extensions support, but there is something missing from the Qt side. I filled a bug, but I don't know how long they will take to fix it. More details in https://qt-project.atlassian.net/browse/QTBUG-143169 Should I submit a new merge request when this problem is resolved?
(In reply to danielvarella from comment #11) > I successfully implemented Chome extensions support for Falkon. May I ask if it supports manifest V3 in order to have a full fledged adblocker in Falkon?
(In reply to postix from comment #17) > May I ask if it supports manifest V3 in order to have a full fledged > adblocker in Falkon? Yes. According to QWebEngineExtensionManager, "Only ManifestV3 extensions are supported, other versions won't be loaded nor installed" I'm also eager to see extensions like uBlock Origin, Dark Reader and Video DownloadHelper working in Falkon.
(In reply to danielvarella from comment #16) > I have some bad news... > > I implemented everything needed for extensions support, but there is > something missing from the Qt side. > I filled a bug, but I don't know how long they will take to fix it. > More details in https://qt-project.atlassian.net/browse/QTBUG-143169 > > Should I submit a new merge request when this problem is resolved? I'm quite excited for the implementation for WebExtensions on Falkon. It appears that the above bug has been resolved and QtWebEngine has also added partial support for them. Has there been any further updates or progress?
(In reply to nqbd1vd1x from comment #19) > (In reply to danielvarella from comment #16) > > I have some bad news... > > > > I implemented everything needed for extensions support, but there is > > something missing from the Qt side. > > I filled a bug, but I don't know how long they will take to fix it. > > More details in https://qt-project.atlassian.net/browse/QTBUG-143169 > > > > Should I submit a new merge request when this problem is resolved? > > I'm quite excited for the implementation for WebExtensions on Falkon. It > appears that the above bug has been resolved and QtWebEngine has also added > partial support for them. Has there been any further updates or progress? The Extensions API is incomplete in QtWebEngine, and can't be implemented externally. Qt developers are not very collaborative with me, so I'm waiting them to decide expanding the QtWebEngine to make the extension support usable. I dedicated 40 days of my time in December 2025/January 2026, but now I'm busy with other projects and don't have time to deal with Falkon. All help is welcome.
(In reply to danielvarella from comment #20) > (In reply to nqbd1vd1x from comment #19) > > (In reply to danielvarella from comment #16) > > > I have some bad news... > > > > > > I implemented everything needed for extensions support, but there is > > > something missing from the Qt side. > > > I filled a bug, but I don't know how long they will take to fix it. > > > More details in https://qt-project.atlassian.net/browse/QTBUG-143169 > > > > > > Should I submit a new merge request when this problem is resolved? > > > > I'm quite excited for the implementation for WebExtensions on Falkon. It > > appears that the above bug has been resolved and QtWebEngine has also added > > partial support for them. Has there been any further updates or progress? > > The Extensions API is incomplete in QtWebEngine, and can't be implemented > externally. Qt developers are not very collaborative with me, so I'm waiting > them to decide expanding the QtWebEngine to make the extension support > usable. > I dedicated 40 days of my time in December 2025/January 2026, but now I'm > busy with other projects and don't have time to deal with Falkon. All help > is welcome. I see, thank you for your effort! I suppose we'll wait for progress on the Qt side then.