401
edits
(improve intro text) |
(explicitly mentioning ruby) |
||
Line 102: | Line 102: | ||
==== the <cue> element ==== | ==== the <cue> element ==== | ||
* is analogous to the [http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-div-element HTML <div> element] and supports all of the attributes and content elements of <div>, in particular all [http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#flow-content flow content] | * is analogous to the [http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-div-element HTML <div> element] and supports all of the attributes and content elements of <div>, in particular all [http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#flow-content flow content] (which includes <ruby>). | ||
* <cue> elements cannot appear inside <cue> elements; it is possible to introduce a parsing rule for <cue> that is similar to <dl>/<dd> where the opening of a new <cue> element implicitly closes the previous one. In this way, it is impossible to write a nested <cue> element - the parser always turns it into something non-nested. | * <cue> elements cannot appear inside <cue> elements; it is possible to introduce a parsing rule for <cue> that is similar to <dl>/<dd> where the opening of a new <cue> element implicitly closes the previous one. In this way, it is impossible to write a nested <cue> element - the parser always turns it into something non-nested. | ||
* it has the following additional attributes: | * it has the following additional attributes: |
edits