Microsoft in its infinite wisdom decided that you as a developer should be able to check development using an older version of their rendering engine. Developer rejoiced in this idea and figured that it would make things awesome from this day forth for the worlds most widely used browser. Compatibility Mode was born, but the issue is that it doesn’t actually work as promised *sadface*.
I can’t even count how many times I’ve designed something and heard a client respond say “Hmm, this doesn’t look right. Somehow all of the boxes are jacked up*”.
My default response:
I see what’s happening here, it looks like you’ve somehow enabled Compatibility Mode in your browser and that often switches the rendering engine to a simulation of a previous version. The issue with that is that the simulation isn’t quite as accurate as the correct version that it’s trying to emulate, in fact it’s worlds apart.
So what types of things can we do about this? Not much, in fact we cannot even code around it efficiently enough. Using Meta, or trying to detect via client-side scripting all seem to fail. I’d love to be able to detect and force compliance however it just cannot be done.
How do you handle the Compatibility Mode bugs, and more importantly how should we proceed moving forward?
*FYI, I know it may be silly but given my name is Jack, I’ve never quite liked something being messed up being referred to as “jacked up” it makes it sound like I’m the issue with everything in the world summed up in one phrase. But I do kid about it nonetheless.