[mpeg-OTspec] format of CSS Variables has changed

[Levantovsky, Vladimir]

Hi Chris,

Thank you for the comments. The examples of using custom properties as part of the UA style sheet were pulled from other parts of the spec just to make is concise for the purpose of quick email confirmation, in the actual text of the standard each of those lines is presented and explained separately so I am reasonably certain that it is clear when and why one may want to use them as additional lines in a user agent style sheet. 
And I am not sure what happened to my /* comment line */ - the original email had it all in one line but somehow one of the email clients managed to break it into two different lines.

Thank you,
Vlad



-----Original Message-----
From: Chris Lilley [mailto:chris at w3.org] 
Sent: Tuesday, March 25, 2014 4:45 AM
To: Levantovsky, Vladimir
Cc: cam at mcc.id.au; mpeg-OTspec at yahoogroups.com
Subject: Re: [mpeg-OTspec] format of CSS Variables has changed

Hello Vladimir,

Monday, March 24, 2014, 8:16:43 PM, you wrote:

> Hi Cameron,

> Thank you very much for letting us know about the upcoming changes in 
> the CSS Variables spec and the new format for custom properties names. 
> I will add these to the list of changes related to the user agent 
> style sheet, with this and earlier changes you recommended it will 
> look as follows (just want to make sure that I get everything right):

Much better with display: none rather than zero font size! Two small changes (trim double ;; and there are two lines of comments, not one)

@namespace svg url(http://www.w3.org/2000/svg);
svg|text, svg|foreignObject {
     display: none !important;
}
:root {
   fill: context-fill;
   fill-opacity: context-fill-opacity;
   stroke: context-stroke;
   stroke-opacity: context-stroke-opacity;
   stroke-width: context-value;
   stroke-dasharray: context-value;
   stroke-dashoffset: context-value;
/* examples: optional custom property declarations
   --color<num>: <color>; */
   --color0: rgba(255,0,0, 0.5);
}

Is it sufficiently clear that the --colorn lines can be edited to suit while the rest is fixed and must not be changed?

--
Best regards,
 Chris                            mailto:chris at w3.org