We’re often asked why cross-browser checking and fixing can be such a time consuming minefield when developing newly designed sites.
One way of thinking about it is a Londoner speaking to a Glaswegian: they speak the same language, but not the same dialect, so what’s said may not ‘translate’ fully.
Effectively we face the same challenge with a website: it is written in a universally understood language (HTML), but in order to ensure that the website is ‘understood’ in different Internet browsers, we need to tailor the underlying code in quite detailed ways to support the individual (and sometimes idiosyncratic) dialects of those browsers.
Furthermore, there are potential challenges in translating the website for a browser from an older generation. Imagine how successfully you could communicate with Shakespeare or Chaucer, without adopting some of their respective dialects. Not easy.