I've found a bug with the Stack Exchange image uploader, that occurs when attempting to use a custom URL to link to an image.

Let's take this lovely image as an example; if I try to use the custom URL the first time, I get this error:

enter image description here

However, if I close the image custom URL error message & try again with the custom URL, it works fine:

enter image description here

Related chat messages from when I first noticed the bug.

I have found this bug exists on both Meta & the main Stack Overflow site. I am using Chrome 45.0.2454.101 m, on Windows 8.1 Professional.

  • 1
    Does this happen all the time or just intermittently? Are you using any userscripts or extensions that may interfere with things? It works for me first time, consistently. (I'm using Chrome 45.0.2454.101 too, albeit on OS X.) Oct 5, 2015 at 14:30
  • @ChrisJester-Young It happens 100% of the time. Yes, I'm using a userscript (the SOCVR cv-pls userscript) & Adblock Plus. I'll do some testing and get back to you.
    – AStopher
    Oct 5, 2015 at 14:38
  • Confirmed, it's a problem with the StackImgurByLink Tampermonkey userscript. Reporting the bug to the developer now.
    – AStopher
    Oct 5, 2015 at 14:41
  • 1
    – Siguza
    Oct 5, 2015 at 15:02

2 Answers 2


(This was caused by a userscript of mine, which I developed in response to this MSO question.)


I changed it to simply call .click() on the link instead of hiding the div and making the other one visible, because that's what humans do too, so it has to work.
I'm not sure what was causing the bug (and I didn't care to investigate, since I found a fix), but I assume there are some event handlers listening on that link, which my script previously bypassed.

  • Yep, all the clickable elements in the image uploader change a whole bunch of state, so it's indeed important to trigger the click event for them. :-) Oct 5, 2015 at 15:58

Turns out that it's a bug caused by the StackImgurByLink Tampermonkey plugin- I forgot that I had it installed!

Reported the bug to Siguza and hopefully will be fixed.

You must log in to answer this question.

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