This really has nothing to do with testing in other browsers... well I guess it could, but it is really an aspect of the content. There was a post on the home page that put an image into the page in a strange way, which messed up the page. We test our pages in Safari, Firefox and IE ... and usually Opera as well. Chrome tends to render like Safari (for obvious reasons) so we haven't really bothered with it. I've said this over and over again, but this keeps coming up... we tend to develop in Firefox 3.x ... and then we test in IE/Safari ... so this repeated suggestion that we only test in IE has no basis in fact. Maybe you think we have to 'go live' whenever someone makes a post, but that isn't the case. No code was pushed out when this blog post was made.
It is pretty hard to imagine a programmatic way to build a website such that you could put absolutely any markup into a post and have it render right in all browsers. One way would be to severely restrict the markup that people can use, to not allow anyone to put images into their posts, etc... and we do some of that (one of the many things people complain about when we do this in the forums)... but we do allow some flexibility and count on our contributors to check that their content looks good before pushing it live. On a site like CNN or someplace similar, they would likely solve this by having all posts be text only with form fields to supply a small set of images for the article or perhaps dynamically putting images in and not allowing the author any choice in the matter. That isn't the direction we've taken for our content.
That particular issue could be fixed if we applied a max-height/max-width on images inside posts on the home page ... but it had never come up before so we had not done that yet ... we will though. Every time a piece of content, in the forums or elsewhere, finds a way to break the layout of the site, we'll try to prevent that in the future, either through CSS restrictions or html filtering of what you are allowed to enter.