[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

OT - CSS - thoughts on non-compliant browsers

• Subject: OT - CSS - thoughts on non-compliant browsers
• From: Robert Koberg <rob@k...>
• Date: Sun, 07 Mar 2004 15:23:02 -0800
• Cc: xml-dev@l...
• In-reply-to: <404B88D0.4010500@s...>
• Organization: liveSTORYBOARD
• References: <200403071358418.SM05492@evanslt> <404B7BF3.7030606@s...> <p06010206bc713470aebe@[192.168.254.4]> <404B88D0.4010500@s...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Hi,

I realize this isn't the place to discuss CSS implementations, but I was 
wondering about your thoughts on browsers that decide to go their own 
way with regard to the spec. Actually, I would like some force to be 
applied to the developers...

The browser in question is mozilla! They have decided that font pixel 
sizing is wrong (in most cases I agree), so they take over the user's 
CSS and provide their own interpretation.

Now, I am not one to prescribe behavior for anyone. But I was wondering 
if there is offense taken by others by this non standard approach. Is 
anyone from mozilla here to explain there decision to abandon standards?

Perhaps mozilla should be denigrated in favor of other choices... at 
least for people who believe in standards.

The reason i bring this up is because we have built a beautiful, 
standards compliant, 3 column, tableless layout which works in all 
browsers. The problem occurs when a user resizes the text up in mozilla. 
We have defined tab's text to be pixel based because we needed to use a 
background image for the tabs (using a background-color and sliding 
image broke all over the place). So we made the decision to go pixel 
based for this one thing (the text is large to begin with). The layout 
looks great in all browsers except mozilla when text is increased.

For our project we are going to provide the user with information of how 
mozilla is screwed up and leave it as is -- as it works everywhere else 
(5th gen and up).

best,
-Rob

• Follow-Ups:
  • Re: OT - CSS - thoughts on non-compliant browsers
    • From: Robert Koberg <rob@k...>
  • Re: OT - CSS - thoughts on non-compliant browsers
    • From: "Thomas B. Passin" <tpassin@c...>

• References:
  • RE: SAX/Java Proposed Changes
    • From: "Kirk Allen Evans" <kaevans@x...>
  • Re: SAX/Java Proposed Changes
    • From: Dennis Sosnoski <dms@s...>
  • Re: SAX/Java Proposed Changes
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: SAX/Java Proposed Changes
    • From: Dennis Sosnoski <dms@s...>

• Prev by Date: RE: W3C suckered by Microsoft?
• Next by Date: Re: CAP (Common Alerting Protocol) needs review
• Previous by thread: Re: SAX/Java Proposed Changes
• Next by thread: Re: OT - CSS - thoughts on non-compliant browsers
• Index(es):
  • Date
  • Thread