You don't *need* to do it, but it's an unexpected behavior--I always approach software testing by wanting to know every way you can break software, and then determine what priority I need to assign to fixing it. Trust me, I know clicking multiple times on a link is irrational for anyone who is familiar with general computer use, but there are people out there who double click on internet links, and thus would break the page anytime they wanted to view a user profile. I don't know about you, but if I wanted to sell an application, I wouldn't want it to be this easy for novice computer users to hose a forum page just by double-clicking on something.
I see what you're getting at, but it reminds me a lot of buying an iPod, submerging it in water, and then asking Apple to waterproof it.
You know what sucks is that I see there are horizontal rules in old post quotes. Yet another thing I'll need to clean out. I'm thinking it's going to take around an hour to totally migrate all of the data when it comes time.
Eh, I would have loved to have been more specific, but I was in a hurry and I was more interested in confirming the claim of the other poster who said there was a problem.
If you would like me to be more specific, I will be: When I would click the profile and click again before it had fully loaded, it would immediately stop. It would load the data, but that data would be cut off due to the fact that the box is not completely open.
I think your analogy is completely inaccurate. In my opinion, it is a bug--no doubt! I often click on things accidentally on a page: It is absolutely feasible that someone would click on the profile by mistake and immediately click it again in order to close it.
As well, if you do get the script to "lock up" and attempt to look at any other profile, you cannot get those to close.
If you do not consider it a bug, fine. Don't fix it.
I'm only kidding! I really have dropped that for now at least.. I'm looking into some ASP forums, because it's not just coasterbuzz that you can't click any buttons. I've experienced the same thing on a couple other sites, and every time I bring them up on a "real" computer, I see the SAME implementation. Even on ASP.NET in the forums you can't click 'search' on pocket IE. Further, I've tried it on several other mobile devices at work, and in some smartphone support forums even non-T-Mobile subscribers have tried it with the same results. Apparently, anything that uses the most recent version of asp.net has that bug w/ Pocket IE. Also, FYI, Jeff, through those support forums I have found that it does, indeed, work with Opera. So, as long as I can get it stable, I *might* actually install it as an alternative.