Hello folks, and welcome to my first WHATWG Weekly. In case you're wondering where Anne van Kesteren is, you can follow his adventures for the next three months at Anne, Tom, and Peter's Trip Weblog. Last time I looked, the gang is in Colombia. And there was something about beer.
peerConnection, <device>, and video conferencing
The biggest change last week was signaled by an email from WHATWG editor, Ian Hickson.
According to the email, Ian made the following changes to WHATWG HTML specification:
- <device> has been replaced with a Geolocation-style API for requesting
user access to local media devices (such as cameras).
- locally-generated streams can be paused and resumed.
- the ConnectionPeer interface has been replaced with a PeerConnection
interface that interacts directly with ICE and its dependencies.
- PeerConnection has been streamlined (compared to ConnectionPeer), e.g.
there is no longer a feature for direct file transfer or for reliable
text messaging.
- the wire format for the unreliable data channel has been specified.
- the spec has been brought up to date with recent developments in other
Web specs such as File API and WebIDL.
Two other WHATWG email list threads are also related to these new updates: one related to PeerConnection encryption, the other providing feedback on the new additions related to the Video conferencing and peer-to-peer communication section in the spec.
Rich Paste and execCommand
Two other lively discussions happened in the WHATWG email lists this last week. The first is one that started the beginning of March and is about the execCommand spec that Aryeh Gregor is working on.
The second is a new thread that started this week, based on a request for image paste capability. It seems this interest has been triggered by work on a patch for this functionality in WebKit/Chrome.
W3C HTML WG Decisions
The co-chairs over at the W3C HTML WG have been busy this week, publishing three new decisions in addition to starting straw polls for others.
In Issue 101, related to the ASCII Character set reference, the co-chairs decided in favor of the proposal to maintain the link to the free of charge ASCII reference (no spec change).
In Issue 125, related to breaking RFC 2616 compliance with respect to single quotes not needed for legacy content, the co-chairs decided in favor of altering the specification in order to comply with Anne's original proposal.
In Issue 128, related to the figure element within <p>, the co-chairs decided on the no-change proposal, leaving figure to be treated the same as <p> and <aside>.
That's it for this week. If I missed anything, let me know and I'll update this post. Otherwise, see you all next week.
update I missed five other W3C HTML WG co-chair decisions:
In Issue 56 on the alignment between HTML5 and IRI align on URLs, the co-chairs decided on restoring the removed text, which I believe maps to this change proposal.
In Issue 88, on meta/content and allowing multiple languages, the co-chairs decided on making Content-Language non-conforming, which does result in a spec change.
One of my issues bit the dust: In Issue 96, the co-chairs decided on the proposal to keep the progress element. This decision was not exactly a surprise.
In Issue 124 on allowing "nofollow" and "noreferrer" as rel values, the co-chairs decided on the proposal that would disallow these values.
In Issue 127, on whether attributes on <link> and <a> can have different effects, the co-chairs decided on the proposal to optimize the text..
So many issues, so little time.
Posted in Weekly Review | 4 Comments »
This is my last WHATWG Weekly for a while. Shelley Powers will take over starting next week. Meanwhile my friend (and colleague these days) Karl Dubost has started writing similar summaries for the W3C Blog: Open Web Platform Weekly Summary. Hopefully this is just the beginning.
EventSource, Workers, and Progress Events
The W3C WebApps Working Group published three Last Call Working Drafts: Server-Sent Events (EventSource), Web Workers, and Progress Events. In theory Last Call is the final check before a specification is more or less done. In practice it can still take over seven years. Irrespective of theory and practice, the sooner you submit your comments on a specification the better. Specifications are implemented, then become used, and at some point become immutable in areas you might be displeased with. You want to beat that.
A restrictive datalist, inline lists, cross-origin databases, and drawWindow()
Over on the WHATWG mailing list Markus Ernst brought up restricting the color palette for the <input type=color> control. Using the datalist element you can suggest a palette, but you cannot restrict it any way. This discussion quickly generalized to all new controls as they have a similar limitation. Jonas Sicking pointed out that providing a good user interface might be difficult. I said that we should probably wait a bit until the existing functionality is implemented by most user agents before adding yet more features.
Jukka K. Korpela re-raised the question many have had since they learned HTML: What about paragraphs that contain lists? James Graham pointed out that the section element cannot be used. Markus Ernst suggested we introduce a new inline list element. Probably best to just not worry too much about it and carry on as we have done for the past decade.
Apart from markup, there were a few API requests too. Brett Zamir wants cross-origin databases. Erik Möller (with Opera) asked about making Mozilla’s <canvas>.drawWindow() part of the web platform.
Layout tables
The W3C HTML Working Group decided that when you put role=presentation on a table element it can be used (in a conforming way) for presentational purposes.
Posted in Weekly Review | 9 Comments »
There is now a new release of the Validator.nu HTML Parser. The new release contains files that were missing from the previous release package by accident. It also contains one tree builder correctness fix and one error reporting improvement.
Posted in Syntax | Comments Off on Validator.nu HTML Parser Version 1.3.1 Released
Thanks to Ben Schwarz the WHATWG now hosts an edition of the HTML standard specifically tailored for web developers: HTML5 for Web Developers. It is identical to the HTML standard, but information specific to implementors and not relevant to web developers has been removed. It also uses some CSS to make it look pretty. We hope you like it!
Posted in Tutorials | 5 Comments »
Much sleep has not been had, so if you read something silly, it might just be me. There’s good news too, Shelley Powers volunteered to start writing the WHATWG Weekly starting March 21. Her main interest is HTML, so you might need to pester her on twitter (@shelleypowers) or email ([email protected]) to get other things covered.
Web Notifications
Robert O'Callahan once wrote a great post on The Essence Of Web Applications. Nonetheless, there are some features desktop applications have that would be quite useful in the web application space. The Web Notifications work is one part of that puzzle, bringing an API to the web to show simple application status messages to the user. This way e.g. Yahoo! Mail can notify you of incoming email even when your browser is running in the background or Yahoo! Mail is not the active tab.
Purging Link Relationships
Per a decision of the W3C HTML WG the up, last, index, first, and their synonym link relationships (values for the rel attribute) have been dropped. Since archives was similar to index that has been removed too for consistency. These relationships were never that useful to begin with so I suppose it is nice that authors no longer have to worry about them. I.e. either worry whether to add them at all or whether they would be appropriate in a certain situation.
Shorts
- Philip Jägenstedt made several small enhancements to the HTML5 Tracker, including better icons for the browsers. Lets us know what you think!
- Tab Atkins would like to reuse
<canvas> for images with structured fallback.
- Dave Kok put forward a detailed proposal for Session Management.
- David Bruant brought a discussion on the interaction of multiple global objects when using ECMAScript to the attention of the WHATWG, which happens to be standardizing some of that.
- Christoph Päper asked whether we should have a new native control for (value, unit) tuples.
- Edward Gerhold joined the quest (pretty sure there is one) to improve the application cache feature.
- Lawrence Rosen presented a license proposal to the HTML WG. Unlike the WHATWG the W3C has a restrictive license for its specifications, but it is considering changing that.
- Since the work on a new cookies specification is practically finished (waiting for the IETF to assign it a RFC number) Adam Barth put forward Origin Cookies. A proposal to solve some of the problems with cookies as they are today.
- Henri Sivonen found joy where most would find despair.
Posted in Weekly Review | 4 Comments »