Join the chat at https://gitter.im/soscripted/sox

SOX v2.3.0

Stack Overflow Extras (SOX) is a project that stemmed from the Stack Overflow Optional Features (SOOF) project.

The SOX userscript adds a bunch of optional features to all sites in the Stack Exchange network. These can be toggled on or off from an easy to use control panel (see screenshot below).

Note: This project has no relation to Stack Overflow or Stack Exchange; it is simply a userscript that enhances the sites!

Installation & Requirements

  1. Install Greasemonkey (for Firefox) or Tampermonkey (for Chrome or Safari). These are userscript managers that must be installed in order for this to work, as the script relies on certain GM_* functions in order to save your settings!
  2. Install the script. Clicking on 'install' below will make your userscript manager prompt you automatically to install it.

  3. Go to any site in the Stack Exchange Network (e.g. Super User or Stack Overflow). You will automatically be asked to choose and save your settings. A toggle button (gears icon) will be added to your topbar where you can change these later on:

newdialog

What features are included?

A full list of all the features is available on the SOX wiki page here.

Bugs and Feature Requests

Please post bugs and feature requests as issues on Github, where we can track them easily and push updates quickly. Please do not post them as answers on Stack Apps -- they are much harder to manage!

Contribute

Pull requests to add new features or improve the existing ones, etc. are welcome! Please head to the Contributing wiki page to get started.

Changes

Please see the change log at Stack Apps.

  • 2
    If you use GM setValue() instead of a cookie, then your script will remember the options across every site. They could even be synched from one machine to another, if the user desires. – Brock Adams Jan 11 '15 at 22:47
  • 1
    Here's one feature you might consider: meta.stackexchange.com/questions/249679/… (There's no way that would get into SOUP, but as an optional feature...) – Ilmari Karonen Feb 28 '15 at 20:03
  • 2
    For anyone who uses Safari, as a replacement for Greasemonkey, etc., you can use NinjaKit. – Cullub Feb 8 '16 at 12:47
  • 1
    @ᔕᖺᘎᕊ, it did in Firefox once upon a time. Haven't rechecked in a while but it still should. – Brock Adams Mar 12 '16 at 10:59
  • 1
    @iRove sorry, not really; if the cogs icon got hidden then there would be no way to ever get back to the settings panel again if you ever wanted to disable a feature, or more importantly enable a new feature that comes in new versions. If you really dislike it, if you have an ad-blocker, you can 'block' the element and unblock it in the future...? If you have any other ideas, I'd be happy to look into them, but there needs to be a way to open the settings panel again :/ – ᔕᖺᘎᕊ Aug 15 '16 at 18:08
  • 1
    @ᔕᖺᘎᕊ Thank you for the quick response! Wow, clever. I'll try to use my ad-blocker to enable/disable the settings cog and get back to you in a second. Love the features in the script! – iRove Aug 15 '16 at 18:09
  • 1
    @ᔕᖺᘎᕊ Your solution with the ad-blocker worked perfectly. Just blocked the element on all stack exchange sites, and can unblock it whenever I want to customize. I appreciate the time and effort you put into this project! :-) – iRove Aug 15 '16 at 18:20
  • 1
    Yes, indeed. I just installed it a couple of days ago. Had to come here to figure out I needed the development version to make it work on Stack Overflow, but everything is good now. Only thing I don't like is it tends to make the page loads laggier, and elements jump around after load, which makes them moving targets for the mouse. But that's really unavoidable with a userscript and not really your fault. It's nice work overall. – Cody Gray Aug 30 '17 at 4:07
  • 1
    SOX seems non-functional now that the new top-bar has been rolled out – Valorum Oct 10 '17 at 18:42
  • 1
    @Valorum many many months later, if you're still interested, I managed to fix it... sorry for how long this took – ᔕᖺᘎᕊ Feb 24 at 20:44
  • 1
    @ᔕᖺᘎᕊ - It's appreciated. – Valorum Feb 24 at 21:01
  • 1
    @sag It should be! Some people in the past have told me about issues when both are installed but I try my best to fix them :) If you use SOX with SOUP and notice something off, please do tell me! – ᔕᖺᘎᕊ Jul 16 at 20:47
  • 1
    @ᔕᖺᘎᕊ It seems the problem is due to Greasemonkey. I replaced it with Tampermonkey and now it's working fine. Probably that was the reason many of my scripts didn't work in FF. But I don't know why it asks To complete the SOX installation, you need to get an access token! Please press "OK" to continue and follow the instructions in the window that opens. every time I open a new page – phuclv Aug 21 at 16:20
  • 1
    I didn't see any popup blocked message appeared. But I managed to get the token by clicking the gears button and click the key at the bottom – phuclv Aug 21 at 17:00
  • 1
    @ᔕᖺᘎᕊ, Thanks for finding the time to get back into this (and thanks to others who have worked on it)! Once you use SOX, it's hard to be without it. I've stuck with FF 52 ESR because I rely on some old add-ons that don't have replacements, and I'm running Tampermonkey. I've encountered some bugs, but they could well be FF-related, so I won't even bother reporting them unless I replicate them in a current FF. The current version looks great, BTW. – fixer1234 Aug 21 at 20:16

