Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Clicking "Unwoot" doesn't actually remove your woot from the post.
Offline
Clicking "Unwoot" doesn't actually remove your woot from the post.
Reload page
Offline
Clicking "Unwoot" doesn't actually remove your woot from the post.
Are you using chrome because this seems like a chrome-y kind of bug but idk it might not be chrome it'd be a first but it's definitely possible for this problem to not be caused by chrome.
I need browser, browser version, OS, and whether or not your browser is chrome. I've been unable to reproduce the bug on the few browsers that I've tried.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
I cannot reproduce this issue with the lastest chrome stable build.
I have never thought of programming for reputation and honor. What I have in my heart must come out. That is the reason why I code.
Offline
~MeleeTonikZ wrote:Clicking "Unwoot" doesn't actually remove your woot from the post.
Are you using chrome because this seems like a chrome-y kind of bug but idk it might not be chrome it'd be a first but it's definitely possible for this problem to not be caused by chrome.
I need browser, browser version, OS, and whether or not your browser is chrome. I've been unable to reproduce the bug on the few browsers that I've tried.
I'm using Mozilla firefox 43.0.2, running on windows 7.
Offline
tfw not chrome. Well, 43.0.1 on linux isn't giving me any issues, and I can't reboot into windows at the moment, but when I do I'll install that version of firefox and investigate. Since 43.0.3 is out you might want to try that instead and see if it fixes the issue. Or try downgrading to 43.0.1. Or clearing cache/cookies.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Offline
I was just able to get two Woots on a post. This might have been because I just changed my username.
Nope, unrelated. The woot mod stores your user id along with your username. If you go and look now you will only see W24.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Offline
^Unrelated, but an issue?
Also, I was under the impression that the only stored data was usernames... good fortune, what with all these username changes.edit:
well, as lucky == woots are important...
Can confirm: IDs are stored.
An issue, but not a different issue. Same one as everyone else in this topic, probably, but I have no idea what their problem is. The jquery says to delete the old element when you click the unwoot button. I don't see how that could possibly be misunderstood by a browser.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
I remember we had this problem before. If people got too quick with the button, it would try to delete the old element (if it was there) ... wait a delay ... and then add it. So, if I clicked multiple times in the delay, it would see there was no old element, 5 times, and then add me five times. But it appears we fixed that.
edit: it's not a speed issue. Autoclicker makes 20 of me show up... but then all 20 take their proper course and leave.
Offline
Yay I'm famous D:
( ͡° ͜ʖ ͡°)
Offline
Pages: 1
[ Started around 1732684373.5996 - Generated in 0.128 seconds, 10 queries executed - Memory usage: 1.59 MiB (Peak: 1.78 MiB) ]