Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)

2011-07-26 Thread Arthur Barstow
On 7/25/11 5:05 PM, ext Aryeh Gregor wrote: From the discussion here, it sounds like there are problems with WebSockets compression as currently defined. Yes, this is what I have concluded too (and if we are wrong, I would appreciate it if someone on the hybi list would please clarify).

CfC: publish Last Call WD of Progress Events; deadline August 2

2011-07-26 Thread Arthur Barstow
The pre-LC comment period for Progress Events resulted in no comments [1]. As such, Anne proposes a new LC be published and this is a CfC to do so: http://dev.w3.org/2006/webapi/progress/ This CfC satisfies the group's requirement to record the group's decision to request advancement for

Re: Frame embedding: One problem, three possible specs?

2011-07-26 Thread Tobias Gondrom
Hi all, sorry for the late answer, a flu and some other duties kept me from answering so far. I agree with Thomas, Adam and David, so please go ahead with the webappsecwg charter. The current plan for #3 is to be adopted in websec (as http headers should be done in IETF) and proceed

Re: CfC: publish Last Call WD of Progress Events; deadline August 2

2011-07-26 Thread Charles McCathieNevile
On Tue, 26 Jul 2011 16:12:40 +0200, Arthur Barstow art.bars...@nokia.com wrote: The pre-LC comment period for Progress Events resulted in no comments [1]. As such, Anne proposes a new LC be published and this is a CfC to do so: Opera supports publishing. cheers -- Charles 'chaals'

Re: More use-cases for mutation events replacement

2011-07-26 Thread Aryeh Gregor
On Mon, Jul 25, 2011 at 11:12 PM, Sean Hogan shogu...@westnet.com.au wrote: I assume you are referring to the NodeWatch proposal from Microsoft. 1st draft:    http://www.w3.org/2008/webapps/wiki/Selector-based_Mutation_Events 2nd draft:  

[Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain

2011-07-26 Thread bugzilla
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13373 Summary: Privacy: Limit SharedWorker connections to same top-level domain Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW

Re: [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain

2011-07-26 Thread Thomas Roessler
Travis, I suspect you mean second-level domain (microsoft.com, w3.org) instead of top-level domain (.com, .net, .org). Further, I'll observe that consistency with other, similar security policies would be valuable instead of introducing yet another privacy policy. Adding public-web-security

Re: [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain

2011-07-26 Thread Anne van Kesteren
On Tue, 26 Jul 2011 12:25:16 -0700, Thomas Roessler t...@w3.org wrote: I suspect you mean second-level domain (microsoft.com, w3.org) instead of top-level domain (.com, .net, .org). Top-level browsing context seems more likely. -- Anne van Kesteren http://annevankesteren.nl/

Re: [Bug 13373] New: Privacy: Limit SharedWorker connections to same top-level domain

2011-07-26 Thread Thomas Roessler
Gack, that's what I get for reading the subject and first paragraph. -- Thomas Roessler, W3C t...@w3.org (@roessler) On Jul 26, 2011, at 15:29 , Anne van Kesteren wrote: On Tue, 26 Jul 2011 12:25:16 -0700, Thomas Roessler t...@w3.org wrote: I suspect you mean second-level domain

RE: [IndexedDB] Client API state after calling deleteIndex and deleteObjectStore

2011-07-26 Thread Eliot Graff
Jonas, Would it be good enough to document the above examples under the deleteIndex and deleteObjectStore APIs, respectively? Or do you believe we should add some text to the API descriptions to make this more clear?  In addition, I believe we should expand the explanation for when