Archive for the ‘Weekly Review’ Category
Revision 6695 made HTML attribute values match in a case-sensitive manner as far as Selectors are concerned. This approach was favored over having a hardcoded list of HTML attributes whose values had to be matched case-insensitively. Revision 6701 removed
selectedOptions from the
input element, a vestige from the Web Forms 2.0 era. Welcome to the weekend (jetlag) edition of the WHATWG Weekly.
The major news today is that since revision 6783 we have a new element:
data. We also lost an element:
data element represents a piece of human readable data that is made machine readable by its required
value attribute. It can either be used for Microdata or as an element to help out scripts, in similar fashion to the
The reason the
time element has been replaced is that its primary use has been for marking up machine-readable times and dates in Microdata vocabularies, which is a use that has been requested for many other types of data as well (currency, numbers, location). The
data element addresses these use cases in a generic fashion and provides yet another hook for scripts to play with.
The same revision also removed the HTML-to-Atom conversion algorithm. Authors can use a schema.org Microdata vocabulary instead.
As reported earlier Simon Pieters did some research into timestamps. He now complemented that with research into separating cues. As a result of this parsing of WebVTT was made more forgiving. Newline handling was made more predictable.
There were many other changes of significance:
- Since revision 6710
MutableTextTrack are identical.
TextTrackCue became mutable in the next revision.
- Revision 6717 aligned the parsing rules for non-negative integers with those of integers.
- Revision 6718 turned the
HTMLDocument interface into an extension of the
Document interface. The plan is to do the same with the
SVGDocument interface down the road and no longer introduce specific
Document interfaces as you really want to have access to all their combined members if you deal with multiple languages at the same time.
- In revision 6727 the HTML standard gained yet another joke, this time in the form of a comment in the source code:
Welcome to crazy town. Population: The Web.
- Now there is a draft for a URL API, we removed
navigator.resolveURL() in revision 6745 as it would become redundant.
- Revision 6754 clarified the scope of attributes defined in the HTML standard. They are only applicable to HTML elements. This includes e.g. Microdata, which for that reason does not work on MathML or SVG at this time.
And even more than those, which you can look up for yourself by going through the HTML5 tracker or by following us on twitter: @WHATWG.
Should we introduce an
isWhiteSpace attribute for
Text nodes, and if we do, what would you use it for? Anyway, WHATWG Weekly, brief one this week.
The big news last week was renewed activity on Gecko:FullScreenAPI, a proposal by Robert O'Callahan to make fullscreen work for the platform. Yours truly made an initial attempt at formalizing it in terms of the DOM and HTML as Fullscreen.
The details of Fullscreen are currently being discussed on the WHATWG mailing list and IRC channel. As a reminder, both are open for anyone to join.
Simon Pieters posted SRT timestamp research. Ryosuke Niwa updated his UndoManager and DOM Transaction proposal. This is the WHATWG Weekly.
In revision 6657 Ian Hickson removed the
text/html-sandboxed MIME type from the HTML standard. The goal of the MIME type was to allow untrusted content to be hosted on the same origin as trusted content. However, given that older versions of Internet Explorer treat content with the
text/html-sandboxed MIME type as content with a
text/html MIME type instead of as downloadable content, the
text/html-sandboxed MIME type did not meet its design goals.
Revision 6668 introduces the ability for the
itemtype attribute to take more than one value. This makes it easier to mark up items in Microdata that share a vocabulary.
On the WebApps WG mailing list Ian Hickson outlined his current views on bindings. In particular the separation between bindings that expose an API (permanent bindings) and bindings that are stylistic (decorator bindings). Meanwhile Roland Steiner has updated the Component Model Discussion wiki page with the open issues, giving a good overview over where we are at this point.
Odin Hørthe Omdal brought up cross-origin image loading via CORS as Gecko and WebKit have different implementations. Julien Chaffraix considers the relation between the
sheet IDL attributes of the
link element to be insufficiently defined. Welcome to the first WHATWG Weekly this October.
HTML is the new HTML
In an attempt to further simplify our efforts, Web Applications 1.0 and its HTML subset have been merged into what is now known as HTML. Redirects are in place, so unless you were writing a thesis on the subject (sorry, FlorianX!), everything should be in order.
Easier element creation
Anne van Kesteren [yes, that's me] suggested a simplified way of creating elements. Basically representing elements and their descendants as an array structure. Combined with the proposal from Ojan Vafai on new DOM manipulation methods this has the potential to drastically improve working with the DOM. You are encouraged to share your thoughts on the matter on the www-dom mailing list.
Philip Jägenstedt provided feedback on WebVTT based on a meeting between various browsers at the Open Video Conference. Tyler Close raised two security issues with
registerProtocolHandler(). This is the WHATWG Weekly.
Changes to HTML
Since revision 6596 the specification defines handling of
multipart/x-mixed-replace resources. A rather peculiar MIME type that allows progressively updating of content. Revision 6595 states that
del are not ideal for marking up edits to tables. This should come as a surprise to exactly nobody.
Adam Klein has outlined the latest proposal to replace Mutation Events on the WebApps WG mailing list: Mutation Observers. While some of the details are still being discussed, it seems this proposal has a better chance at succeeding than previous proposals due to the support of a number of developers from both Mozilla and Google.