Change Proposal: figure and details - Revision history

Mjs: /* Proposal Details */

2010-01-12T01:31:13Z

Proposal Details

← Older revision		Revision as of 01:31, 12 January 2010
Line 111:		Line 111:
	Semantically, and for purposes of UA behavior, we only really need to distinguish the caption part of the element. There is no need to wrap the remaining body part with a special element. True, they can be handy as a styling hook, but authors who need that styling hook can always use <div>.		Semantically, and for purposes of UA behavior, we only really need to distinguish the caption part of the element. There is no need to wrap the remaining body part with a special element. True, they can be handy as a styling hook, but authors who need that styling hook can always use <div>.

	=== ~~Proposal~~ Details ===		=== Details ===

	This proposal includes the following specific changes:		This proposal includes the following specific changes:

Lachlan Hunt: /* Impact */

2010-01-12T00:03:16Z

Impact

← Older revision		Revision as of 00:03, 12 January 2010
Line 144:		Line 144:
	This proposal would have a potential negative impact on authors: it would introduce two new elements relative to the current spec.		This proposal would have a potential negative impact on authors: it would introduce two new elements relative to the current spec.

	However, the positive impact is arguably greater. The new elements would be more readable, more intuitive, and more in line with the standard HTML design pattern for structured elements. Thus, despite the addition of more elements, the overall increase in cognitive load will be less. In addition, there is no need to use <div> or any other wonky workarounds to get it to work in legacy UAs.		However, the positive impact is arguably greater. The new elements would be more readable, more intuitive, and more in line with the standard HTML design pattern for structured elements. Thus, despite the addition of more elements, the overall increase in cognitive load will be less. In addition, there is no need to use <div> or any other wonky workarounds to get it to work in legacy UAs.

	The impact on implementations is trivial. fcaption and dlabel are trivial to implement, and the appearance and behavior can be mostly defined via stylesheet. This is not significantly more work than altering the rendering of dt and dd inside figure and details; in fact it may be less work in some implementations.		The impact on implementations is trivial. fcaption and dlabel are trivial to implement, and the appearance and behavior can be mostly defined via stylesheet. This is not significantly more work than altering the rendering of dt and dd inside figure and details; in fact it may be less work in some implementations.

Mjs: /* Proposal Details */

2010-01-12T00:02:50Z

Proposal Details

← Older revision		Revision as of 00:02, 12 January 2010
Line 116:		Line 116:

	1) Define a new element fcaption. Details would be approximately as follows:		1) Define a new element fcaption. Details would be approximately as follows:
	Categories: none
	Contexts in which the element may be used: As the first or last child of a figure element.		Categories: none
	Content model: flow content		Contexts in which the element may be used: As the first or last child of a figure element.
	Content attributes: global attributes		Content model: flow content
	DOM interface: HTMLElement		Content attributes: global attributes
	Semantics: The fcaption element represents the caption of the figure that is its parent, if it has a parent that is a figure element.		DOM interface: HTMLElement
			Semantics: The fcaption element represents the caption of the figure that is its parent, if it has a parent that is a figure element.

	2) Define a new element dlabel. Details would be as above, but replacing mentions of "figure" with "details".		2) Define a new element dlabel. Details would be as above, but replacing mentions of "figure" with "details".

	3) Change figure as follows:		3) Change figure as follows:
	New content model: "Flow content, optionally either preceded by or followed by an fcaption element."		New content model: "Flow content, optionally either preceded by or followed by an fcaption element."
	New caption definition: "The first fcaption element child of the element, if any, represents the caption of the figure element's contents. If there is no child fcaption element, then there is no caption."		New caption definition: "The first fcaption element child of the element, if any, represents the caption of the figure element's contents. If there is no child fcaption element, then there is no caption."
	New content definition: "All child elements other than the first fcaption element, if there are any, represent the element's contents. If there are no child elements besides the first fcaption, then there are no contents.		New content definition: "All child elements other than the first fcaption element, if there are any, represent the element's contents. If there are no child elements besides the first fcaption, then there are no contents.
	Update the examples appropriately.		Update the examples appropriately.
	Update the suggested UA stylesheet in the Rendering section as appropriate.		Update the suggested UA stylesheet in the Rendering section as appropriate.

	4) Change details as follows:		4) Change details as follows:

Mjs: /* Proposal Details */

2010-01-12T00:00:16Z

Proposal Details

