W3C home > Mailing lists > Public > www-style@w3.org > August 2008

Re: @media and browsers conditional statments

From: Alan Gresley <alan@css-class.com>
Date: Tue, 12 Aug 2008 18:47:30 +1000
Message-ID: <48A14E22.6060604@css-class.com>
To: Brad Kemper <brkemper.comcast@gmail.com>
CC: Joshua Cranmer <Pidgeot18@verizon.net>, CSS 3 W3C Group <www-style@w3.org>

Brad Kemper wrote:
> 
> On Aug 10, 2008, at 10:28 PM, Alan Gresley wrote:
> 
>> The only hacks I use for Gecko, Opera or Safari are hacks to lock out 
>> other browsers. The only CSS bugs that I do see in Gecko, Opera or 
>> Safari are bugs that can not be hacked around. One test case.
> 
> Well congratulations. I am happy for you. I have found other differences 
> unique to Gecko that I've needed to hack around, and I've used selector 
> hacks to do so. Similarly, I've sometimes needed to give separate rules 
> to WebKit, such as when I used its "placeholder" attribute on a text 
> field, and wanted to simulate that in other browsers via a background 
> image.


So are you using these hacks for progressive enhancement or moving a box 
a pixel here and there? If this is for progressive enhancement then we 
may want to consider how this can be done.

By allowing media browser specific rules the onus of dealing with CSS 
bugs or possible use of progressive CSS becomes an issue which authors 
have to deal with and not implementors. Meaning instead of just that 
funky browser IE to contend with, we as authors also have to deal with 
Gecko, Safari and Opera as well.


-- 
Alan http://css-class.com/

Nearly all men can stand adversity, but if you want to test a man's 
character, give him power - Abraham Lincoln
Received on Tuesday, 12 August 2008 08:48:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:11 GMT