HTML and CSS Reference
Here is an example of how the details element might appear:
The final stop on this speculative tour is the output element, which is used to define a
region that will be used as output from some calculation or form control. Here I imagine
using the calendar picker and having the eventual release date of HTML5 being revealed in
an output element:
<form action="#" method="get" id="testform">
<p><input type="date" id="year">
<p> HTML5 released in the year
<output for="year"> </output></p>
Script could certainly be used to perform this action:
In this case, it is doubtful we need to concern ourselves too much with the likely
representation of this yet-to-be supported element, because, as defined, output is just
a semantic element and could be simulated in traditional HTML using a <div> .
The Uncertain Future of Frames
The introduction of frames with Netscape 2 heralded some of the first markup changes to
support Web applications. Interestingly, the HTML5 specification drops <frameset> ,
<frame> , and <noframes> because “their usage affected usability and accessibility for the
end user in a negative way 4 .” Despite dropping it from support, the specification does still
offer rendering rules for the frame and frameset elements. This is more evidence that the
HTML5 specification tries to account for anything a Web developer may design even if it is
not according to the specification.
Given the fairly widespread use of frames, some online pundits have suggested that this
frame elimination can be worked around by using an HTML 4 frameset to pull in HTML5
documents. In this spirit, we may validate all around but not really address the concerns of
the W3C and others. It would seem from these possible changes from HTML5 that the days
of frames are numbered, or are they?
HTML5 continues to support <iframe> ; in fact, it not only supports it but extends the
tag. The inline frame has plenty of life left if the HTML5 vision comes true because it will be
used to include new content and functionality in pages from remote sources and may even
be used in intra-document communication. So, the future of frames as far as HTML5 is
concerned isn't set.
4 Quoted from http://www.w3.org/TR/html5-diff circa 2009.