W3C home > Mailing lists > Public > www-style@w3.org > May 2012

[css-wywiwyg] browser interpretation of css

From: Rik Schaaf <coolcat_the_best@hotmail.com>
Date: Fri, 4 May 2012 01:02:55 +0200
Message-ID: <BAY0-P2-EAS1160B18DF134E7BCE1FE106CF2F0@phx.gbl>
To: "www-style@w3.org" <www-style@w3.org>
How can we make sure that a piece of css code is interpreted the same way in every browser without additional code? 

Even this question is wrong, because style and layout shouldn't be a matter of interpretation or recommendation, but of rules and protocols. What you write is what you get. How can it be that my webpage looks different in several browsers? This difference should be eliminated.

Is there an explanation why css uses only recommendations and not strict protocols? If it is about browser specific css which wouldn't be possible, then I don't agree: a part of the protocol could be prefix or suffix extentions. A browser pre-/suffix would be registered and documented. (a bit like the moz or webkit prefixes, but for a different purpose)

One of the problems is that css is embedded deeply into the browser software, so changes to css recommendation are dependent on browser updates. Separation of the browser and the software that processes the css could be a solution. The browser should only be the frame around the content. The content itself should be processed by a company indipendent standard, the web standard.
Received on Thursday, 3 May 2012 23:03:27 GMT

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