Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support for cross-browser web extensions #244

Open
7 of 22 tasks
kalikiana opened this issue Jan 29, 2019 · 5 comments
Open
7 of 22 tasks

Support for cross-browser web extensions #244

kalikiana opened this issue Jan 29, 2019 · 5 comments
Assignees
@kalikiana
Labels
enhancement New feature or request
Milestone
There's always ne...

Comments

@kalikiana
Copy link
Member

kalikiana commented Jan 29, 2019 •
edited
Loading

Aside from its own native extension (plugin) interface Midori should support web extensions. The use cases are:

  • Use existing extensions for other browsers
  • Facilitate feature development based on web technologies
  • Share extensions between platforms (Android, GTK+)

Issues or merge requests should be linked next to the items, which should be checked as they're implemented.

See ANDROID-10 for the Android epic

For reference:
@kalikiana kalikiana added this to the Robolicious milestone Jan 29, 2019
@kalikiana kalikiana self-assigned this Jan 29, 2019
@kalikiana kalikiana added the enhancement New feature or request label Jan 29, 2019
@kalikiana kalikiana mentioned this issue Feb 6, 2019
Open
kalikiana added a commit to kalikiana/core that referenced this issue Feb 6, 2019
@kalikiana
Initial support for cross-browser Web Extension API
47b4e68 
* Json-GLib is a introduced as a new dependency to read manifest.json
* The README contains a new section to summarize the Web Extension API
* Web extension support is implemented as a Peas plugin
* Web extensions can be built-in, system-wide or user-installed
* The Javascript interface is added to the core GLib.Resource
* Midori.Tab shares a WebKit.UserContentManager per WebKit.WebContext

Fixes: midori-browser#244
kalikiana added a commit to kalikiana/core that referenced this issue Feb 7, 2019
@kalikiana
Initial support for cross-browser Web Extension API
e45253b 
* Json-GLib is a introduced as a new dependency to read manifest.json
* The README contains a new section to summarize the Web Extension API
* Web extension support is implemented as a Peas plugin
* Web extensions can be built-in, system-wide or user-installed
* The Javascript interface is added to the core GLib.Resource
* Midori.Tab shares a WebKit.UserContentManager per WebKit.WebContext

Fixes: midori-browser#244
kalikiana added a commit to kalikiana/core that referenced this issue Feb 7, 2019
@kalikiana
Initial support for cross-browser Web Extension API
70d0ebb 
* Json-GLib is a introduced as a new dependency to read manifest.json
* The README contains a new section to summarize the Web Extension API
* Web extension support is implemented as a Peas plugin
* Web extensions can be built-in, system-wide or user-installed
* The Javascript interface is added to the core GLib.Resource
* Midori.Tab shares a WebKit.UserContentManager per WebKit.WebContext

Fixes: midori-browser#244
kalikiana added a commit to kalikiana/core that referenced this issue Feb 7, 2019
@kalikiana
Initial support for cross-browser Web Extension API
e84c5cf 
* Json-GLib is a introduced as a new dependency to read manifest.json
* The README contains a new section to summarize the Web Extension API
* Web extension support is implemented as a Peas plugin
* Web extensions can be built-in, system-wide or user-installed
* The Javascript interface is added to the core GLib.Resource
* Midori.Tab shares a WebKit.UserContentManager per WebKit.WebContext

Fixes: midori-browser#244
@kalikiana kalikiana mentioned this issue Feb 7, 2019
Merged
kalikiana added a commit to kalikiana/core that referenced this issue Feb 7, 2019
@kalikiana
Initial support for cross-browser Web Extension API
7ba37d3 
* Json-GLib is a introduced as a new dependency to read manifest.json
* The README contains a new section to summarize the Web Extension API
* Web extension support is implemented as a Peas plugin
* Web extensions can be built-in, system-wide or user-installed
* The Javascript interface is added to the core GLib.Resource
* Midori.Tab shares a WebKit.UserContentManager per WebKit.WebContext

Fixes: midori-browser#244
@kalikiana
Copy link
Member Author

With initial (built-in) extension having landed, we can look into more specific aspects and interfaces to support as well as UX tasks as outlined in the proposal.

@kalikiana kalikiana reopened this Feb 8, 2019
@kalikiana kalikiana mentioned this issue Sep 14, 2019
Open
3 tasks
@zonia3000
Copy link

Hi, sorry for the stupid question... I'm developing a simple cross-browser extension, in which folder should I put it for trying it on Midori? I installed Midori on Ubuntu using snap.

@kalikiana
Copy link
Member Author

Hi, sorry for the stupid question... I'm developing a simple cross-browser extension, in which folder should I put it for trying it on Midori? I installed Midori on Ubuntu using snap.

It should go in ~/.local/share/midori/extensions/, in the case of the snap you'll want to prefix it with the snap home i.e. ~/snap/midori/current/ so it would become ~/snap/midori/current/.local/share/midori/extensions/.

@RJVB
Copy link

RJVB commented Jun 9, 2020

What else do you need to do to get an extension (say in a .xpi container) to load, or else to get some diagnostic output explaining why it isn't being loaded?

@alex-eri
Copy link

alex-eri commented Apr 2, 2021

Using v9.0-7-gd8546ca from snap and dont see content_scripts loaded in inspector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kalikiana kalikiana

Labels
enhancement New feature or request
Projects
None yet
Milestone
There's always next time
Development

No branches or pull requests
4 participants
@alex-eri @kalikiana @RJVB @zonia3000