Metafilter Scroll Tag issues on FF Quantum November 28, 2017 5:05 PM Subscribe
Since updating to Firefox Quantum, and having had to reinstall the Metafilter Scroll Tag greasemonkey script, I'm having some issues with it ...
Win 7, latest Firefox Quantum.
After FF updated me with Quantum it uninstalled various things automatically. I had to reinstall the scroll tag greasemonkey script from here, and it doesn't seem to be playing nicely with Quantum.
When I open a thread, I have to click on the timestamp on the first comment to get the little arrow in the left margin. But it doesn't follow me down the page with a downward arrow. If I click on the timestamp of another comment, I get the arrow in the left margin again, but that's it. Going back to a thread, there's no way to navigate back to the last read comment.
Is anyone else having this issue, and is there any way I can fix it?
Win 7, latest Firefox Quantum.
After FF updated me with Quantum it uninstalled various things automatically. I had to reinstall the scroll tag greasemonkey script from here, and it doesn't seem to be playing nicely with Quantum.
When I open a thread, I have to click on the timestamp on the first comment to get the little arrow in the left margin. But it doesn't follow me down the page with a downward arrow. If I click on the timestamp of another comment, I get the arrow in the left margin again, but that's it. Going back to a thread, there's no way to navigate back to the last read comment.
Is anyone else having this issue, and is there any way I can fix it?
I just added an issue for this over at the github repo. If anyone wants to try their hand at fixing the script that's a great place to jump in.
posted by john hadron collider at 7:01 PM on November 28, 2017 [1 favorite]
posted by john hadron collider at 7:01 PM on November 28, 2017 [1 favorite]
I got it working in Tampermonkey, though not in Greasemonkey.
posted by Pronoiac at 2:27 AM on November 29, 2017
posted by Pronoiac at 2:27 AM on November 29, 2017
This brings up a good point. The two scripts that I cannot LIVE without are Deleted Posts and MultiFavorited Multiwidth.
I have Greasemonkey. After doing the FF update, the scripts worked fine for a few days, then stopped. So I installed Violentmonkey, which sort of got the latter script to work, but not the former. (I also got the latter to work on Chrome, but not the former). How do we know if it's the script itself, or the Monkey plug-in? Is it on a script by script basis? Is Tampermonkey better than the other two? Thanks for any insight about this for a dumb user...
posted by Melismata at 7:50 AM on November 29, 2017 [3 favorites]
I have Greasemonkey. After doing the FF update, the scripts worked fine for a few days, then stopped. So I installed Violentmonkey, which sort of got the latter script to work, but not the former. (I also got the latter to work on Chrome, but not the former). How do we know if it's the script itself, or the Monkey plug-in? Is it on a script by script basis? Is Tampermonkey better than the other two? Thanks for any insight about this for a dumb user...
posted by Melismata at 7:50 AM on November 29, 2017 [3 favorites]
I tried the Scroll Tag script on Tampermonkey too, with exactly the same result as on greasemonkey.
posted by essexjan at 9:41 AM on November 29, 2017
posted by essexjan at 9:41 AM on November 29, 2017
I am having the same issue, but on Windows 10. So this doesn't seem to be a Win 7 compatibility issue.
posted by ActingTheGoat at 9:42 AM on November 29, 2017
posted by ActingTheGoat at 9:42 AM on November 29, 2017
Well, this is weird. Here's a screengrab of my tampermonkey dashboard, which shows Scroll Tag enabled.
And here's a screengrab of the drop-down when I click on tampermonkey in the menu bar, showing no script is running, despite the dashboard saying it's enabled.
posted by essexjan at 9:55 AM on November 29, 2017
And here's a screengrab of the drop-down when I click on tampermonkey in the menu bar, showing no script is running, despite the dashboard saying it's enabled.
posted by essexjan at 9:55 AM on November 29, 2017
Pronoiac's updated script fixed this problem for me in Chrome (Version 62.0.3202.94) with Tampermonkey (v 4.4)
posted by briank at 10:48 AM on November 29, 2017
posted by briank at 10:48 AM on November 29, 2017
Yeah, the weirdness continues. MultiFavorited Multiwidth does NOT work now, via Violentmonkey, despite assurances that it is installed. But I LIKE FF...:(
posted by Melismata at 11:16 AM on November 29, 2017
posted by Melismata at 11:16 AM on November 29, 2017
Melismata, I just got Scroll Tag to work in Tampermonkey/FF by following heyho's workaround - unticking 'use secure browsing' in my preferences. You could try that.
posted by essexjan at 11:19 AM on November 29, 2017
posted by essexjan at 11:19 AM on November 29, 2017
May I jump in to ask if anyone has updated the Metafilter "New Posts - Comments" script for Greasemonkey for Firefox Quantum? I have it in an older version of FF that runs on my old iMac running 10.6.8 but it won't work on my Macbook running Sierra and FF Quantum (haven't upgraded to High Sierra until Apple figures out what to do with their log-in exploit).
posted by Lynsey at 2:34 PM on November 29, 2017
posted by Lynsey at 2:34 PM on November 29, 2017
It definitely seems to be a https issue. I've tried both greasemonkey and tampermonkey and the script only works on unsecured browsing.
posted by essexjan at 3:15 PM on November 29, 2017
posted by essexjan at 3:15 PM on November 29, 2017
It might be best if discussion about scripts other than Scroll Tag go over in the more general scripts thread.
essexjan, did you install the version of the script I linked? Your Tampermonkey dashboard looks like it wasn't updated.
posted by Pronoiac at 5:33 PM on November 29, 2017
essexjan, did you install the version of the script I linked? Your Tampermonkey dashboard looks like it wasn't updated.
posted by Pronoiac at 5:33 PM on November 29, 2017
Yes, Pronoiac, I reinstalled both grease-and tamper-monkeys, and the scripts, and tried them both separately. Both work in unsecured browsing, so it looks as if this is related to the https switch.
posted by essexjan at 11:55 PM on November 29, 2017
posted by essexjan at 11:55 PM on November 29, 2017
That's weird, I updated the script to work with https.
posted by Pronoiac at 7:37 AM on November 30, 2017
posted by Pronoiac at 7:37 AM on November 30, 2017
I just got it working on https in Tampermonkey, but not Greasemonkey.
posted by essexjan at 8:15 AM on November 30, 2017
posted by essexjan at 8:15 AM on November 30, 2017
At the top of that script you linked, it says:
// @include http://metafilter.com/*
// @include http://*.metafilter.com/*
Have you changed those to https: in your installed script? If not, that may help.
posted by crysflame at 1:20 PM on November 30, 2017
// @include http://metafilter.com/*
// @include http://*.metafilter.com/*
Have you changed those to https: in your installed script? If not, that may help.
posted by crysflame at 1:20 PM on November 30, 2017
essexjan, right now, I prefer the Tampermonkey user experience, as Greasemonkey isn't recognizing user scripts on Github. Upon retrying, my issues in Greasemonkey may have been in the user interface. I apparently disabled the script, but once I re-enabled and updated it again, from a local server, it looks like it works.
Right now, Greasemonkey is frustrating and confusing. My "helping" someone with it could easily make the matter worse.
crysflame, see the updated script. (Note, that's different than my earlier comment, and the post.)
posted by Pronoiac at 2:15 PM on November 30, 2017
Right now, Greasemonkey is frustrating and confusing. My "helping" someone with it could easily make the matter worse.
crysflame, see the updated script. (Note, that's different than my earlier comment, and the post.)
posted by Pronoiac at 2:15 PM on November 30, 2017
Thanks for your help, Pronoiac, which is invaluable for people such as me who aren't very technically adept. It's working well in Tampermonkey, so I'll stick with that.
posted by essexjan at 1:03 AM on December 2, 2017 [1 favorite]
posted by essexjan at 1:03 AM on December 2, 2017 [1 favorite]
I recoded the deleted-posts script into a browser extension last night. I don't know how closely it matches the original script as I never used it, and only had a screenshot to guide me, so if anyone uses it and finds it's missing functionality, please let me know.
In addition, if anyone wants to take the code and make a userscript from it, here's the source code. Note, it has a separate CSS file (the main reason I prefer coding extensions to userscripts), so make sure to include that detail in the JS.
posted by urbanwhaleshark at 9:36 AM on December 2, 2017 [2 favorites]
In addition, if anyone wants to take the code and make a userscript from it, here's the source code. Note, it has a separate CSS file (the main reason I prefer coding extensions to userscripts), so make sure to include that detail in the JS.
posted by urbanwhaleshark at 9:36 AM on December 2, 2017 [2 favorites]
please let me know
So far, so good.
Many, many thanks!
posted by Mister Bijou at 12:54 AM on December 3, 2017 [1 favorite]
So far, so good.
Many, many thanks!
posted by Mister Bijou at 12:54 AM on December 3, 2017 [1 favorite]
« Older Resetting expectations about U.S. political... | Our Great Shared National Treasures Newer »
You are not logged in, either login or create an account to post comments
posted by restless_nomad (staff) at 5:09 PM on November 28, 2017