46 votes
Possibility to show in what browsers script works. planned
Scripts that don't use "GM_*" can work at Firefox (with Gresemonkey), Opera and probably at more browsers. Maybe scriptwriters can mark at what browsers their script can work correctly. And it will be show on the right as a small icons (they can work as a link to FAQ for specified browser). Or You can search on server for "GM_*" tags, and mark scripts as working only at Firefox or (if You don't find any "GM_*") Firefox and others.
aeosynth
// @compatibility Firefox 3.5+ Opera 10+
2 days ago
sine non qua
Lift this information from script attribute. Adopt a format within a comment section to prevent breaking script.
3 days ago
ed.galligan
Maybe have three options for each too. Like:
- Full support for:- blah blah blah
- Some support for:- blah blah blah
- No support for:- blah blah blah
For example a script might use @resource but still partially work in older Greasemonkeys etc.
11 months ago
jerone
So, options to select to be supported in and tested in:
- which browser,
- browser version,
- extention/addon (like GreaseMonkey or IE7PRO),
- extention/addon version.
11 months ago
mathemajor
ed.galligan beat me to the punch on this one. There are significant additions to JS between versions 1.8 and 1.9 as well as in GM 0.8. Many new functions in 1.9, like getElementsByClassName, are begging to be used by scriptwrites. Without some kind of @compat declaration supported in our scripts or a means by which to warn FF2 / GM 0.7 users of compatibility issues, problems could arise for users.
about 1 year ago
ed.galligan
Also.. in addition to this, it should show browser versions (as I'm sure there are javascript differences between FF3 and FF2, so we might soon see scripts that are incompatible with FF2)
about 1 year ago
ed.galligan
Scanning for GM_* =bad idea-not all GM functions have this prefix(doGMMeenoo), some other things are incompatible w/Opera(XPConnect) & some things aren't needed in Opera(unsafeWindow, window.content)
Any automated way would be tricky. Adding an "Opera compatible" checkbox when scripts are submitted would be far more effective, & would educate scripters in the fact that Opera scripts are possible.
about 1 year ago
jerone
This is good idea and I would vote for it as I had some points :p
It's on the planning to make my scripts work on the other browsers too.
I don't think scanning for "GM_*" is a good idea, as it can be used for for example cross browser scripting.
about 1 year ago