Eric: Well, I am just thinking theoretically, but the standards refrain is, everyone should meet the standards. And so css says, the code 'corners: rounded' or 'corners: spiked' is valid. But then the browsers fail to comply. They need it to be, 'mozilla-corners: rounded', and then there are 8 varieations.
And I wonder, why does the language not have the ability to internalize that, or can the language itself negotiate a successful result, given this imperfect reality. Pre-processors may well have other value, but is this negotiation a function that should be done by them? We already have a lack of standardization, so I personally am not thrilled with this extra layer of complication on an already difficult process, but given the potential I would assume they are here to stay. Rgrds, Andrew Andrew, I'm not following what you mean by this - "Why can't there be a code for all browsers, to do something like transparency or rounded corners." Are you talking about something outside of CSS? Something else maybe? Eric ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
