W3C

I can’t believe none of us knew DOM2 This is how a tweet from @SubtleGradient, re-tweeted by @jdalton, has been able to steal my rest tonight … and this post is the consequence … What’s new in a nutshell There is a W3C Recommendation about addEventListener behavior, which clearly specify the second argument as an Read the rest…

A draft of the W3C Capture API has been put out there by the editors. The Capture API defines a JavaScript API for accessing the microphone and camera of a hosting device. When I look at the API for getting pictures from a camera I got a little scared at the amount of DOM fluff Read the rest…

The king of browser compatibility tables, ppk, recently posted an introduction to W3C Widgets: The time has come to talk about the W3C Widgets part of my job. Exactly what is a widget, how do you create one, why would you want to, and which systems support them? Personally I firmly believe that widgets are Read the rest…

On Friday, the SVG and CSS working groups of the W3C published the first working drafts of Apple’s proposed graphics and styling extensions: The CSS and SVG Working Groups delivered today five new specifications for public review, aimed at enabling more compelling content creation with open Web technologies. The five drafts are: SVG Transforms 1.0, Read the rest…

I’ve long believed that the Ajax/JavaScript communities and the W3C should communicate more and have more awareness of what both camps are doing so we can work together better and get things done. In light of this, here are some updates on a special W3C meeting that is taking place right now. From October 20th Read the rest…

Lack of support for XHTML is a fact of life on the web in 2008. Prior to the 3.0 series of Firefox the XHTML processor in Gecko was so poor that Mozilla’s own engineers recommended against it[27]; no version of Internet Explorer up to, and including, IE 8 support XHTML at all, and a number Read the rest…

Sir Tim Berners-Lee announced a new World Wide Web Foundation: To encourage those communities to come together, I am pleased to unveil tonight a new Foundation, the World Wide Web Foundation. The mission of the Foundation is: to advance One Web that is free and open, to expand the Web’s capability and robustness, and to Read the rest…

Bert Bos, a W3C fellow, thinks that CSS variables are to be considered harmful: Adding any form of macros or additional scopes and indirections, including symbolic constants, is not just redundant, but changes CSS in ways that make it unsuitable for its intended audience. Given that there is currently no alternative to CSS, these things Read the rest…

The W3C Web API group has a new working draft, Progress Events 1.0. This document describes event types that can be used for monitoring the progress of an operation. It is primarily intended for contexts such as data transfer operations specified by XMLHTTPRequest, or Media Access Events. This API standardizes progress events that seem to Read the rest…

The W3C has publicly invited browser vendors, application developers, and content designers to help design the next version of HTML by participating in the new W3C HTML Working Group. Ian Hickson commented over at the WHATWG: Surprisingly, the W3C never actually contacted the WHATWG during the chartering process. However, the WHATWG model has clearly had Read the rest…

Marcos Caceres is the editor of the Widgets 1.0 Requirements from the W3C (mentioned previously). Following the publication of the W3C Widgets 1.0 standard the W3C’s WAF working group has republished a requirements document for Widgets 1.0. The new document attempts to embrace the movement towards making widget engines available on mobile devices and the Read the rest…

Arve Bersvendsen of Opera let us know about the new working draft from the W3C: Widgets 1.0. Everyone and their mother have created their own widget specifications, and now as a developer you need to make choices. Do you want it to work on Dashboard? Google? MSN? Yahoo!? If the big hitters supported this widget Read the rest…