On userscripts.org site, I suggest you ...

Possibility to show in what browsers script works.

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.

103 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    matrixik shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    12 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • kwah commented  ·   ·  Flag as inappropriate

        Personally I'd go for these categories for each browser / compatibility group::

        * Tested - working
        * Tested - major issues / not working
        * Tested - small / minor issues
        * Not Tested

        These could be set by the scriptwright to indicate what they believe it to be / what it should be, and users could vote for different combinations (eg, v1.1 or a script w/ff3.6; v1.1 w/ff4; v2.0 w/Opera etc) in a similar way to how the wordpress plugins site does it.

      • waz commented  ·   ·  Flag as inappropriate

        just update new version of MWAP.. but seems not working properly.. MWAP menu gone,etc so I should do manually :((

      • sizzlemctwizzle commented  ·   ·  Flag as inappropriate

        I really like this. Although it probably wouldn't be perfect(since I often define those missing functions in some of my scripts and that wouldn't be noticed), it would still be a huge help.

      • Marti commented  ·   ·  Flag as inappropriate

        More automated would be useful though. Although having a uso: namespaced key might be useful too. *thumbs up*

      • sine non qua commented  ·   ·  Flag as inappropriate

        Lift this information from script attribute. Adopt a format within a comment section to prevent breaking script.

      • ed.galligan commented  ·   ·  Flag as inappropriate

        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.

      • mathemajor commented  ·   ·  Flag as inappropriate

        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.

      • ed.galligan commented  ·   ·  Flag as inappropriate

        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)

      • ed.galligan commented  ·   ·  Flag as inappropriate

        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.

      • Adminjerone (Admin, Userscripts.org) commented  ·   ·  Flag as inappropriate

        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.

      Feedback and Knowledge Base