12 Answers 12

up vote 14 down vote accepted

Change Log

On 12/02/16, SOOF was renamed to SOX and rewritten by ᔕᖺᘎᕊ and ᴉʞuǝ. The versioning was reset.

  • 02/09/18 - v2.3.0:
    • Greasemonkey is no longer supported. Please use Tampermonkey
    • You can now import and export your settings from the SOX dialog
    • Added feature to paste images directly into SE textareas without using the image dialog
    • The old topbar is no longer supported (affects Area 51 mainly)
    • The feature that lets you watch posts for edits will soon be available as a separate userscript, and has been removed from SOX
    • Behind the scenes refactoring by @GaurangTandon
    • The fixed topbar feature has been deprecated as it is natively supported now!
    • Added feature to only show comment flagging/upvote buttons on hover (like it used to be)
    • Added feature to add the tag wiki link on the new tag popup box
    • Various bug fixes
  • 15/06/18 - v2.2.0:

    • lots of bug fixes (see milestone link above)
    • fixes major issue where SOX settings cog didn't show up
    • works on FF again
    • deprecated a few features
    • added a few features (disableVoteButtons, addTimelineAndRevisionLinks)
  • 24/02/18 - v2.1.0:

    • various bug fixes
    • many new features added
    • updated to be compatible with the new topbar and site design changes made by SE
    • versioning changed to MAJOR.MINOR.PATCH style
  • 21/12/16 - v2.0.2:

    • revamped dialog to include info hover buttons
    • added disableOwnPostVoteButtons, flagPercentageBar, replyToOwnChatMessages (thanks @IStoleThePies), hideCertainQuestions, inlineEditorEverywhere (thanks @nicael) features
    • fixed enhancedEditor feature
    • fixed downvotedPostsEditAlert feature
    • fixed issues with certain features not working in Firefox
    • deprecated addEllipsis feature
    • reordered features in dialog and made more categories for easier searching
    • added debug mode to help SOX devs fix bugs quicker and easier
    • features no longer run on page where they weren't designed to run on, fixing lots of weird bugs
    • completely rewritten fixedTopbar feature to work on all sites without manual configuration (thanks @IStoleThePies!)
    • fixed design issues with features with their own dialogs (thanks @IStoleThePies!)
    • fixed long-standing bug where the fancy vote buttons caused tearing on Skeptics.SE (thanks @IStoleThePies!)
    • fixes bugs in various features, which can be seen in the v2.0.2 Github milestone
  • 01/10/16 - v2.0.1:

    • many more bug fixes
    • fixed major issue where script did not work at all on Firefox
    • fixed cross-browser compatibility issues with the access token
    • rewritten downvotedPostsEditAlert feature to make it easier to use and more functional
    • known bug: the downvotedPostsEditAlert feature is flaky right now
  • 02/07/16 - v2.0.0:
    • Completely refactored version fixing a lot of bugs
    • deprecated feature that hides the search bar, feature that removes excessive exclamation marks from comments, quickCommentShortcuts feature
    • removed Ace Editor from the enhanced editor feature
    • bug fixes
    • fixed timing issues
    • setting dialog UI updates
    • script now request oauth access after installing to prevent rate limiting on certain features
    • added alignBadgesByClass, quickAuthorInfo, warnNotLoggedIn, hotNetworkQuestionsFiltering, hiddenCommentsIndicator features
  • 05/04/16 - v1.0.3:
    • SOX settings dialog now has a search bar and is a menu just like the inbox
    • new features
    • bug fixes
  • 06/03/16 - v1.0.2:
    • rewrote parts of script to allow better control over what features run when
    • bug fixes
    • added new feature (enhanced editor)
  • 28/02/16 - v1.0.1:
    • lots of bug fixes
    • rewrote some helper functions
    • built in error handling
  • 12/02/16 - v1.0: SOOF is now SOX.

