Bug overview description.
Modes stop working randomly, and open the clicked post instead of performing the selected action.

What part(s) of the site page(s) are affected?
https://e621.net/post/index

What is the expected behavior?
Uh, the modes work.

What actual behavior is given instead?
See the overview. Happens with all modes that I've tried, including scripting and locking ratings.

Time of incident (if applicable).
Today, 06/08/2016. From what I've heard, happened yesterday too.

Can you reproduce the bug every time?
Yep.

What steps did you take to replicate this bug?
Always happens after a few posts if I click the thumbs at my normal speed. Doesn't seem to happen if I slow down the clicks to snail-pace, though that pretty much makes tag scripting useless.

Errors or other messages returned (if any).
Not applicable.

Have you experienced this bug before 2016-08-02 as well?

Are you using eSixExtend? If so, does disabling it affect the reliability of the modes?

KiraNoot said:
Have you experienced this bug before 2016-08-02 as well?

No. Just noticed it myself for the first time. I haven't done scripting for a few days, it might've started with the update. Was definitely working fine last week, except for the random 522 errors.

...Hudson said it's affecting him too.

Are you using eSixExtend?

No, and my own script doesn't run on that page.

Reason I ask is because there were no changes to the JavaScript anywhere but blacklist and comment voting. So I find myself puzzled that it would start with the update.

Might've started yesterday, not with the update.
Hard to say. I think I did some scripting right after the update. And if it were an issue back then, I would've noticed. But I'm not sure when it was, can't check because the rating locks aren't recorded in the tag history.

Does it always happen to the same posts? And if you know how to bring up a Javascript console (Ctrl+Shift+I, click Console tab usually), see if it generates an error when it happens.

TonyLemur said:
Does it always happen to the same posts?

I don't think so. I can keep hammering the same set of posts with 'lock rating', and it seems to trigger on random ones...

Oh! Just figured it out. It mostly happens on narrow thumbnails.

If I miss the click and hit slightly outside of the thumbnail (on either side), it opens the post instead of applying whichever mode is selected.

All posts seem to have a clickable border now. It's just far easier to accidentally hit on narrow ones. That also explains why it didn't happen when I was clicking slower..

The clickable borders has been happening for a while now, definitely before the update a few days ago. They're really annoying because it's difficult to find "empty space" between posts that you can click on without navigating to a new page. Sounds like the latest update changed how they worked in relation to modes though, if you only started experiencing it recently.

Edit: There doesn't seem to be any more clickable borders for me anymore.

It also used to be possible to tag script with keyboard, with Tab + Enter combo. Enter used to apply whichever mode is selected to the highlighted post, but now that too simply opens the post.

TonyLemur said:
Edit: There doesn't seem to be any more clickable borders for me anymore.

I'm still getting those. On Chrome, at least.
Screenshot: http://i.imgur.com/KGK8mrC.png

The area that I can click on (and that breaks the modes) matches the highlighted area.

Can confirm "padding” on A-element on narrow thumbs; PostModeMenu.click() should either be moved from the IMG to the A, or A should be inline-blocked (or something along those lines).

So, um, any news about this? I'd like to get back to my scripting projects, they're starting to pile up.

Bug confirmed. Assigned internal bug ID #658. Fix created, pending deploy.

Fixed as part of deploy 1.1.2.