Because a video sometimes is better than words…
This tiny video shows the actual state of extension support:
– we can manage chrome extensions (I just copied examples from here): we can recognize unpacked extensions, install, enable/disable. (oops.. uninstall/delete missing. Adding next days..)
– we can interpret (a bit) the version 2 manifest.json inside
– we can manage browse actions
– we can manage page actions
– we can open popups
So, the first easy step is done. Now what to really say we are supporting chrome extensions? Here is my todo list:
– support chrome object and (a subset of) its API (very long task)
– support the callback mechanism (really hard, this is the trick missing to say we’ll reach one day our goal)
– implement a way to retrieve extensions (support chrome extensions site? seems problematic. Add a ghns layer? Should do the trick. Probably…)
– ehm… port/implement extensions 😉
Stay tuned.
adjam.weblog() 
Keep up the good work! I would love to see chromek extensions available for rekonq!
very good news !
Any progress with this great feature?
If this is implemented, then Firefox and Chromium goes to the trash.
Apopas,
cause of the big changes in qtwebkit , blink and so on we had to postpone this work after the qt5/webengine port, sorry.
It is an hard interim period for rekonq and qtwebkit browsers 😉
Pingback: Rekonq: in arrivo il supporto per le estensioni di Google Chrome – Gda Tech
Pingback: Rekonq tendrá soporte para las extensiones de Google Chrome