Re: [selectors-api] Reference to obsolete ECMAScript Language spec version

On 2012-10-29 14:38, Norbert Lindenberg wrote: The current drafts of the Selectors API specifications [1, 2, 3] refer to the third edition of the ECMAScript Language Specification, The references have been updated. Thank you. -- Lachlan Hunt http://lachy.id.au/ http://www.opera.com/

[Bug 19969] New: clarify some user name/password and setRequestHeader() Authorize header issues

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19969 Priority: P2 Bug ID: 19969 CC: m...@w3.org, public-webapps@w3.org Assignee: ann...@annevk.nl Summary: clarify some user name/password and setRequestHeader()

[Bug 19969] clarify some user name/password and setRequestHeader() Authorize header issues

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19969 Anne ann...@annevk.nl changed: What|Removed |Added Status|NEW |RESOLVED

[selectors-api] Editoral Changes and Test Suite Progress

Hi, The test suite has been reviewed by a colleague at Opera, which resulted in a few minor corrections. No corrections required any changes to the implementation report. However, it did result in a few editorial changes to Selectors API spec. These changes should not affect conformance of any

[css-regions] Fwd: Scheduling multiple types of end-of-(micro)task work

Hello, CCing www-style and BCCing public-webapps I have given some thoughts to the regionlayoutupdate event - what condition triggers it and when it should be dispatched. For the current version of the spec I think it is sufficient to consider the event is triggered only by changes of the

[css3-conditional] Last Call Working Draft for @supports and CSS.supports()

Hello WebApps, The CSSWG expects to publish a Last Call Working Draft of CSS Conditional Rules Level 3 within the next week. We would appreciate your review, particularly of the API parts: http://dev.w3.org/csswg/css3-conditional/#apis The LCWD will likely appear here:

Call for Consensus: CORS to Candidate Recommendation

WebApps and WebAppSec WG members, (and copied security interest groups who we invite to provide comments) Following discussion at TPAC, I've resolved outstanding changes in the security considerations section agreed to by WebAppSec as well as differences between the W3C and WHATWG versions of

FileSystem compromise spec

As discussed at TPAC, there's little support for the current FileSystem API, but some support for a new API, and I promised to put forth a compromise proposal. In order to do that, I'd like to hear 1) what kinds of changes would make it more popular; 2) who I'm trying to convince. There are a

[PE] Start working on Progress Events

Hi all, I came to start working on Progress Events spec to move it towards REC. Because the spec is already a CR, I am planning to focus on satisfying the exit criteria to ship it. Please see inline comments and questions. Jungkee From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: