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

Re: [css3] [css21] browser specific CSS

From: Gérard Talbot <www-style@gtalbot.org>
Date: Fri, 1 Apr 2011 17:00:53 -0700
Message-ID: <9e9ab032fc8043bbc972d3d451154ba2.squirrel@cp3.shieldhost.com>
To: "Anton Prowse" <prowse@moonhenge.net>
Cc: "Public www-style mailing list" <www-style@w3.org>, "Glenn Linderman" <v+html@g.nevcal.com>

Le Ven 1 avril 2011 12:39, Anton Prowse a écrit :
> Hi Glenn,
> Most authors also tend to assume that when their page looks wrong in
> Browser X it's because Browser X is wrong.  Often, however, Browser X
> isn't wrong; instead Browser X is exercising free choice given to it via
> the CSS spec, either granted explicitly or more usually through making
> the rendering undefined when certain conditions are satisfied.  (Search
> for the string "define" in CSS21 to catch the instances of "is not
> defined", "does not define", "undefined" etc to see just how many there
> are!)


There is also the string "free to make a guess" (section 10) and "round"
and possibly the word "may".
There is also not defining keyword values. E.g. thin is not necessarly 1px
wide: it could be 2px, or 3px, etc. it is all up to the user agent to
choose such value.
Default, initial values are also up to user agents. The whole appendix D
is informative, not normative.

CSS 2.1 Test suite RC6, March 23rd 2011

Contributions to CSS 2.1 test suite

Web authors' contributions to CSS 2.1 test suite
Received on Saturday, 2 April 2011 00:01:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 12:34:50 UTC