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 7643 - Why not use display:none instead of overflow:hidden; height:0? display:none seems to have the desired behavior in terms of exposure to AT and keyboard navigation in browsers.
Summary: Why not use display:none instead of overflow:hidden; height:0? display:none s...
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: NE, NoReply
: 7655 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-09-15 21:54 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-09-15 21:54:57 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-details-element-0

Comment:
Why not use display:none instead of overflow:hidden; height:0? display:none seems to have the desired behavior in terms of exposure to AT and keyboard navigation in browsers.

Posted from: 83.252.193.59
Comment 1 Simon Pieters 2009-09-16 14:06:28 UTC 
*** Bug 7655 has been marked as a duplicate of this bug. ***
Comment 2 Ian 'Hixie' Hickson 2009-09-29 02:02:44 UTC 
The height was used instead of display to make the element open and close because then it can be animated — but I guess that isn't necessary. I've made it more vague.

The clipping when open is intentional, because if we don't clip then animating the <details> becomes dangerous since different solutions might expose different rendering artifacts.
Comment 3 contributor 2009-09-29 02:03:09 UTC 
Checked in as WHATWG revision r4026.
Check-in comment: Be less specific about how <details> hides its kids.
http://html5.org/tools/web-apps-tracker?from=4025&to=4026
Comment 4 Maciej Stachowiak 2010-03-14 14:51:22 UTC 
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.