When I click "Start a Bounty" I get the dialog asking me to choose how many points to offer, but when I click Next nothing happens (the dialog stays, no points are subtracted, no bounty is added). Clicking X or pressing ESC will clear the dialog, clicking cancel jumps to the top of the page but the popup is still on the screen.

Tested on several SE sites, on both questions posted by me, and questions posted by others.

This is on the latest version of IE, 11.1358.10586.0 on Windows 10. Tested on two machines (a desktop and a MS Surface).

Both are in the same corporate network, so I suppose that could be a factor, although I can't imagine that firewall settings would prohibit that one specific action, while I can do everything else on SE sites.

EDIT: Still broken. Proof? Had to use Chrome to add a bounty to this question.

  • Confirmed as well. Click Cancel doesn't do anything for me. Esc and close do work.
    – rene
    Commented Feb 7, 2018 at 16:12
  • @rene You're right, cancel doesn't work either. Edited.
    – BradC
    Commented Feb 7, 2018 at 16:15
  • 1
    For some reason $(function(){}); doesn't work anymore in IE11 if the javascript gets loaded in the DOM way after the DOM was ready. If I change it to setTimeout(function(){},10); I can proceed to the next page and cancel works as well. But that is more like a hack then a proper fix. I can't find what the root cause is of this and/or when it changed.
    – rene
    Commented Feb 7, 2018 at 17:40
  • 2
    Hidden Feature...
    – Chad
    Commented Feb 7, 2018 at 18:01
  • 1
    @rene root cause is IE being IE... borked and weird. ;) Commented Feb 8, 2018 at 8:15
  • @ShadowWizard Once I filed a bug for something in a different application; a developer of that commented that "to be fair, there's no standard for this, it's just that IE doesn't do what most of the other browsers do". Commented Feb 9, 2018 at 9:13

1 Answer 1


This will be fixed in the next build.

A previously executed $(function () { ... }) contained a check if (CSS.supports) before calling CSS.supports directly, but didn't account for the fact that if CSS.supports is undefined, CSS will also be undefined.

Because this JavaScript error happened inside a ready event callback it broke the $(function () { ... }) that wires events in the popup.

  • Thanks!! Any idea when that build will be available to test?
    – BradC
    Commented Feb 13, 2018 at 19:49
  • Not sure. It's noon on the west coast, so another meta build will probably go out today, but definitely by tomorrow. Commented Feb 13, 2018 at 19:52
  • Ok, still within my bounty window, then. I'll test it before awarding :)
    – BradC
    Commented Feb 13, 2018 at 19:53
  • One more question: is that fix going out cross-network? I had the original problem on skeptics.SE.
    – BradC
    Commented Feb 13, 2018 at 19:55
  • The fix is live on Meta now and will be on the rest of the network in the next few minutes. There's usually not a big gap between Meta going live and the rest of the network. If there is, it's because a dev needs validate something in prod and Meta is a more forgiving test subject. Commented Feb 13, 2018 at 20:25
  • Fix confirmed, and bounty awarded! Thanks!
    – BradC
    Commented Feb 13, 2018 at 20:44
  • When did you start using CSS.supports? Commented Feb 13, 2018 at 22:44
  • @ShadowWizard 11 days ago. It looks like it's related to some responsive design work around comments. Commented Feb 13, 2018 at 23:40
  • So... comments killed bounties and tag popups. Nice. ;) Commented Feb 13, 2018 at 23:58

You must log in to answer this question.

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