HTML <details> Tag
<details> tag represents additional details that the user can view or hide on demand.
It is used with the
<summary> tag to provide a legend that can be clicked on to expand/collapse the details as required. If there is not
<summary> tag, the browser should display its own summary/legend.
<details> element accepts "flow content", which means that it accepts most HTML elements that can appear within the
<body> of an HTML document.
<details> tag is written as
</details> with a
<summary> tag inserted between the start and end tag. The expandable/collapsible content follows the
<summary> tag (but is also contained between the start and end tags of the
<details> <summary>Click to open</summary> <p>Collapsible content...</p> </details>
Basic tag usage
<details> is used along with the
<summary> tag to create expandable content.
If you leave the
<summary> tag out, the browser should create its own legend.
You can have multiple
<details> elements, all expanding and collapsing their own content. This is where the
<summary> tag can really come in handy, otherwise you will see a whole bunch of headings that read Details with nothing else to distinguish each one.
<details> tag can be used to show/hide most elements that appear within an HTML document's
<body> element. This includes text, form controls, images, etc.
The following example demonstrates various elements being placed within the
You can use CSS to add styles to the
<details> element. Not only that, you can use it to style the element in its various states (i.e.
closed), as well as the
<summary> element depending on the state of the
<details> element. In other words, you can specify different styles to use on both the
<details> and the
<summary> elements based on whether the user has expanded or collapsed the control.
Attributes can be added to an HTML element to provide more information about how the element should appear or behave.
There are 3 kinds of attributes that you can add to your HTML tags: Element-specific, global, and event handler content attributes.
<details> element accepts the following attributes.
This table shows the attributes that are specific to the
|open||Specifies whether the details should be open (visible to the user) or closed (hidden from the user).
This is a boolean attribute. If the attribute is present, its value must either be the empty string or a value that is an ASCII case-insensitive match for the attribute's canonical name, with no leading or trailing whitespace (i.e. either
The following attributes are standard across all HTML5 elements. Therefore, you can use these attributes with the
<details> tag , as well as with all other HTML tags.
For a full explanation of these attributes, see HTML 5 global attributes.
Event Handler Content Attributes
Event handler content attributes enable you to invoke a script from within your HTML. The script is invoked when a certain "event" occurs. Each event handler content attribute deals with a different event.
Below are the standard HTML5 event handler content attributes.
Again, you can use any of these with the
<details> element, as well as any other HTML5 element.
For a full explanation of these attributes, see HTML 5 event handler content attributes.
Differences Between HTML 4 & HTML 5
<details> element was not part of HTML 4 and earlier specifications.
<details> tag was also not introduced as part of the HTML5 specification. It was introduced in the HTML 5.1 specification, as well as the WHATWG HTML Living Standard.
For more detail on the
<details> element, see HTML5
<details> Tag. Also check out the links to the official specifications below.
Here's a template for the
<details> tag with all available attributes for the tag (based on HTML5). These are grouped into attribute types, each type separated by a space. In many cases, you will probably only need one or two (if any) attributes. Simply remove the attributes you don't need.
For more information on attributes for this tag, see HTML5
<details open="" accesskey="" class="" contenteditable="" contextmenu="" dir="" draggable="" dropzone="" hidden="" id="" itemid="" itemprop="" itemref="" itemscope="" itemtype="" lang="" spellcheck="" style="" tabindex="" title="" translate="" onabort="" onautocomplete="" onautocompleteerror="" onblur="" oncancel="" oncanplay="" oncanplaythrough="" onchange="" onclick="" onclose="" oncontextmenu="" oncuechange="" ondblclick="" ondrag="" ondragend="" ondragenter="" ondragexit="" ondragleave="" ondragover="" ondragstart="" ondrop="" ondurationchange="" onemptied="" onended="" onerror="" onfocus="" oninput="" oninvalid="" onkeydown="" onkeypress="" onkeyup="" onload="" onloadeddata="" onloadedmetadata="" onloadstart="" onmousedown="" onmouseenter="" onmouseleave="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" onmousewheel="" onpause="" onplay="" onplaying="" onprogress="" onratechange="" onreset="" onresize="" onscroll="" onseeked="" onseeking="" onselect="" onshow="" onsort="" onstalled="" onsubmit="" onsuspend="" ontimeupdate="" ontoggle="" onvolumechange="" onwaiting="" > </details>
For more details about the
<details> tag, see HTML5
Here are the official specifications for the
- HTML Living Standard (WHATWG)
- Current W3C Draft (the next version that is currently being worked on)
What's the Difference?
W3C creates "snapshot" specifications that don't change once defined. So the HTML5 specification won't change once it becomes an official recommendation. WHATWG on the other hand, develops a "living standard" that is updated on a regular basis. In general, you will probably find that the HTML living standard will be more closely aligned to the current W3C draft than to the HTML5 specification.