13658 2011-08-04 02:28:07 +0000 Allow customizing the details element 2011-11-24 02:41:09 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX a11y P2 major --- 1 gcl-0039 contributor ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52298 0 gcl-0039 2011-08-04 02:28:07 +0000 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. 52387 1 mike 2011-08-04 05:00:56 +0000 mass-moved component to LC1 53132 2 jackalmage 2011-08-04 05:06:58 +0000 This is expected to be handled by CSS. 60198 3 mike 2011-11-20 15:11:33 +0000 Greg, this bug is waiting for you to respond to comment #2: > This is expected to be handled by CSS. 60420 4 ian 2011-11-24 02:38:02 +0000 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