[Bug 11084] @open on details should reflect as defaultOpen, for consistency with checked, value, and potentially muted. Then a CSS pseudoclass of :open should be created to match open details elements, similar to :checked.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11084

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-12-27 23:41:58 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: <details open> is specifically designed to test how DOM-mutating
features work in practice, so that we can learn from it, and apply those
lessons with future features. The .defaultValue design of <input> has been
widely criticised but we don't have good information on whether or not the
alternative is actually better, and <details> is a good way to test it.

-- 
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, 27 December 2010 23:42:00 UTC