I can see how the following Quirks Mode question could be construed as "not about CSS."
But perhaps it is because CSS is unpredictable and semi-worthless when browsers get tripped into Quirks Mode. I've been getting a lot of legacy work recently where website owners bring me ancient table layout Dreamweaver sites they want updated--so they appear well on phones as well as on monitors. I'm finding those sites are often riddled with HTML errors, which are usually easy enough to fix. One persistent error is a lack of alt="xxx" tags inside images, and also lots of mis-matches between DOCTYPE and coding style--often with no closing </p> elements for paragraphs and ongoing coding salad that mixes <br> with <br/> and <img> elements that sometimes self-close and sometimes do not, all in the same file. How does one know when a browser is or is not in Quirks Mode? Sometimes it's obvious. Sometimes it is not. -- /* Colin (Sandy) Pittendrigh >--oO0> */ ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
