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.

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

Improved Greasemonkey compatibility #1091

Open
Emdek opened this Issue Mar 28, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@Emdek
Copy link
Member

Emdek commented Mar 28, 2016

Currently we have basic support for user scripts, but to support more of existing scripts we have to support some extra features.

The most important stuff:

  • respecting @exclude, @include and @match keywords;
  • support for extra JavaScript APIs exposed by GM, plus support for @grant keyword;
  • support for @resource and @requires keywords.

Other tasks:

  • support for @icon keyword;
  • UI to manage scripts;
  • support for updating scripts.
@Frenzie

This comment has been minimized.

Copy link
Member

Frenzie commented Mar 28, 2016

Note that for the moment, users can look at e.g. http://userscripts-mirror.org/scripts/show/105153 for the GM API.

@Emdek

This comment has been minimized.

Copy link
Member Author

Emdek commented Mar 28, 2016

@Frenzie, good catch.
I guess that this one could be a good reference implementation to test our implementation.

@uahim

This comment has been minimized.

Copy link

uahim commented Mar 29, 2016

@Emdek @Frenzie thanks

where am I to put the directory, I did check settings, about:config and also the Otter settings directory for a subdirectory, all with no luck. unless this is coming in 118?

@Emdek

This comment has been minimized.

Copy link
Member Author

Emdek commented Mar 29, 2016

@uahim, right now it is a bit complex task...
I'll try to land some basic Addons Manager before beta.

@uahim

This comment has been minimized.

Copy link

uahim commented Mar 29, 2016

ah sorry didn't see the "in progress" label; figured it was already usable

Emdek added a commit that referenced this issue Mar 29, 2016

@vbr vbr referenced this issue Apr 9, 2016

Closed

scripting #1116

@OVNI-modding

This comment has been minimized.

Copy link

OVNI-modding commented Mar 27, 2018

@run-at should also be supported.

Especially '@run-at document-start' since it's pretty much mandatory for complete restyling scripts.
For example I use it in other browsers for a "dynamic contrast" script that makes every background colors a bit darker, and text brighter.
(For now I use a user-css in Otter, but it can only set absolute color)

@Emdek

This comment has been minimized.

Copy link
Member Author

Emdek commented Apr 26, 2018

@OVNI-modding, currently run-at is only fully supported with QtWebEngine backend.
In theory we could already improve it on QtWebKit side but it's harder to properly map injection time without dedicated API for running user scripts...

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