-
Notifications
You must be signed in to change notification settings - Fork 517
Description
When installing a script on Greasy Fork, the user is directed to the .user.js URL. Greasy Fork expects that a script manager will take over that request. After 2 seconds, Greasy Fork will direct the user's original tab to a post-install page, offering help if the script didn't install, a link to post feedback on the script, etc.
With TM on Chrome, this all works, but the user's browsing history loses an entry.
- Go to https://greasyfork.org/
- Click any script link (under the heading "Step 2" on the home page)
- Click "Install this script". TM install tab opens.
- Install or cancel, doesn't matter. TM install tab closes. User's left on Greasy Fork post-install page.
- Click browser back.
Now we're back on the Greasy Fork home page instead of the script page we visited in step 2 above.
Environment
- Browser and Version: Chrome 142.0.7444.175
- Tampermonkey version: 5.4.0
- Operating System and Version: Ubuntu 24.04.3 LTS
Additional context
I can change the logic from Greasy Fork's side if needed. Currently the button press is handled by JS, which eventually sends the user with location.href to the .user.js, then after a 2s timeout, sends the user with location.href to the post-install page. https://github.com/greasyfork-org/greasyfork/blob/main/app/javascript/install.js