OpenUserJS / OpenUserJS.org

The home of FOSS user scripts.
https://openuserjs.org/
GNU General Public License v3.0
857 stars 303 forks source link

List Browser Support #401

Open TimidScript opened 10 years ago

TimidScript commented 10 years ago

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.

jerone commented 10 years ago

Probably after the discussion here: https://greasyfork.org/forum/discussion/1933/potential-new-feature-script-compatibility

Martii commented 10 years ago

We'll have to wait and see what the other user.js engine maintainers support in JasonBarnabe/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 package.json so with npm we can retrieve @Ventero 's isolated https://github.com/greasemonkey/greasemonkey/blob/38084649e10aa3c2d70355baf54ea68fb008d872/peg.txt with a git url e.g.

Sample dummy package.json... needs full major.minor.build/patch syntax:

{
  "name": "Greasemonkey",
  "version": "2.3.0"
}
Martii commented 6 years ago

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 https://github.com/OpenUserJS/OpenUserJS.org/issues/401#issue-47385964 and will look back into this periodically.

Martii commented 4 years ago

Been watching this forever and there's absolutely no consistency in its usage... additional browsers have shown up, strange modifications, etc.