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.

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

Open
TimidScript opened this issue Oct 31, 2014 · 4 comments
Open

List Browser Support #401

TimidScript opened this issue Oct 31, 2014 · 4 comments
Labels
feature Something we don't already have implemented to the best of knowledge but would like to see. needs vote Give a thumbs up or thumbs down on a request for the first comment in the issue.

Comments

@TimidScript
Copy link

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.

@TimidScript TimidScript changed the title Browser Support UI List Browser Support Oct 31, 2014
@jerone
Copy link
Contributor

jerone commented Oct 31, 2014

@Martii Martii added the feature Something we don't already have implemented to the best of knowledge but would like to see. label Oct 31, 2014
@Martii
Copy link
Member

Martii commented Oct 31, 2014

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 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 Martii added the needs vote Give a thumbs up or thumbs down on a request for the first comment in the issue. label Jul 12, 2018
@Martii
Copy link
Member

Martii commented Jul 12, 2018

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.

@Martii
Copy link
Member

Martii commented Sep 10, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something we don't already have implemented to the best of knowledge but would like to see. needs vote Give a thumbs up or thumbs down on a request for the first comment in the issue.
Development

No branches or pull requests

3 participants