← Older revision		Revision as of 00:00, 12 January 2010
Line 133:		Line 133:

	4) Change details as follows:		4) Change details as follows:
	New content model: "~~Flow content~~, ~~optionally either preceded by or~~ followed by ~~a dlabel element~~."		New content model: "One dlabel element, followed by Flow content."
	New summary definition: "The first dlabel element child of the element, if any, represents the summary of the details. If there is no child dlabel element, the user agent should provide its own label (e.g. "Details")."		New summary definition: "The first dlabel element child of the element, if any, represents the summary of the details. If there is no child dlabel element, the user agent should provide its own label (e.g. "Details")."
	New details definition: "All child elements other than the first dlabel element, if there are any, represent the details. If there are no child elements besides the first dlabel, then there are no details.		New details definition: "All child elements other than the first dlabel element, if there are any, represent the details. If there are no child elements besides the first dlabel, then there are no details.
	Update the examples appropriately.		Update the examples appropriately.
	Update the suggested UA stylesheet in the Rendering section as appropriate.		Update the suggested UA stylesheet in the Rendering section as appropriate.


	=== Impact ===		=== Impact ===

TabAtkins: /* Impact */

2010-01-11T23:58:43Z

Impact

← Older revision		Revision as of 23:58, 11 January 2010
Line 144:		Line 144:
	This proposal would have a potential negative impact on authors: it would introduce two new elements relative to the current spec.		This proposal would have a potential negative impact on authors: it would introduce two new elements relative to the current spec.

	However, the positive impact is arguably greater. The new elements would be more readable, more intuitive, and more in line with the standard HTML design pattern for structured elements. Thus, despite the addition of more elements, the overall increase in cognitive load will be less. In addition, there is no need to use <div> or any other wonky workarounds to get it to work in legacy UAs.		However, the positive impact is arguably greater. The new elements would be more readable, more intuitive, and more in line with the standard HTML design pattern for structured elements. Thus, despite the addition of more elements, the overall increase in cognitive load will be less. In addition, there is no need to use <div> or any other wonky workarounds to get it to work in legacy UAs.

	The impact on implementations is trivial. fcaption and dlabel are trivial to implement, and the appearance and behavior can be mostly defined via stylesheet. This is not significantly more work than altering the rendering of dt and dd inside figure and details; in fact it may be less work in some implementations.		The impact on implementations is trivial. fcaption and dlabel are trivial to implement, and the appearance and behavior can be mostly defined via stylesheet. This is not significantly more work than altering the rendering of dt and dd inside figure and details; in fact it may be less work in some implementations.

Mjs: /* Proposal 3 */

2010-01-11T23:51:33Z

Proposal 3

@@ Line 60: / Line 60: @@
 == Proposal 3 (<code><figure><fcaption>...</fcaption>...</figure>; <details><dlabel>...</dlabel>...</details></code>) ==
 === Summary ===
@@ Line 97: / Line 98: @@
 h1 connotes "header", which is not quite right for either figure or details.
 "caption" and "label", or variations thereof, are the most semantically appropriate names for the caption and label respectively on figure and details.
@@ Line 103: / Line 106: @@
 Reuse of almost any existing element in an unrelated context introduces compatibility problems, whether "hard" problems with parsing or behavior, or "soft" problems with pre-existing author styles. This Change Proposal uses brand new elements and thus avoids all these problems, unlike the use of dt/dd, legend, label, caption, or h1. All of those are known to have some lesser or greater technical issues.
 === Proposal Details ===
 === Impact ===
 == Proposal 3b (<code><figure><figcaption>...</figcaption>...</figure>; <details><dsummary>...</dsummary>...</details></code>) ==

Hixie: /* Proposal 4 (<caption>...</caption>...; <label>...</label>...) */

2010-01-11T23:40:36Z

Proposal 4 (<caption>...</caption>...; <label>...</label>...)

← Older revision		Revision as of 23:40, 11 January 2010
Line 109:		Line 109:

	=== Impact ===		=== Impact ===

			== Proposal 3b (<code><figure><figcaption>...</figcaption>...</figure>; <details><dsummary>...</dsummary>...</details></code>) ==
			Same as proposal 3, but with the element names "figcaption" and "dsummary" respectively.

			Reasoning: "figcaption" is more memorable. "dsummary" more accurately describes what the "label" of a <details> element is.


	== Proposal 4 (<code><figure><caption>...</caption>...</figure>; <details><label>...</label>...</details></code>) ==		== Proposal 4 (<code><figure><caption>...</caption>...</figure>; <details><label>...</label>...</details></code>) ==

Hixie: /* Proposal 7 == Proposal 3 (......; ...... or ......; ......) */