Please see the revision history for this post to see the change log for SOOF, before it was renamed.

I had some trouble getting your script to run on Firefox / Greasemonkey. It turns out that I needed to replace this line:

// @require http://ajax.googleapis.com/ajax/libs/jqueryui/1.8/jquery-ui.min.js

with:

// @require https://ajax.googleapis.com/ajax/libs/jquery/1.8/jquery.min.js
// @require https://ajax.googleapis.com/ajax/libs/jqueryui/1.8/jquery-ui.min.js

With this change, the script seems to work on Firefox (although I haven't properly tested all the features yet).


I also noticed a few issues with the options pop-up:

  • The pop-up appears in a weird location, partially off the screen. I managed to fix this issue by changing the style attribute from the original

    display:inline-block; position:fixed; margin:auto; top:50%;
    margin:-100px 0 0 -150px; z-index:2; background-color:gray;
    color:white; -webkit-border-radius: 15px; -moz-border-radius: 15px;
    border-radius: 15px;
    

    to:

    display:inline-block; position:fixed; top:10px; left:50%; width:500px;
    margin-left:-250px; z-index:2; background-color:gray; color:white;
    padding: 10px; border-radius: 15px;
    
  • Having the checkboxes at the end of the option descriptions is somewhat ugly awkward; they'd look nicer and be easier to click if they were at the beginning. You could also simplify the HTML by nesting the checkboxes inside their labels, as in:

    <label><input type=checkbox id=id checked> Text </label><br>
    
  • Every time I open the options dialog, all the checkboxes get checked. It would be much better to have them retain their previous state.

  • Closing the options dialog using the "Close" link (instead of the "Submit" button) resets all the features to active, due to this line:

    GM_deleteValue('featureOptions'); //Delete the setting when clicked
    

    In particular, this interferes with trying to make the checkboxes retain their state (which is otherwise fairly simple). Simply removing this (apparently unnecessary) line makes it work better; the new settings will override the old when submitted, anyway.

  • I don't see any particular reason why I shouldn't be allowed to disable all the features, if I want. That extra check seems just plain useless to me.

  • Also, the "Options were saved!" alert after editing the options gets kind of annoying after a while.


Also, the "add features" link injection doesn't seem to work on the fancy new user profile currently in testing on meta.SE. You might want to add compatibility for that, especially since it'll likely be rolled out network-wide sooner or later.

  • 1
    Thanks for telling me about the incompatibility with Firefox, will look into that. I don't know why the options box comes off-screen, works for me, so I'll try using your CSS on different resolutions - that may be the problem...? I'll make the text come after the checkbox (I'm not the best in design and user interaction ;p). I'll make it so that the checkboxes fill from the settings. But could you clarify the last bullet please? I don't exactly get what you say - are you saying there should be an option to disable all the features? And I'll see what I can do about the MSE profile change. – ᔕᖺᘎᕊ Feb 28 '15 at 18:30
  • I just meant that the code that checks if all the checkboxes are unchecked, and, if so, brings up an alert saying "Please check at least one box!", seems to be completely unnecessary (and mildly annoying when testing). – Ilmari Karonen Feb 28 '15 at 18:35
  • Ps. I forked your gist and committed fixes for some of the issues listed above. I don't think I can create a proper pull request for a gist, but you may want to review the changes and merge them yourself, if they look good to you. – Ilmari Karonen Feb 28 '15 at 18:50
  • Whoops...! Only just saw your message! I just published the gist and looks like they're the same changes- sorry! Regarding your last edit-isn't that being a bit too pedantic? I think it's unnecessary-I agree it can be a pain in testing, but can be useful when being used normally - or you might just think nothing happened without checking the console, and I don't think you should need to do that. Your CSS works in different resolutions, so I've used that - thanks again for that - and I'm still in the process of checking with Firefox incompatibilities. Please accept my edit for the status-* tags – ᔕᖺᘎᕊ Feb 28 '15 at 19:15
  • Sure, accepted. I can live with the alert, but I don't really see why it's necessary; the dialog closing already indicates that something happened, and generally when you click a "Save" button (BTW, shouldn't it say something like "Save settings" instead of "Submit"?), you'd assume it saved the settings. With the new persistent checkboxes, it's also easy enough to verify if you don't trust it. – Ilmari Karonen Feb 28 '15 at 19:26
  • You put a good argument forward ;p I guess... you're right... I'll remove the alert and rename the button in the next version (when I've tested on Firefox and also add the needed require) :) – ᔕᖺᘎᕊ Feb 28 '15 at 19:28
  • Thanks, no problem. :) Ps. I notice that there's already some overlap (e.g. this) between your script and SOUP, and I think I might want to steal a few more of the less controversial features (with appropriate credit, of course!). ;) That said, I think your script will make an excellent complement to SOUP (which doesn't come with a settings panel to toggle features, and so generally avoids anything controversial). You may have noticed that I've added a link to your script from the SOUP home page. :) – Ilmari Karonen Feb 28 '15 at 19:32
  • 1
    Thanks for adding this link to SOUP :) I have no problem with you stealing some things - I think the many difference between SOUP and this is that SOUP generally fixes bugs while this (no acronym unfortunately ;( - AOF?) adds features - so a slight overlap is obviously going to happen (eg. a bug, but not actually a bug = bug+feature-request), but a full on replica is just useless ;p. And I have no problem with you stealing snippets for SOUP :) – ᔕᖺᘎᕊ Feb 28 '15 at 20:14

