GeezerVison is showing github.com — Script editor should expose (text) resources · Issue #2733 · greasemonkey/greasemonkey
Script editor should expose (text) resources #2733DescriptionReacted by darkred and SLC Activityadded this to the This milestone has been deleted milestone on Nov 28, 2017Sxderp commented on Nov 30, 2017
... expose (text) resources ...
I suppose detection through mime-type?
Slightly tangent to the issue, should @require and @resource be re-fetched when the scripts are updated? That is, through the updater interface / autoupdate when said things are implemented. Of course that'd bring up concerns with local modifications, but that issue applies to local modifications of the script itself too. arantius commented on Nov 30, 2017 CollaboratorAuthor More actions
I suppose detection through mime-type?
Yep.
Slightly tangent to the issue, should @require and @resource be re-fetched when the scripts are updated?
Like 3.x does. Generally yes. Any local modification: don't (automatically) overwrite (but also expose a purely manual "force" action). removed this from the This milestone has been deleted milestone on Jan 19, 2018arantius commented on Nov 8, 2023 CollaboratorAuthor More actions arantius commented on Nov 29, 2023 CollaboratorAuthor More actions This should be done. I could use your help testing this! Checkout or download Greasemonkey's source code, then follow the documentation for installing an extension during development. As far as I know this will break installed scripts, so you should use about:profiles to create and launch a new blank Firefox profile to do so, rather than overwriting your existing Greasemonkey install. (Maybe take a Greasemonkey backup first to be safe.)
Any testing results, positive or negative, would be great. added a commit that references this issue on Nov 24, 2024This issue will close once commit fbb3380 is merged into the 'master' branch.fbb3380
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|