This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13658 - Allow customizing the details element
Summary: Allow customizing the details element
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: contributor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2011-08-04 02:28 UTC by Greg Lowney
Modified: 2011-11-24 02:41 UTC (History)
6 users (show)

See Also:


Attachments

Description Greg Lowney 2011-08-04 02:28:07 UTC
The default presentation of details elements is fine for dialog boxes and other cases where the content wants to emulate the platform or browser. However, authors of other content will want to customize its presentation; for example, one may want to replace the browser's widget (usually a triangle) with an icon that is more suggestive of its function (such as a question mark in a circle for displaying a definition). If HTML5 does not permit this, authors will use custom scripting rather than standard controls, which can render them incompatible with assistive technology and reduce the ability of users to customize them using browser settings, browser add-ins, or user style sheets.

Similarly, ideally an author-provided or user-provided style sheet would be able to adjust certain aspects of the detail element's presentation, such as the height of the control widget and perhaps overriding the open attribute.
Comment 1 Michael[tm] Smith 2011-08-04 05:00:56 UTC
mass-moved component to LC1
Comment 2 Tab Atkins Jr. 2011-08-04 05:06:58 UTC
This is expected to be handled by CSS.
Comment 3 Michael[tm] Smith 2011-11-20 15:11:33 UTC
Greg, this bug is waiting for you to respond to comment #2:
> This is expected to be handled by CSS.
Comment 4 Ian 'Hixie' Hickson 2011-11-24 02:38:02 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: see comment 2