Re: [css3] [css21] browser specific CSS

On 1/04/2011 2:20 PM, Glenn Linderman wrote:
> On 3/31/2011 4:24 PM, Tab Atkins Jr. wrote:
>> On Fri, Mar 25, 2011 at 2:50 AM, Glenn Linderman<v+html@g.nevcal.com>
>> wrote:
>
>> Browser-specific hacks are a strong anti-pattern that we shouldn't
>> propagate, or even worse, officially bless in CSS. This does mean
>> that us web authors have a somewhat more difficult job, either
>> designing good CSS that still works in the presence of bugs, or making
>> our code ugly with hacks on occasion, but I think that's an acceptable
>> cost.
>
> I understand about the anti-pattern... but that is clearly a purist
> point of view, with little practicality. Forcing sites to use JavaScript
> just to detect which buggy browser one is dealing with is a significant
> negative, particularly when users turn Javascript off, and not all web
> hosts support CGI scripting (or limit it to particular scripts they
> install).
>
> Forcing sites to resort to ugly hacks that depend on other bugs in the
> same browser, that don't affect other browsers, and which often lead to
> non-validating CSS is not a good design either... and I don't consider
> it an acceptable cost, for two reasons:
>
> 1) Not all browsers can be easily differentiated with the various known
> hacks. Searching for and/or inventing such hacks may bring a feeling of
> accomplishment, but are largely a waste of programming resources. Some
> of the hack sites I've visited point out that certain browsers cannot be
> easily differentiated, but do have variant CSS implementations.


I strongly disagree with the use of any browser hacks. From all my 
experience with coding CSS and HTML, any browser bugs relating to CSS 
implementation that do occur can not be fixed with hacks. The only fix 
is the rearrange the HTML or try simpler CSS styling.



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

Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo

Received on Friday, 1 April 2011 05:54:28 UTC