Try checking these things:

1. Clear any custom CSS you have
2. Disable AdBlock (well I guess you already tried this one..)
3. Disable any User Scripts you may be using (like via the Tampermonkey)
4. Check your browser extensions, some of them may be interfering with the webpage.

If you rule out all of these, please do the following:

1. Go to the page where you have the unresponsive button, and hit Ctrl+Shift+J to bring up the javascript console
2. If you see any errors or output in this console, take a screenshot for us
3. With the console still open, click the button, and see if any new errors show up in the console when you do the click.

Let me know.

If you're not sure, then you're probably not using any. They are usually done through a browser extension called Tampermonkey, so if you don't have that then you're fine.

And well, opening the JS console shouldn't affect the way the page behaves. Have you confirmed that the button is still unclickable when the console is closed, like right now?

Three more questions:

1- What is your screen resolution? 2- Could you try it again, but this time, "pop out" the console and see if the button continues to work.

To pop out the console, click the vertical dots icon on the top right corner:

The left-most option for Dock Side (the one with two rectangles) will make it pop out into its own window.

3- Can you also try simply making your browser window smaller (without the console open) and see if it's still unclickable? Like making it half-screen size for instance.

Thanks. One more question for both you and when they see this. When you hover over the button, does your cursor change to the little hand icon (like it's supposed to do for links) or does absolutely nothing happen at all?

Could you two please try updating your browser? This seems like it was a browser issue and may have been fixed in the latest version of Chrome. The new version is 64 and I notice you're both on version 63 so hopefully an update will fix it.

Awesome, I'm glad that's all it was. What a strange error. I'll lock this up as resolved :)