[css-conditional-values] Changes

Author: LeaVerou

css-conditional-values/Overview.bs

@@ -86,10 +86,14 @@ before being passed to any of the above procedures.)
 </div>
 
 The host syntax defines how relative values (such as percentages or em units) are resolved in <<comparison-operand>>.
-When <<condition>> is used in a declaration, these relative values resolve against the declaration property.
+When <<condition>> is used in a declaration,
+these relative values resolve in the same way as regular values in the declaration property.
 
-Note: Why are using '=' for equality and not ':' as is established in [[css-conditional-4]] already?
+Note: Why are we using ''='' for equality and not ':' as is established in [[css-conditional-4]] already?
 Because a lot of third party code (syntax highlighters etc) assumes that colons separate declarations and would break.
+Also, ''foo: bar'' establishes a key-value pair,
+whereas in equality comparisons the two operands are of equal weight,
+and do not establish a key-value pair.
 
 Issue: Do we need a "not equals" operator or is 'not(op1 = op2)' sufficient?
 
@@ -125,10 +129,20 @@ Issue: Define these concepts for comparisons (currently they point to calc())
 Inline conditionals: The ''if()'' function
 ===========================================
 
-The ''if()'' function allows authors to set a property value (or parts thereof) to different values based on certain conditions.
+The ''if()'' function allows authors to set a property value (or parts thereof)
+to different values based on certain conditions.
 
 <pre class="prod def">
-<<if()>>  = if( <<condition>>, <<consequent>> [, <<antecedent>>])
+<<if()>>  = if( <<condition>>, <<consequent>> [, <<antecedent>>]?)
+<<consequent>> = <<declaration-value>>
+<<antecedent>> = <<declaration-value>>
+</pre>
+
+Issue: How can authors specify consequents or antecedents that include commas?
+Alternative syntax that adresses this, though may be hard to read when consequent/antecedent are keywords:
+
+<pre class="prod def">
+<<if()>>  = if( <<condition>> then <<consequent>> [else <<antecedent>>]?)
 <<consequent>> = <<declaration-value>>
 <<antecedent>> = <<declaration-value>>
 </pre>
@@ -169,3 +183,10 @@ as the ''var()'' function, for the same reasons.
 Issue: How to disambiguate when used in a place where arguments are disambiguated by type?
 Unlike ''var()'', this cannot just be resolved at substitution,
 because we need to be able to interpret the values to compute the condition and perform the substitution accordingly.
+
+Privacy and Security Considerations {#priv-sec}
+===============================================
+
+This specification defines a purely author-level mechanism for specifying conditionals
+on styling information within a page they control.
+As such, there are no new privacy considerations.