GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Script editor should expose (text) resources · Issue #2733 · greasemonkey/greasemonkey

Script editor should expose (text) resources #2733

New issue
Copy link
New issue
Copy link
Closed
Closed
Script editor should expose (text) resources#2733
Copy link
Milestone
4.12

Description

@arantius
arantius
opened on Nov 28, 2017
Issue body actions

I've got a script ( https://arantius.com/misc/greasemonkey/ebay-butler.user.js ) which has a CSS resource ( https://arantius.com/misc/greasemonkey/imports/ebay-butler.css ). That resource is injected into the page. I need to fix its contents.

Now I can only do that by remotely editing the file and re-installing the whole script. I should be able to edit the resource in place.

Reacted by darkred and SLC

Activity

  1. arantius
    added this to the This milestone has been deleted milestone on Nov 28, 2017
  2. Sxderp commented on Nov 30, 2017

    @Sxderp
    Sxderp
    on Nov 30, 2017
    Contributor
    More actions

    ... 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.

  3. arantius commented on Nov 30, 2017

    @arantius
    arantius
    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).

  4. arantius
    removed this from the This milestone has been deleted milestone on Jan 19, 2018
  5. arantius
    added this to the Features milestone on Feb 22, 2018
  6. IvanCen
    added a commit that references this issue on Nov 22, 2021

    Update README.md

    735732f
  7. arantius
    added
    bankruptcyIssues that have been closed for "bug bankruptcy". Usually very old non-active issues.Issues that have been closed for "bug bankruptcy". Usually very old non-active issues.
    on Nov 2, 2023
  8. arantius
    closed this as completedon Nov 2, 2023
  9. arantius
    removed
    bankruptcyIssues that have been closed for "bug bankruptcy". Usually very old non-active issues.Issues that have been closed for "bug bankruptcy". Usually very old non-active issues.
    on Nov 8, 2023
  10. arantius
    reopened this on Nov 8, 2023
  11. arantius commented on Nov 8, 2023

    @arantius
    arantius
    on Nov 8, 2023
    CollaboratorAuthor
    More actions

    This was something I always wanted (see how long ago this was filed), and a recent new batch of work to do got me to look into it again.

    FWIW see https://gist.github.com/arantius/0dc6a6f59e70e7e8f2d2905c77c2d393 which is my testing script while I work on this feature.

  12. arantius
    modified the milestones: Features, 4.12 on Nov 8, 2023
  13. Repository owner deleted a comment from h8nor on Nov 8, 2023
  14. arantius
    closed this as completedin fbb3380on Nov 9, 2023
  15. arantius
    added a commit that references this issue on Nov 29, 2023

    Editor: derive unknown resource URLs.

    8bd283f
  16. arantius commented on Nov 29, 2023

    @arantius
    arantius
    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.

  17. Zombie10
    added a commit that references this issue on Nov 24, 2024

    Allow editing (text) resources.

    This issue will close once commit fbb3380 is merged into the 'master' branch.
    fbb3380
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      • 4.12

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.