2010-01-11T23:36:42Z

Proposal 7 == Proposal 3 (......; ...... or ......; ......)

← Older revision		Revision as of 23:36, 11 January 2010
Line 143:		Line 143:
	Easy denotation of figure captions, without any compatibility hacks that may persist long into the future.		Easy denotation of figure captions, without any compatibility hacks that may persist long into the future.

	== Proposal 7 ~~== Proposal 3~~ (<code><figure><fcaption>...</fcaption>...</figure>; <details><dlabel>...</dlabel>...</details></code> or <code><figure><fcaption>...</fcaption><fbody>...</fbody></figure>; <details><dlabel>...</dlabel><dbody>...</dbody></details></code>) ==		== Proposal 7 (<code><figure><fcaption>...</fcaption>...</figure>; <details><dlabel>...</dlabel>...</details></code> or <code><figure><fcaption>...</fcaption><fbody>...</fbody></figure>; <details><dlabel>...</dlabel><dbody>...</dbody></details></code>) ==

	=== Summary ===		=== Summary ===

	The current HTML5 draft uses the dt and dd elements to markup the captions and content of the figure and details elements. This change proposal explains why the dt and dd elements are a poor choice for these purposes and proposes an alternative. Specifically, the proposal is to introduce a new fcaption element for marking up the caption within figure, and a dlabel element for use within details to replace dt. In addition, it proposes an optional fbody element for use inside figure, and an optional dbody element for use inside details, to mark up the content/body and replace dd.		The current HTML5 draft uses the dt and dd elements to markup the captions and content of the figure and details elements. This change proposal explains why the dt and dd elements are a poor choice for these purposes and proposes an alternative. Specifically, the proposal is to introduce a new fcaption element for marking up the caption within figure, and a dlabel element for use within details to replace dt. In addition, it proposes an optional fbody element for use inside figure, and an optional dbody element for use inside details, to mark up the content/body and replace dd.

Hixie: /* Proposal 7 */

2010-01-11T23:36:22Z

Proposal 7

← Older revision		Revision as of 23:36, 11 January 2010
Line 143:		Line 143:
	Easy denotation of figure captions, without any compatibility hacks that may persist long into the future.		Easy denotation of figure captions, without any compatibility hacks that may persist long into the future.

	== Proposal 7 ==		== Proposal 7 == Proposal 3 (<code><figure><fcaption>...</fcaption>...</figure>; <details><dlabel>...</dlabel>...</details></code> or <code><figure><fcaption>...</fcaption><fbody>...</fbody></figure>; <details><dlabel>...</dlabel><dbody>...</dbody></details></code>) ==

	=== Summary ===		=== Summary ===

	The current HTML5 draft uses the dt and dd elements to markup the captions and content of the figure and details elements. This change proposal explains why the dt and dd elements are a poor choice for these purposes and proposes an alternative. Specifically, the proposal is to introduce a new fcaption element for marking up the caption within figure, and a dlabel element for use within details to replace dt. In addition, it proposes an optional fbody element for use inside figure, and an optional dbody element for use inside details, to mark up the content/body and replace dd.		The current HTML5 draft uses the dt and dd elements to markup the captions and content of the figure and details elements. This change proposal explains why the dt and dd elements are a poor choice for these purposes and proposes an alternative. Specifically, the proposal is to introduce a new fcaption element for marking up the caption within figure, and a dlabel element for use within details to replace dt. In addition, it proposes an optional fbody element for use inside figure, and an optional dbody element for use inside details, to mark up the content/body and replace dd.

Hixie: /* Proposal 6 */

2010-01-11T23:34:52Z

Proposal 6

← Older revision		Revision as of 23:34, 11 January 2010
Line 124:		Line 124:
	CON: Content model would be ambiguous.		CON: Content model would be ambiguous.

	== Proposal 6==		== Proposal 6 (<code><figure><p caption>...</p>...</figure></code>)==
	===Summary===		===Summary===
	The proposal is to introduce a caption attribute that may be used on an element within figure to denote the contents of that element as being the caption. This proposal does not address the details element.		The proposal is to introduce a caption attribute that may be used on an element within figure to denote the contents of that element as being the caption. This proposal does not address the details element.
Line 142:		Line 142:
	===Impact===		===Impact===
	Easy denotation of figure captions, without any compatibility hacks that may persist long into the future.		Easy denotation of figure captions, without any compatibility hacks that may persist long into the future.


	== Proposal 7 ==		== Proposal 7 ==