- From: Brian Manthos <brianman@microsoft.com>
- Date: Fri, 1 Apr 2011 09:04:12 +0000
- To: Glenn Linderman <v+html@g.nevcal.com>
- CC: Tab Atkins Jr. <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>, Alan Gresley <alan@css-class.com>
Alan hits on a good point here. IMO, one of the weakest points in the interoperability story right now is the lack of tests. 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. 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". -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. -- Alan http://css-class.com/
Received on Friday, 1 April 2011 09:04:53 UTC