<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.whatwg.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Brucelawson</id>
	<title>WHATWG Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.whatwg.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Brucelawson"/>
	<link rel="alternate" type="text/html" href="https://wiki.whatwg.org/wiki/Special:Contributions/Brucelawson"/>
	<updated>2026-05-14T04:09:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://wiki.whatwg.org/index.php?title=Summary_element&amp;diff=5152</id>
		<title>Summary element</title>
		<link rel="alternate" type="text/html" href="https://wiki.whatwg.org/index.php?title=Summary_element&amp;diff=5152"/>
		<updated>2010-08-04T08:00:02Z</updated>

		<summary type="html">&lt;p&gt;Brucelawson: /* summary flexibility advantages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{stub}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element is a new element in HTML5, a child of the new &amp;lt;code&amp;gt;&amp;amp;lt;[[details]]&amp;amp;gt;&amp;lt;/code&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
{{For|the summary attribute|Table Summary}}&lt;br /&gt;
&lt;br /&gt;
== summary naming or flexibility ==&lt;br /&gt;
&lt;br /&gt;
Currently the &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element is a special element specifically for use for the label inside the &amp;lt;code&amp;gt;&amp;amp;lt;details&amp;amp;gt;&amp;lt;/code&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
The name of the &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element however is too generic sounding of an element name for this special usage.  &lt;br /&gt;
&lt;br /&gt;
It is inevitable that people will begin using the &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element when they simply mean a semantic &amp;quot;summary&amp;quot;, perhaps of a &amp;lt;code&amp;gt;&amp;amp;lt;section&amp;amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;article&amp;amp;gt;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
I say inevitable due to the broad evidence presented by the known existing problem with the &amp;lt;code&amp;gt;&amp;amp;lt;address&amp;amp;gt;&amp;lt;/code&amp;gt; element (special use - for contact information for the document, but used and often errantly taught as a generic &amp;quot;address&amp;quot; for street addresses).&lt;br /&gt;
&lt;br /&gt;
Thus we should &amp;lt;em&amp;gt;either&amp;lt;/em&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Rename the details &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt;&#039;&#039;&#039; to something more specific (suggestions welcome), &amp;lt;em&amp;gt;OR&amp;lt;/em&amp;gt;:&lt;br /&gt;
# &#039;&#039;&#039;Alternatively make the &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element generic.&#039;&#039;&#039; Make it an actual summary inside &amp;lt;code&amp;gt;&amp;amp;lt;article&amp;amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;body&amp;amp;gt;&amp;lt;/code&amp;gt;, as well as inside &amp;lt;code&amp;gt;&amp;amp;lt;details&amp;amp;gt;&amp;lt;/code&amp;gt;. Allow &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; anywhere &amp;lt;code&amp;gt;&amp;amp;lt;header&amp;amp;gt;&amp;lt;/code&amp;gt; is allowed (basically, make it a part of the new section related elements).&lt;br /&gt;
&lt;br /&gt;
I prefer the second solution, make the &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element more generic/flexible. — [[User:Tantek|Tantek]] 20:38, 3 August 2010 (UTC)&lt;br /&gt;
&lt;br /&gt;
=== summary flexibility advantages ===&lt;br /&gt;
Advantages of making the &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element more generic and flexible:&lt;br /&gt;
* This is &#039;&#039;&#039;close to the semantic of the Atom &amp;quot;summary&amp;quot; element&#039;&#039;&#039;, and the hAtom microformat &#039;entry-summary&#039; property.&lt;br /&gt;
* This would allow an &#039;&#039;&#039;enhancement of the algorithm for converting HTML5 to Atom&#039;&#039;&#039;: take the first HTML5 &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; inside an &amp;lt;code&amp;gt;&amp;amp;lt;article&amp;amp;gt;&amp;lt;/code&amp;gt; being converted to an entry, and use that HTML5 &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; as the Atom entry  &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;discussion&amp;quot;&amp;gt;&lt;br /&gt;
Opinions / discussion:&lt;br /&gt;
* +1 [[User:Tantek|Tantek]] - I think web authors would make good use of a new generic &amp;lt;code&amp;gt;&amp;amp;lt;summary&amp;amp;gt;&amp;lt;/code&amp;gt; element.&lt;br /&gt;
* Bruce Lawson: I don&#039;t think there&#039;s a need for a generic summary element. But I&#039;d support renaming the summary attribute of details (because it doesn&#039;t really summarise). Perhaps &amp;quot;rubric&amp;quot; could replace details&amp;gt;summary and figure&amp;gt;figcaption ?&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Brucelawson</name></author>
	</entry>
</feed>