WHATWG Weekly: Quiet Week
A relatively quiet week this week.
Nicholas Zakas brought up a question on the scoped attribute of the style element, when the element is placed in an area expecting flow content. This triggered an interesting discussion about what works, as compared to what's valid.
Stefan Håkansson suggested that since the Peer-to-peer and Stream APIs are similar between what is proposed in the WHATWG spec, and a comparable spec written by Harald Alvestrand that one is adopted as a base for further work. Harold expressed willingness, but is concerned about embedding the API in HTML5.
Speaking of which, my favorite quote of the week comes from Michael Smith in the WHATWG IRC:
# [18:14] anyway, I'm happy until PHP starts getting called HTML5
Rumor has it that Starbuck's is coming out with an HTML5 brand of coffee—twice the caffeine with a hint of fruity, hot pepper notes.
On the W3C side, the discussion continues about HTML5 licensing.
The issue about longdesc has been re-opened and there was some fragmented discussion on this in the W3C HTML WG email list. This discussion on longdesc seems to have the most activity, but nothing has been decided.
What was decided was Issue 126 on the requirement to break RFC 2616 compliance with respect to backslashes not needed for legacy content. The co-chairs decided to leave the text in HTML5, unchanged.
The co-chairs also issued a decision on Issue 140. The co-chairs did adopt the proposal by Noah Mendelsohn to modify the text of HTML5 so that "conforming document" now becomes "conforming HTML5 document", and that the term only be applied to the HTML5 document, itself. This does necessitate changes to the HTML5 spec.
Another co-chair decision is related to Issue 139, which asked that the Microdata usability study acknowledgement be removed from the HTML5 specification, since Microdata is no longer contained in the HTML5 specification. Instead, the acknowledgement will be moved to the Microdata specification.
If I missed anything that should have been included, add a note in comments and I'll update this post. Otherwise, ta until next week.
The HTML to Platform Accessibility APIs Implementation Guide is up for first publication this week.
In addition, the HTML WG co-chairs asked for consensus on publishing eight other working drafts including HTML5.