The WHATWG Blog

Please leave your sense of logic at the door, thanks!

Archive for April, 2011

WHATWG Weekly: Week of April 25

Monday, April 25th, 2011

Dimitri Glazkov asked a question about pseudo classes for state changes with the audio and video elements so that designers/developers could style the devices without having to listen for events.

Discussion continued on a question that Justin Karneges had about microformats, microdata, and custom data attributes. A point was made in the discussion about not using custom data attributes (data-*) for document interchange, as these are for in-page development, only.

The HTML5 editor, Ian Hickson, made a change to the documentation for video and audio, noting that both elements will accept audio and video content. He's also done more tweaking related to the Media Controller.

In the W3C, RDFa API and RDFa 1.1 Primer Drafts were updated and Web Applications WG published four drafts: WebSocket API, Indexed Database API, File API: Writer, and File API: Directories and System.

The CSS WG published a Call for Review for the CSS 2.1 Proposed Recommendation. The group also published an update of the CSS3 Speech draft.

Dominique Hazael-Massieux posted a note in the HTML WG that the Device APIs and Policy WG would like feedback on a new approach for HTML Media Capture.

The W3C co-chairs posted a possible survey for HTML5 licenses, seeking feedback from the HTML WG.

The W3C co-chairs also published three decisions related to two issues: Issue 31 and Issue 80. Both of these issues have to do with alternative text.

The first decision was related to the requirements section for alternative image text. The co-chairs decided on the change proposal to keep the requirements section in the HTML5 document.

The second decision was about the text used in the img element section of the HTML spec. The co-chairs decided on the following text:

An img element represents an image.

The image given by the src attribute is the embedded content; the value of the alt attribute provides equivalent content for those who cannot process images or who have image loading disabled.

The last decision had to do with alternative text validation. The co-chairs decided in favor of a morphing between a couple of change proposals, resulting in the following validation criteria:

I'm going to go out on a limb here and offer my personal opinion that it's simpler just to remember to provide alt text.

In the news this week were discussions about Apple and Google auto-logging location history on the iPhone and Android. Appropriately enough, Philippe Le Hégaret posted his position paper for an upcoming presentation at Web Tracking & User Privacy.

Posted in Weekly Review | No Comments »

WHATWG Weekly: WHATWG goes Native!

Monday, April 18th, 2011

OK, everyone: time to form a drum circle.

Kyle Huey proposed a new method, toBlob, on Canvas. This method would have the same functionality as Mozilla's non-standard mozGetAsFile, and would retrieve the Canvas contents in such a way that they can be stored in a file.

Jukka Korpela brought up the Chrome support of commas in numbers and the concept of localization and floating point number representation. Jukka also asked about ways of expressing physical quantities.

The HTML5 witch doctor, Ian Hickson, has been applying more HTML WG decisions, and doing some event tweaking. If you ever want to follow what's happening in the land of HTML edits, check out the WHATWG Twitter thread, which documents each new change.

The W3C HTML WG tribe has had an extremely busy time last week. In fact, the email list is becoming a bit hard to follow. However, machete in hand, I dove in.

I had missed pointing out a very long thread that Danny Ayers triggered on systematic access to media/plugin metadata, and that has generated thoughtful and interesting replies.

The co-chairs published a decision on Issue 131 on adding a caret location API to Canvas. The co-chairs decided in favor of the proposal to modify the existing Canvas API caret and focus ring but with a couple of exceptions.

The co-chairs also decided on Issue 155 on table border, ruling in favor of the proposal to add border="1" on HTML tables.

As is typical with the HTML WG, both decisions were accepted graciously by the body—leading the co-chairs to marvel, yet again, at how wonderfully easy and uncomplicated their WG tasks are.

Elsewhere in the W3C, the Clipboard API and Events Working draft was published this week, as was the CSS Text Level 3 draft, and the Messenging API draft. These join with the First Draft of the Platform Accessibility APIs Implementation Guide, making this a very productive week among the working groups.

In other news, Bruce Lawson was kind enough to pull together a list of HTML5ish people on Twitter. Let's raise our coconut drinks in thanks!

As usual, if I missed something or made an error, please provide a note (including links, if applicable) in comments and I'll update this post.

A hui hou kakou!

Posted in Weekly Review | No Comments »

WHATWG Weekly

Tuesday, April 12th, 2011

This week was more continuation of previous discussions, though there are changes and decisions of note.

A new discussion broke out about making checkboxes readonly.

Discussion still continues on styling details, in addition to other questions on the elements' implementation, including an implementation proposal.

Ian Hickson wrote about changes he made to the MediaController, as noted in detail in the HTML5 change tracker.

Ian also applied changes based on previous W3C HTML WG decisions, including the decision on modifying the ARIA mapping table. This change, though, generated some disagreement, and the change was reverted.

Over in the W3C there are several decisions of note.

The first is related to Issue-32 on table summary. The co-chairs agreed with the proposal to continue obsoleting <table> @summary.

The co-chairs also made a decision on Issue 27 on rel ownership. The decision was in favor of the change proposal to defer to the Microformats community for maintaining rel values.

Just when you thought it was safe to get back into the water...the <u> element is back. Cue Jaws music.

The decision about Issue 147, playbackrate undefined is in favor of the proposal to consider playback rate a hardware limitation and not to expose it in an API.

Today, the co-chairs posted a decision on Issue 131 caret-location-api. The proposal adopted modifies the existing Canvas 2D API caret and focus ring support to drive screen magnification, with a couple of caveats, detailed in the decision. Concerns have been expressed about the caveats, primarily because previous decisions have focused mainly on choosing between proposals, not choosing a proposal and modifying it. The only other decision where this has happened is the decision related to the ARIA mapping.

