Re: CSS Properties defined by other specs

Dirk Schulze:
> I just submitted the first batch of changes to the coordinate and
> units section and have some questions.
>
> At the moment there is a section about "The 'transform' property". I
> want to come back to a thread of Cameron. Cameron asked if we add a
> note with a link the the definition of a property, if it is defined
> by a CSS spec. This is the case for the 'transform' property [1].
> Should I still add the complete table with description of name,
> values, computed values, initial value and so on? At the moment I
> just have the name, and the information that it is animatable. Is
> that enough? If not, how do we handle the case that a property
> definition changes on the CSS side?
>
> What is with the properties 'transform-origin', 'perspective',
> 'perspective-origin', 'back face-visibility' and 'transform-style'.
> Do they need to be mentioned in SVG 2.0?

I think all the properties defined in other specs that SVG depends on, 
like those above, should be mentioned in the SVG spec still.  What I've 
done for example for the display and visibility property definitions is 
to replace them with this section:

   https://svgwg.org/svg2-draft/painting.html#VisibilityControl

So I renamed the section to say "the effect of the blah properties" in 
contrast to sections that actually define properties which say "the blah 
properties".  I've dropped the property definition tables.  In SVG all 
properties are animatable, so probably that line should just be dropped 
from the property definition tables anyway.

There will be a section (I haven't added it yet) that lists all 
properties that we "import" from other specs too.  But I think it is 
also good to mention them in the main body of the SVG spec like I've 
done for display/visibility.

Received on Thursday, 7 June 2012 00:01:38 UTC