I'm using v1.4 and I noticed that the following features seem to clash somehow:

  • Make the topbar fixed (stay at the top as you scroll)
  • Make the vote buttons sticky

The topbar stays at the top, that works fine, but when scrolling, the upvote button disappears under the topbar. See the following screenshot for an example:

screenshot

It would be great if the upvote button was visible all the time.

  • I'll look at this and your other bug report and push 1.5 out by this weekend hopefully :) +1 for both :) – ᔕᖺᘎᕊ Jul 7 '15 at 16:23
  • 1
    This issue is now solved (at least on developer branch) ;) – Daniel Aug 18 '15 at 7:37

This doesn't work for Stack Overflow, due to the new topbar design.

Workaround:

For now, you must use the Dev version to make it work on SO.

  • This has been fixed in the Dev version, please could you install that and it try it? :) – ᔕᖺᘎᕊ Feb 17 '17 at 17:05
  • @ᔕᖺᘎᕊ I will, thanks for informing me. Keeping this here. EDIT: Did it, and it's good. I'm not sure how to keep both versions though... – EKons Feb 17 '17 at 17:05
  • You can delete the original version :) you only need to keep one version, and the Dev is newer than the other one so you can just delete that one :) – ᔕᖺᘎᕊ Feb 17 '17 at 17:19

(thanks to ArtOfCode, that is :)

This appears to break the styling of title bars on at least beta SE sites. It would be good if it didn't obscure the top part of the title bar.

To see what I mean:

Without 'Fix topbar position' enabled:

enter image description here

With it enabled:

enter image description here

v1.5 DEV has a problem with the "Extra Mod Diamond" added to the toolbar when used in combination with stackoverflow-code-expando

When stackoverflow-code-expando is disabled there is no issue.

Appears to be a z-ordering issue?

Firefox 38.0.5, Windows 7 4Bit.

Here is a screenshot of the problem from StackOverflow.

