- From: Ladd Van Tol <ladd@criticalpath.com>
- Date: Fri, 4 May 2007 13:03:21 -0700
- To: www-style@w3.org
- Cc: Bert Bos <bert@w3.org>
3.1.2. Using Named Strings
Should define behavior for an undefined named string (empty string?)
4. Leaders
"UAs should attempt to align leader patterns on a page." -- suggested
language: "User Agents should attempt to horizontally align
corresponding glyphs from the leader pattern between consecutive lines"
5. Cross-references
It would be helpful to provide a mechanism to treat external page
links differently. For many document types, it would be desirable to
append "(see page nn)" to only internal destination anchors
("#someid"). An elegant mechanism for specifying this in CSS is not
immediately obvious.
6. Footnotes
The first two examples have syntax issues. Suggest closing the <p>
tags, and quoting the id value "words" .
9.1 Hyphenate properties
Should specify allowed format(s) for hyphenation dictionaries -- is
this TeX-style dictionaries? Making this UA-dependent would be bad.
10.3 The ‘symbol()’ list-style-type
Section header 10.3 should read "The 'symbols()' list-style type,
assuming the contained example is accurate.
20. Change bars
"To avoid these limitations, the beginning of a change mark is
associated with one document and the end of a change mark is
associated with another document." -- should read "one element" and
"another element".
22. Named page lists
Should coordinate terminology with that of Named Strings. Leaving
value could be exit value.
23.2. Index
In the example, the dfn tag should read: <dfn class="entry">
Received on Monday, 7 May 2007 12:08:22 UTC