Thanks for finding this. I ran a couple simple tests and I don't believe I can fix this. In compatibility mode IE8 will not let you replace the mouse click handler for <button>'s with your own handler.
Compatibility mode describes itself as being for old websites that don't display properly, saying that turning on compatibility mode may fix this. But the website displays fine without compatibility mode, so I'm going to close this issue. Thanks again for the help, you and AZPaul3.
AZPaul3 just discovered that his IE8 wasn't working because he had compatibility mode set. Can you verify whether you have compatibility mode set? If it is set then please unset it and see if that helps.
If it is not set then could you perform the experiment I described to AZPaul3 in Message 382. Let me know what happens and we'll go from there.
I've never fiddled with anything having to do with compatibility mode. And most certainly not in the recent past. How do I even check that?
There's a little icon that looks like a broken page at the very top the the IE browser window. Click on that and it should tell you what mode you're in. If you're in compatibility mode then turn it off and see if things start working.
Assuming that didn't work, here's the next thing to check:
While viewing an EvC Forum page, right click and select "View Source".
On line 8 you'll see a link to dBoard.js. Cut-n-paste that into your browser's address window and hit return. Oh wait, IE only get's confused when you do this. You'll have to cut-n-paste it into the FF address window.
Poking around on the Internet I was able to find that compatibility mode changed rapidly between IE6 and IE8. It didn't exist in IE6, I think that IE7 made it available but not under user control, and IE8 places it in the browser window header and in the Tools menu as Compatibility View (checked if you're in Compatibility Mode) and Compatibility View Settings (which brings up a dialog window).
So while I'm not certain, let's assume that in IE7 Compatibility Mode is on all the time for you, which means it is behaving identically to IE6. I do have access to IE6 and will attempt to fix the problem later today.