I would say code for standards at the end of the day, because standard is really the minimum requirement, once that's ticked off then code/hack for other browsers. Can't say I've read it anywhere but my web sites certainly look, work and load a lot better since I've started following that process.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David McKinnon Sent: 01 September 2008 11:55 To: wsg@webstandardsgroup.org Subject: [WSG] Code for Firefox, hack for IE Hi, For a while now, I've been operating on the principle "Code for Firefox, hack for IE". That is, writing CSS for the most standards-compliant browser, and then making adjustments for non-standard behaviour. I said this in a meeting last week to argue a point and my boss said "who says?". I could have said "me", but maybe that's not a good enough answer. Somewhere some years ago I read this, or heard someone at a conference or something and it got stuck in my head. Is this the way anyone works? Is it the best way to work? Does anyone know where I got this idea from? Book? Blog? A bit of googling this afternoon turned up not very much. Thanks, David ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* -- No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.6.14/1644 - Release Date: 31/08/2008 16:59 ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
