W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: [css3] [css21] browser specific CSS

From: Glenn Linderman <v+html@g.nevcal.com>
Date: Fri, 01 Apr 2011 02:58:17 -0700
Message-ID: <4D95A1B9.1030707@g.nevcal.com>
To: Brian Manthos <brianman@microsoft.com>
CC: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>, Alan Gresley <alan@css-class.com>
On 4/1/2011 2:04 AM, Brian Manthos wrote:
> Alan hits on a good point here.  IMO, one of the weakest points in the interoperability story right now is the lack of tests.

You may be right that that is one of the weakest points.  Easier to tell 
that from your perspective than mine, perhaps.

> If one or more browsers appear to be wrong, make a test case that captures the specific issue succinctly and submit it for consideration to the test suite.

How?  Where?

In general, I can only tell that the browsers differ in their behavior, 
not which one is wrong.  But still, that makes it appropriate for a test 
case, and the CSS enforcement police can decide which browsers are 
guilty, and of what.

> If it gets accepted, that re-enforces the case as a correct interpretation of the specification and puts pressure on vendors aiming for compliance to fix the issue.  If it gets rejected, you'll learn something in the "why".

Yes, I agree with all this.

But that doesn't reduce the number of buggy implementations in the 
field, that sites still have to deal with.  And so it doesn't directly 
and immediately help the site that discovers the problem.  For that, I 
need to deal with the variant behavior by coding variant CSS.  And it is 
hard to code variant CSS without resorting to hacks or Javascript... 
which is my whole issue.


> -Brian
>
> -----Original Message-----
>
> On 1/04/2011 5:38 PM, Glenn Linderman wrote:
>> For my personal web sites, I've chosen to mostly be bland, but that
>> doesn't appeal to customers. And even with blandness, I've discovered
>> enough differences in browsers, that I finally decided to code for
>> Firefox, use Javascript to detect which browser, and have a few tweaks
>> for (mostly) IE (and not just IE 6... some of the differences I've found
>> are still in IE9), but also Opera and Chrome. So if users of non-Firefox
>> browsers turn off Javascript, certain parts of my sites look terrible.
>> Firefox doesn't need Javascript at all to use my sites, but others do...
>> only so I can detect the browser and use different CSS rules.
> Do you have test cases? What you describe above does not reflect my
> views and my experience. What may be considered a CSS bug may be a
> browser attempting to follow two or more rules in the specs where part
> of the specs makes other parts of the specs break. Most of this was
> concerning interaction between floats and elements (inline-level and
> block-level) in normal flow.
>
Received on Friday, 1 April 2011 09:58:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:39 GMT