- From: Charles McCathieNevile <charles@w3.org>
- Date: Thu, 11 Jul 2002 21:25:03 -0400 (EDT)
- To: "Ian B. Jacobs" <ij@w3.org>
- cc: <w3c-wai-ua@w3.org>
The way that CSS handles this, with computed values and actual values, is probably a good model. Basically there is the theoretical value of something, which might be rounded off, but some calculations are required to be done on the theroetical value while others can be applied to the actual value being used. In CSS1 the relevant paragraph is the last in the section 6 - units at http://www.w3.org/TR/REC-CSS1#length-units (helps to have an outline navigation function I guess) as part of the chapter on units, and in CSS2 it is at section 6.1 "Specified, Computed and Actual values" at http://www.w3.org/TR/REC-CSS2/cascade.html#q1 cheers Chaals >UAWG teleconference, 11 Jul 2002 [snip] >------------------ >On checkpoint 4.1 >------------------ > >IJ: What about new wording? > > 1. Allow global configuration of the scale of visually rendered > text. Preserve text size differences when the user changes the > scale. > >IJ: Suggest: "Text rendered at different sizes should scale >proportionally." > >HB: What about rounding errors? > >Action IJ: > > 1. Change second sentence in bullet one to > "Text rendered at different sizes should scale proportionally." > > 2. Clarify that rounding may occur and is appearing. >
Received on Thursday, 11 July 2002 21:25:19 UTC