On Sat, 29 Aug 2009, Schuyler Duveen wrote:
There is a use case for hierarchical progress elements: e.g. multiple
file uploads (or multiple phases). Consider the following example:
progress id=p max=17 value=5 data-units=MB
progress id=current-file-progress max=21/progress
/progress
There is a use case for hierarchical progress elements: e.g. multiple
file uploads (or multiple phases). Consider the following example:
progress id=p max=17 value=5 data-units=MB
progress id=current-file-progress max=21/progress
/progress
could be displayed something like this:
style div
On Sun, 26 Nov 2006, Anne van Kesteren wrote:
Some element content model explicitly mention that they can't contain
themself. This probably makes sense for the following elements as well:
* meter
* progress
* time
* t
* m
* abbr?
* cite?
There might be more.
Done for meter,
Michael(tm) Smith wrote - a long time ago:
However, I would vehemently stress that it is not that uncommon
for notes and marginalia to themselves have notes or marginalia,
I don't doubt that there are some, but are you aware of any
specific examples?
The Talmud! Or most scholarly works of
I've been meaning to send a rambling discussion of annotations to either
the www-html or whatwg lists at some point. However, I would vehemently
stress that it is not that uncommon for notes and marginalia to
themselves have notes or marginalia, and it would seem particularly odd
to allow that in
On Nov 30, 2006, at 4:53 AM, Michael(tm) Smith wrote:
[nested annotations]
and it would seem particularly odd to allow that in the limited
space of paper but not the free expanse of hypertext.
I think one reason why existing content models exclude them is
the problem of how to render them.
Anne van Kesteren [EMAIL PROTECTED], 2006-11-26 12:58 +0100:
Some element content model explicitly mention that they can't contain
themself. This probably makes sense for the following elements as well:
* meter
* progress
* time
* t
* m
* abbr?
* cite?
There might be more.
