This is probably for Finn. I just discovered something unusual in the 
spec. It describes the dominant-baseline property in a number of places 
as: 'The "dominant-baseline" property is a compound value with three 
components.' It then goes on and lists the 3 components as 
"dominant-baseline-identifier", "baseline-table" and "baseline-table 
font-size" collectively referred to as a "scaled-baseline-table". Or to 
put it differently - the computed value of the "dominant-baseline" 
property is a value of type "scaled-baseline-table".

The current property system models the dominant-baseline property only 
as an enum and doesn't provide for its computed value being the above 

Any suggestions how to best integrate this into the property system. 
Doesn't that mean the getValue on the dominant-baseline property should 
not return an enum but a value of type "scaled-baseline-table"?



Reply via email to