<p>EDIT: not sure of the etiquette but based on the comments I opened this on meta.stackoverflow.com as <a href="http://meta.stackexchange.com/questions/74544/ajaxy-control-buttons-on-user-profile-page-can-break">http://meta.stackexchange.com/questions/74544/ajaxy-control-buttons-on-user-profile-page-can-break</a></p> <p>-- </p> <p>In Chrome 8.0.552.224 on Windows 7, I found a bug in which I receive what looks to me like the raw, unformatted output of an ajax call vs having that output incorporated in the page correctly. I seem to be able to reproduce it at will in Chrome. I was going to say that Firefox 3.6.13 didn't have the same problem, but I banged on it some more and recreated it there too.</p> <p>Here's what my page looks like when I follow the steps below:</p> <p><img src="http://jetmore.org/john/misc/error.png"></p> <p>Here are the steps to reproduce in Chrome:</p> <ul> <li>Load serverfault.com</li> <li>click on my username at the top to load my profile</li> <li>scroll down to "Answers" section</li> <li>click on any of the "answers" page numbers to to go any page but #1 (so, click "2" or "next")</li> <li>click on any of the answers to load that question page in the same tab</li> <li>click the back button to return from the question page to the profile page</li> <li>scroll back down to the "answers" page numbers again</li> <li>click a different page number</li> <li>Boom, all the data that should be loaded in the answers section, but in a new page, not incorporated in the profile page.</li> </ul> <p>Steps to reproduce in firefox (this works in Chrome too and is actually a simpler way to reproduce, but I'm leaving the Chrome steps because it's how I found the problem organically which might be useful reference):</p> <ul> <li>load serverfault.com</li> <li>click my username to load profile page</li> <li>scroll to answers</li> <li>click one of the numbers to go to a different page of answers (2, for instance)</li> <li>F5 to reload the page</li> <li>scroll back down and click another answers page index number (2 again will work)</li> <li>And again, what appears to be the ajax response rather than the page w/ the response incorporated into it.</li> </ul>