enter image description here

  • yeah - it's probs z-index. It's the weekend now(!) - so I'll update the script with a fix to this (and the freehand circles css bug!) :) – ᔕᖺᘎᕊ Jun 26 '15 at 16:21
  • Cheers, have a virtual drink on me ;) – DavidPostill Jun 26 '15 at 16:28
  • Anything a bit more... Legal? :P – ᔕᖺᘎᕊ Jun 26 '15 at 16:48
  • 1
    Ah, I just spotted your age :/ – DavidPostill Jun 26 '15 at 16:53
  • I've pushed an update to the develop branch - can you update and check if it's fixed please? – ᔕᖺᘎᕊ Jun 27 '15 at 16:53
  • 1
    @ᔕᖺᘎᕊ updated. Waiting for a blue diamond to test. – DavidPostill Jun 27 '15 at 16:59
  • @ᔕᖺᘎᕊ Hmm. Strange. New version was installed yesterday (white diamond) but today a) doesn't appear to be running (no diamond at all) and b) no "add features" visible on profile pages :(. I've disabled all other scripts and reinstalled, restarted firefox, but no change ... – DavidPostill Jun 28 '15 at 8:15
  • Anything in console...? – ᔕᖺᘎᕊ Jun 28 '15 at 8:43
  • Timestamp: 28/06/2015 09:44:50 Error: The connection to wss://qa.sockets.stackexchange.com/ was interrupted while the page was loading. Source File: cdn.sstatic.net/Js/full.en.js?v=8ac5fbfa1bd9 Line: 1 – DavidPostill Jun 28 '15 at 8:46
  • Timestamp: 28/06/2015 09:44:52 Error: jQuery is not defined Source File: file:///C:/Users/DavidPostill/AppData/Roaming/Mozilla/Firefox/Profiles/5ubcfk8m.default/gm_scripts/SE_Additional_Optional_Features/jquery-ui.min.js Line: 5 – DavidPostill Jun 28 '15 at 8:46
  • Timestamp: 28/06/2015 09:45:34 Error: TypeError: document.getElementById(...) is null Source File: chrome://web-developer/content/overlay/javascript/overlay.js Line: 7333 – DavidPostill Jun 28 '15 at 8:46
  • Let us continue this discussion in chat. – DavidPostill Jun 28 '15 at 8:48
  • @ᔕᖺᘎᕊ Any update? – DavidPostill Jul 16 '15 at 17:45
  • Whoops! Can you please try installing v1.5? I pushed it yesterday to the main branch - it fixed someone else's problem on Firefox - it should fix yours as well! – ᔕᖺᘎᕊ Jul 16 '15 at 17:57
  • 1
    @ᔕᖺᘎᕊ No change to the stackoverflow-code-expando issue :/. The good news is the diamond and "add features" is back ;) – DavidPostill Jul 16 '15 at 18:09

The Change the 'share' link to show link as markdown format feature has the annoying side-effect that the replaced text in the form [text](link) is not selected when clicking the share link.

It is pretty annoying to manually having to select the text - it would be better if the whole text was already selected, so I could copy it directly from the box.

Fixed in this build

This is really borked on askubuntu:

enter image description here

  1. The bar position is broken.
  2. The vote button is broken.
  3. The post content moves to the left.
  • I presume this is with fixed topbar? You've just managed to get 2 of the bugs related to the fixed topbar happen at one time: The vote button is broken: github.com/shu8/SE_OptionalFeatures/issues/5. The post content moves to the left: That happens at random times - it's a glitch, but I've never been able to properly repro it! So I can't fix it... however a scroll up and down fixes it. – ᔕᖺᘎᕊ Jul 26 '15 at 20:14
  • However, the bar position is broken is new - I've never used Ask Ubuntu before so I didn't notice it. But sorry - I'm not going to change this because it only affects Ask Ubuntu :/ BTW Please can you post any issues or feature requests on github now? Thanks! :) – ᔕᖺᘎᕊ Jul 26 '15 at 20:17
  • The fixed topbar has a lot of issues with it... I might just get rid of it... I'm not too sure yet - I'll think about it! – ᔕᖺᘎᕊ Jul 26 '15 at 20:18
  • 1
    @ᔕᖺᘎᕊ Here you go! – Universal Electricity Jul 27 '15 at 3:16

'Get access token?' link broken, generates the following error:

VM2649:3464 Uncaught channelUrl must be under the current domain
r @ VM2649:3464
(anonymous function) @ VM2649:3740
n.event.dispatch @ VM2649:8
r.handle @ VM2649:8

Running on chrome, Version 49.0.2623.110 m

Works only when clicking it on http://meta.stackexchange.com/ - If this is intended, maybe show a warning or only display the link when on meta.stackexchange.com

  • 1
    Sorry! I completely forgot about the meta SE URL I gave.. I'll fix this ASAP. If you could post this on GitHub, I can ping you over there when it gets fixed :) Thanks for the bug report! – ᔕᖺᘎᕊ Apr 10 '16 at 12:08
  • No worries :) - Bug report is here: github.com/soscripted/sox/issues/50 – Rob Apr 10 '16 at 12:16

Installation completion dialog box opens every time I visit a SE page.

Solution:

  1. Open browser console.
  2. Click on the first URL to get your SE access token.
  3. Approve the extension.

