W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2010

[Bug 8379] Remove Section 4.11.1 The Details Element

From: <bugzilla@wiggum.w3.org>
Date: Mon, 11 Jan 2010 01:38:41 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NU9Ev-0000y4-Jp@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8379


Aleksey <anime4christ@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anime4christ@gmail.com




--- Comment #12 from Aleksey <anime4christ@gmail.com>  2010-01-11 01:38:41 ---
How about if we use details/legend, but also allow an intermediate form until
browsers catch up: the first child of details with the role of "legend" could
be used instead of legend as well. Another, less desirable, solution could be
an attribute in details that selects the element that acts as "legend" the way
form elements have a form attribute.

Examples of solution 1:
<details>
  <span role="legend">Summary</span>
  <p>Long story</p>
</details>

<details>
  <p role="legend">The Legend...</p>
  <p>of HTML 5.</p>
</details>

<details>
  <legend><span role="legend">Details</span></legend>
  <p>Fall back is partially possible with this method</p>
</details>

Examples of solution 2:
<h2 id="details_legend1">Details</h2>
<details legend="#details_legend1">
  <p>The gory details</p>
</details>

<details legend="#legend2">
  <span id="legend2">Dislike</span>
  <p>I dislike the second solution because of its complexity,
    but it would be okay if there was no other way.</p>
</details>


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 11 January 2010 01:38:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC