- From: Michael Adams <linux_mike@paradise.net.nz>
- Date: Thu, 09 Oct 2008 08:39:31 +1300
- To: www-validator@w3.org
I am a little disappointed. Was hoping for more comments despite the percieved OT nature. On Mon, 06 Oct 2008 08:21:18 +0200 Came this utterance fomulated by Jens Meiert to my mailbox: > > > The more i work in CSS the more i notice that all browsers need > > hacks. > > That's a myth, fortunately, even though that myth's not uncommon. Bugs in other products have and do exist. http://www.andybudd.com/archives/2005/11/common_css_bugs_in_safari_firefox_and_opera/ is a little out of date but http://www.quirksmode.org/bugreports/index.html Dont forget how hard it is to make a large program error free. http://portal.acm.org/citation.cfm?id=948586 Typically i don't often have to write CSS around bugs in gecko, webkit or presto but on occasions they have not performed as expected without cludges. khtml is a different fish. [snip] > as well as their impact on performance due to additional HTTP > requests). http://forumdeli.com/2-how-to-serve-pre-compressed-css-js-and-other-web-content/ My idea was to enable workarounds if and when bugs do come up in the future on all modern browsers. This would also allow serving of SVG background images, for a current example, to browsers that support it and alternatives to those that do not. OK, i will ask this question again on a different list. -- Michael All shall be well, and all shall be well, and all manner of things shall be well - Julian of Norwich 1342 - 1416
Received on Wednesday, 8 October 2008 19:38:58 UTC