After that, the popup will reopen, you just need to save your preferred settings again.

  • A popup should have opened. Check you haven't got a pop-up blocker blocking it. And would it be possible to put these in 1 answer please? (Or delete the first one! :) – ᔕᖺᘎᕊ Feb 17 '17 at 17:37
  • @ᔕᖺᘎᕊ The thing is that I have already done the thing. Yes the pop-up did open the first time, after that the popup doesn't open but the dialog box still shows up. I don't think the dialog box or the popup should show up after installation has been completed. And no, it's not possible, since they are entirely different issues. – EKons Feb 17 '17 at 17:40
  • Can you make sure you only have 1 version installed, and if it still happens, click reset at the bottom of the dialog and refresh the page. If it still happens, please open the console and post the contents here. We prefer to use github for reporting bugs because it makes it more manageable, that's the only reason I asked to delete or merge them, but it's fine – ᔕᖺᘎᕊ Feb 17 '17 at 17:45
  • @ᔕᖺᘎᕊ Yes it seems I only have 2.0.22 (Dev). I will try what you recommend and see if it works. – EKons Feb 17 '17 at 17:50
  • 1
    @ᔕᖺᘎᕊ The console had a URL which I clicked, approved and got an access token. Problem seems to be solved now, although I'd like something like local memory. EDIT: When I tried to edit this post to include a solution, the popup suddenly appeared. I just had to re-save to solve this time. – EKons Feb 17 '17 at 18:05

My SOX appears to "time-out" after 24 hours. Some features are still available, but elements like 'Show tags for the question an answer belongs to on search pages (for better context)' stop working.

Entering the console shows this link

Mixed Content: The page at 'Stack Overflow Extras (SOX)' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://stackapps.com/posts/6091/revisions'. This request has been blocked; the content must be served over HTTPS.

And clicking the link goes to

{"error_id":403,"error_message":"key is not valid for passed access_token, token not found.","error_name":"access_denied"}


  • This issue can be resolved by resetting SOX and requesting a new token.
  • Hi, could you try installing the development version: github.com/soscripted/sox/raw/dev/sox.user.js and see if the problem still occurs? :) – ᔕᖺᘎᕊ Apr 25 '17 at 6:24
  • @ᔕᖺᘎᕊ - I've noticed that the link you get when you open the console says "soscripted.github.io/sox/#access_token=ts67upOKAiRKFZgf*xFSqQ))&expires=86399". Presumably that's in seconds, hence why it times out after a day. – Valorum Apr 25 '17 at 14:31
  • @ᔕᖺᘎᕊ - I don't know how to do that. I'm reliant on clicking the "install" button. The link you sent me to doesn't appear to have one of those – Valorum Apr 25 '17 at 14:32
  • When I click update, then open the console it say "ados.js Failed to load resource: net::ERR_BLOCKED_BY_CLIENT (unknown) SOX: Deleting feature "Unsorted-parseCrossSiteLinks" (category rename?) – Valorum Apr 25 '17 at 14:33
  • 1
    @ᔕᖺᘎᕊ -Ah, now that's new. There's a key-shaped icon that says "request new access token". When I click it, it takes me to a page that asks for "perpetual access", then takes me to another page that gives me a key and there's no "expires=" in the URL. – Valorum Apr 25 '17 at 14:35
  • Great! Looks like it should work now! :) – ᔕᖺᘎᕊ Apr 25 '17 at 16:48
  • 1
    @ᔕᖺᘎᕊ - I shall report back in precisely 23.5 hours :-) – Valorum Apr 25 '17 at 17:00
  • 1
    @ᔕᖺᘎᕊ - That worked just fine :-) – Valorum Jul 22 '17 at 8:38

The recent top bar rollout seems to have broken the tools again as I am no longer able to access the menus such as settings or the meta link which shows new activity and my name is now showing as false.

This is using the dev version

  • Hi, I am aware of this, but I haven't gotten round to fixing it yet :( sorry, I'll try getting it fixed asap – ᔕᖺᘎᕊ Oct 24 '17 at 20:16
  • @ᔕᖺᘎᕊ Look forward to the fixes when you have time. – Joe W Oct 24 '17 at 20:18
  • I know it's been a long time, but if you're still interested in using this script, I've fixed it for chrome in the latest version and am working on a FF fix too! – ᔕᖺᘎᕊ Feb 25 at 17:02
  • 1
    @ᔕᖺᘎᕊ Thanks for the update, just installed your latest version and looking forward to using it again. – Joe W Feb 25 at 17:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .