I think I’ve ranted (mildly) about this before.
I hate web browsers - different ones will render markup differently, requiring hacks to get around the borked behaviour. However, that has nothing on what Firefox just did to me for about an hour. Load a page in my development environment. Everything looks right. Click on one of the links that performs an action, sets a message in the session, and hands back to the code to render the message and update the page. That works. Click refresh - the message should go away (and the exact same code on other pages has always worked). The message doesn’t go away.
Check the contents of the session - the message area is emptied, which is correct, so there’s no content to be displayed. Hold down Shift and click reload. Message is still there. Check the server side cache of the template - the message isn’t there. View source, the message is there. The only thing that’s changed since I was last testing this code was a Firefox update.
Set Firefox’s cache to 0, and the problem goes away.
I hate web browsers.
I can top that for browser-hate: different browsers on the same system loading the same IMAGE differently. Not talking about where it puts the image on the screen, but the image itself is affected by which browser it’s in. I recently revamped my blog, and redid the image… the image is a slightly different hue and gamma depending on whether I’m viewing it in Safari, Camino (Gecko 1.8+), and Opera. Haven’t been able to entirely track down why, but I think it has something to do with whether or not the rendering engine supports embedded profiles in the jpg. *twitch*
Comment by Nabil — March 1, 2007 @ 19:03
Yep, that’s to do with Safari supporting ICC profiles, and the rest not.
Comment by cricalix — March 1, 2007 @ 19:15