-
Notifications
You must be signed in to change notification settings - Fork 301
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
List Browser Support #401
Comments
Probably after the discussion here: https://greasyfork.org/forum/discussion/1933/potential-new-feature-script-compatibility |
We'll have to wait and see what the other user.js engine maintainers support in greasyfork-org/greasyfork#30... if rejected OUJS could always "prefix" although that could change to the mentioned separate metadata block from our #285. I'll be tackling the pegjs package soon and retrying to figure out how we are going to read that into our "serialized" object that we actually use... but I need feedback there first since that is a dependency. I think it is also preferred that @arantius / @johan creates a dummy Sample dummy {
"name": "Greasemonkey",
"version": "2.3.0"
} |
The key value pairs that are currently used over there are: // @compatible firefox
// @compatible chrome
// @compatible opera
// @compatible safari This is doable however not anywhere near as comprehensive as my GPL compatibility matrix which is deposited in the script content area (and the text version of it in the About docs). A lot of authors don't even specify this over the last few years e.g. it's not a widely used feature even over there. If they do it's usually in the script content area. Most of the browsers are Gecko, Goanna, whatever Edge is up to, Trident, and Blink (V8) back-end engines regardless of their brandings which come and go (Think Operas switch to Blink). So I'm still on the fence. I do like the simplicity but it's also quite "favorable" to only four actual browsers. We have the asset resources to do this already with the UA. I've added a "needs vote" label to this... please vote on the issue summary above #401 (comment) and will look back into this periodically. |
Been watching this forever and there's absolutely no consistency in its usage... additional browsers have shown up, strange modifications, etc. |
Support an extra meta-data "Browsers" or maybe just a way in the OUJS site to select and show the browsers the script officially supports. Maybe the list of supported browsers should also appear in script listings.
The text was updated successfully, but these errors were encountered: