- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Mon, 10 Nov 2014 13:16:24 +0000
- To: Andrea Rendine <master.skywalker.88@gmail.com>
- Cc: HTMLWG WG <public-html@w3.org>, "Michael[tm] Smith" <mike@w3.org>
- Message-ID: <CA+ri+VnN=xjDPFDD5vcFkOzrgxKfuy7XkmEY9+8hZqq-tnunoQ@mail.gmail.com>
details/summary was removed from HTML5 REC because it did not have 2 interoperable implementations (like a number of other new features which were also removed). It lives on in HTML 5.1 [1] as there is a reasonable expectation that interoperable implementations will happen in the timeframe of 5.1 going to REC (in 2016) [1] http://www.w3.org/html/wg/drafts/html/master/interactive-elements.html#the-details-element -- Regards SteveF HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> On 10 November 2014 13:07, Andrea Rendine <master.skywalker.88@gmail.com> wrote: > To the attention of whoever interested. > Does anybody know when the <details> element, along with its controller > <summary> and all references to them, were removed from the official spec? > And more important, why was it removed? Is it due to lacking support? > Because, IMHO, removing an element from the list of allowed elements is not > the best way to ensure that authors make use of it, thus driving vendors to > upgrade browsers and offer support. I mean, authors worrying about validity > issues will not use it at all. Like me, as I'm feeling the urge of removing > it instead of ensuring its functionality via a polyfill. > I hope the removal was a mistake. Evidence would be the fact that it is > not listed among the obsolete elements. Despite the section name, the list > also contains the ominous <hgroup> element, which in an early stage was > meant to group headings and subheadings in the form of <h#> elements poorly > used. > Otherwise it could be due to the fact that it is basically a > presentational element, whose purpose is NOT to highlight a real "details" > section, but to have a widget with an open/close toggle behavior. But, were > that the case, why is the element still present in the nightly? > As a side note, for validator crew (and unfortunately this means only Mr > Michael Smith): the validator says that the element "is not supported > properly by browsers yet", but as a matter of fact it is a non-conforming > element now. Please update the error message properly when you have time. > Sorry for verboseness. > Andrea R. >
Received on Monday, 10 November 2014 13:17:31 UTC