- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 20 Feb 2003 10:28:53 -0800 (PST)
- To: Christian Roth <roth@visualclick.de>
- Cc: www-style Mailing List <www-style@w3.org>
On Thu, 20 Feb 2003, Christian Roth wrote:
>
> I'm sorry to bring this issue up again. I'm developing on a conversion
> product using CSS syntax and semantics for the style language that
> requires proprietary property identifier names.
>
> [...]
>
> What route is the recommended way to go? We'd rather not need to change
> the prefix once the product is released.
As I understand it, the current thinking in the working group is as
follows:
If you have full control over your parser, then proprietary properties
should be indicated by using the format
-vendor-identifier
This ensures that the identifier will be ignored by compliant UAs and
will never clash with official CSS properties.
If you don't have control over the tokeniser part of your parser,
replace the initial hyphen with an underscore, as in:
_vendor-identifier
The Working Group guarentees that it will not start any official
identifier with an underscore, ever.
Most extensions I am aware of use the first form, e.g.:
white-space: -opera-pre-wrap;
white-space: -moz-pre-wrap;
I am aware of several extensions, including -hp-foo, -konq-foo, etc.
Historically, there are also a few other forms:
-pre-wrap (no vendor prefix, used in older versions of Opera)
mso-foo (no leading hyphen, used for some Microsoft Office extensions)
HTH,
--
Ian Hickson )\._.,--....,'``. fL
"meow" /, _.. \ _\ ;`._ ,.
http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 20 February 2003 13:28:40 UTC