Quote from: deathsythe on September 13, 2012, 05:20:48 AM

Quote from: libertaad on September 12, 2012, 06:51:43 PM

Quote from: deathsythe on September 12, 2012, 01:23:10 AM

I've noticed a lot of times on roulette I have to click several times before it registers my click. It happens a lot when the bet/double button lines up over another number or between two numbers. I need to move my mouse a little bit and click again, even though I was already on the button. /shrug/

That sounds bad! I am not able to replicate this issue though. Could you help me out and elaborate a little more? Which buttons require clicking multiple times - the big buttons at the bottom of the table (eg, "Spin", "Repeat Last", etc.), or is it the roulette board itself that sometimes requires multiple clicks. Also, what browser are you using? Finally, if possible, could you post a screenshot of: "It happens a lot when the bet/double button lines up over another number or between two numbers". I'm not sure exactly what you mean here, and a screenshot would help a lot. Thanks!

Also, what's your username on bitZino? I'll comp you as well for helping me out Cheesy

Same as here, and as reddit. Tongue

Thanks bud.

(imgur is giving me crap right now for some reason...)

So sometimes when I am doubling my bet on the x2 button and I click outside the red box it doesn't take for some reason.

I've actually never really used the big buttons on the bottom except for spin.

Also - you see how the top part of the "x2" button lines up with the 16. If I am doubling my bet sometimes it will select 16 (or 10 if I'm betting red)

Thanks for the feedback! That definitely explained it very well. Comp sent

This is a very strange bug, because that button is actually just a single element, so the border shouldn't have a different behavior than the inside. Also, the interaction with the elements behind it are bizarre and unexpected. I can't seem to replicate the issue on either Firefox or Chrome, so I can't figure out what would be causing it. We will definitely keep an eye out for this bug though, and fix it if we can.

Thanks again for the feedback!