Quote from: ChloeST on July 17, 2011, 04:18:55 PM

Thanks for the BTC, but the kind of problem that I was describing is a kind of attack on users running firefox and chrome browsers: I can make them not have buttons in a first-to-act situation every time.

In other words, I'm running an opera browser, and "stealing" the small blind of a user who is waiting at a table is very easy. The browser featured on screen in the video is firefox, I make the firefox browser have no buttons by running opera on a separate computer.

I'm sure I can make the first person to act in a full ring game that is already running not have buttons just by sitting down with an opera browser.

Have you actually successfully stolen a blind with this? You claim it's "easy", but you don't demonstrate it.

I couldn't repro this bug at all, myself, let alone steal a blind.

I looked at your screencast. At no time is action on you with no buttons showing. There is a bug here - Opera's not responding properly to the blind request - but once the player times out, the game proceeds as normal. During the time you have no buttons, the action is actually on the other player. That's why the timeout bar is on their name and not yours.

The server has asked that player "Do you want to post a blind?" and the client is meant to automatically respond to that request. It's not, for whatever reason - but that doesn't affect anyone but that client. When you refresh the FF client, nothing happens, because the action isn't on you in the first place. We're waiting for the other player. When you refresh Opera, it "fixes" it because for some reason refreshing makes Opera respond to the blind request properly.

I tried hacking a client to not respond to the blind request, and when it times out, the SB is returned to the player.

That said - thanks for submitting such a detailed bug report. If it weren't for the screencast I wouldn't have any clue what was happening at all.