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

Re: Prefix SVG properties in CSS?

From: Chris Lilley <chris@w3.org>
Date: Tue, 31 Jan 2012 18:06:26 +0100
Message-ID: <1735600773.20120131180626@w3.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Simon Sapin <simon.sapin@kozea.fr>, "www-style@w3.org list" <www-style@w3.org>
On Tuesday, January 31, 2012, 5:49:52 PM, Tab wrote:

TAJ> On Tue, Jan 31, 2012 at 3:19 AM, Simon Sapin <simon.sapin@kozea.fr> wrote:
>> Hi,

>> I just added the image-rendering property from SVG in WeasyPrint, a CSS
>> engine. I made it apply to image replaced elements and background images.

>> SVG 1.1 is a W3C Recommendation, but the property is not in any CSS spec
>> (AFAIK) so I prefixed it. However, this case is not covered in
>> http://wiki.csswg.org/spec/vendor-prefixes

>> As an implementer, should I use a prefix in such a case?

TAJ> It being present in SVG 1.1 is sufficient to allow you to not use a prefix.

I see that the wiki gives the exact opposite advice to what you and I replied:

"If you are implementing a feature which is defined in a mature W3C specification (CR, PR, REC), but not in CSS, your implementation: 

* SHOULD NOT support an unprefixed version of the feature"

Since the advice on the wiki is
a) wrong
b) not what the major existing implementations do

then the wiki clearly needs to be updated. i see two ways forward:

a) Define 'in CSS' to include CSS properties defined in other specifications. Then the 'not in CSS' does not apply

b) Split the advice into "implementing a CSS property" and "implementing a feature which is not a CSS property", ad make them say different things.

Thoughts?

-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups
Received on Tuesday, 31 January 2012 17:06:30 GMT

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