In other news:

Robin Berjon announced the Call for Consensus for a FPWD of the new Calendar API. It joins with the publication of the 8 drafts from the HTML WG, including HTML5.

The Grid Layout First Working Draft was also published, as well as the FPWD for the Vocabularies for EmotionML, and the Last Call for the Emotion Markup Language (EmotionML).

As always, if I missed something or made a mistake, send me an email or tweet, or leave a comment.

update Forgot this one: Sam Ruby put out a call for brainstorming for the next version of HTML. A wiki has been set up, and I believe all parties are welcome to participate—you don't have to be a member of HTML WG.

Posted in Weekly Review | 1 Comment »

WHATWG Weekly: the rubber hits the road

Monday, April 4th, 2011

The HTML WG is heading towards Last Call, and the activity is increasing, both in the W3C and in the WHATWG email lists.

Opera is working on its implementation of the new HTML5 <details> and had several implementation questions. The issue is that the implementors need to provide a way for users to style the element, and whatever is used should be consistent among the implementors.

In the discussion, the concept of XBL shadow trees arose. If you're not familiar with XBL, it is, or was, the XML Binding Language—a Mozilla creation using XML to describe the behavior and styling of XUL widgets and XML elements. There is an effort to standardize the concept in the W3C with XBL2. Currently, the spec is in Candidate Recommendation status, with the most recent activity being a discussion about moving the spec forward that happened in March.

The issue of what happens with the DOM range when a page mutates spawned a lively discussion between Aryeh Gregor (Google) and Boris Zbarsky (Mozilla). The discussion looks to continue from a response posted by Ryosuke Miya (WebKit).

In an email that revives a dormant discussion related to media elements statistics, Silvia Pfeiffer points to a wiki page on Video Metrics. These wiki pages that pull all the disparate pieces together—not only from different implementors but discussed in different email lists and groups—are essential for ensuring cooperation, cohesion, and transparency. If anyone has another page that should be featured in a Weekly, drop a note in comments, send me an email, or tweet me at @shelleypowers, and I'll find a way to incorporate a reference to the page.

In the meantime, Chris Pearce has added support for Mozilla-specific decoding/painting statistics in the Firefox trunk for expected release with Firefox 5.

The discussion on @longdesc continues. In a comment to a weblog post, Bruce Lawson questioned whether the <details> element can't be used in place of longdesc. He continued the discussion with a question on the feasibility of this substitute to the WHATWG email list.

Speaking of @longdesc, I wanted to take this opportunity to point out the extensive collection of @longdesc use cases that Laura Carlson has been heroically gathering. There was also a wiki page gathering together all of the discussions on longdesc, but I believe it was locked down due to contentious activity. If there's a new wiki page somewhere, make a note in comments or send me the link and I'll update this page.

Alexandre Morgaut initiated a fascinating discussion on a browser implementation detail that many JavaScript developers may not be aware of.

All the major browsers add any HTML element that has an @id attribute to the global namespace. Chrome, Opera, IE, and Safari do so automatically, and Firefox does so in quirks mode. What this means is that if you have an element with an @id of "testing", you can access that element by the @id value name directly in code—without having to use getElementById first to get the element reference.

This behavior isn't part of HTML4, but it is part of HTML5, as noted in a bug filed on this behavior.

I linked to this discussion to a), make you aware of the functionality and the ongoing discussion and bug, and b) to strongly suggest that you never make use of this functionality in your applications. Read the WHATWG email thread for more on why this browser behavior is potentially harmful.

On the W3C side, I'll defer details of actions to the inestimable Karl Dubost, and his excellent Open Web Platform Weekly reports, but I did want to point out some decisions and email discussions of interest.

The co-chairs made a decision on Issue 120 related to RDFa prefixes. They decided in favor of continued support for prefixes, with recommendations to clarify their use and ensure people are aware they are optional.

The co-chairs also made a decision about Issue 122, choosing the change proposal that recommended removing the section describing alt text for decorative images out of HTML5 in favor of a link to the WCAG 2.0 guidelines.

In regards to Issue 142 on Poster Alt, the co-chairs decided in favor of the no Poster Alt change proposal.

Later in the week, the co-chairs declared that Issue 145 on codecs-vs-octet, was closed by amicable resolution. Amicable resolution...we should all take a moment to pause and savor this rare resolution state.

OK, moment's over.

The co-chairs continued with the rollout of decisions with one for Issue 129 on ARIA mapping, and whether @role can override rather than define element semantics. The chairs decided in favor of the change proposal to allow @role to change some role mappings, with some specific exceptions outlined in the decision.

I believe this is a first: the chairs also re-opened Issue 30 as a Last Call Issue. In case you're unfamiliar with Issue 30, it is about @longdesc.

Two decisions led to formal objections: Issue 120 on RDFa prefixes, and Issue 142 on Poster Alt. All formal objections are recorded and maintained in one specific page.

The Canvas API accessibility folks have asked for feedback on improved hit testing for canvas accessibility. The request is focused specifically to the canvas development community. I believe you can respond to the public-canvas-api email list even if you aren't a member. If not, you could probably post emails directly to Richard Schwerdtfeger.

An announcement was made on the new Task Force for Home Networking inside the Web and TV IG.

There's also be considerable discussion on incorporating support for PUT and DELETE in forms, including a re-opened bug on the issue.

The discussion still continues on the license for HTML5.

Whew! I'm exhausted just writing all of this stuff. The activity should continue to be high as the W3C HTML WG moves towards Last Call, and as the rubber hits the road with HTML5.

Posted in Weekly Review | 2 Comments »