Re: Use Cases for Connectionless Push support in Webapps recharter

2012-01-13 Thread Arthur Barstow
Hi All, With respect to the charter, the SSE snippet currently says: [[ Server-Sent Events - An API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events. The API is designed such that it can be extended to work with other push notification

RE: to add Speech API to Charter; deadline January 19

2012-01-13 Thread Deborah Dahl
Olli has a good point that it makes sense to implement the SpeechAPI in pieces. That doesn't mean that the WebApps WG only has to look at one proposal in deciding how to proceed with the work. Another option would be to start off the Speech API work in the Web Apps group with both proposals (the

RE: to add Speech API to Charter; deadline January 19

2012-01-13 Thread Young, Milan
That's exactly the right question to ask. Please take a look at: http://www.w3.org/2005/Incubator/htmlspeech/XGR-htmlspeech-20111206/#requirements I am also in support of Olli's statement that we may not be able to spec/implement the complete XG recommendation in one pass. But decisions made

Re: Selection of a document that doesn't have a window

2012-01-13 Thread Boris Zbarsky
On 1/13/12 2:37 AM, Simon Pieters wrote: HTML uses this concept in lots of places, e.g. http://www.whatwg.org/specs/web-apps/current-work/#cookie-free-document-object A Document that has no browsing context. Ah, that's better than using defaultView (because behavior for defaultView on

RE: to add Speech API to Charter; deadline January 19

2012-01-13 Thread Deborah Dahl
I agree that getting good enough out there sooner is an excellent goal, although in practice there's always a lot of room for disagreement about what's good enough. There isn't a draft priority list now, although the XG final report does include prioritized requirements [1]. However, the

Re: Selection of a document that doesn't have a window

2012-01-13 Thread Boris Zbarsky
On 1/13/12 12:18 PM, Aryeh Gregor wrote: Actually, defaultView is defined to return the Document's browsing context's WindowProxy object, if it has one, and null otherwise. Hmm. I guess the spec doesn't really define what happens to the association between a document and its browsing context

Re: File modification

2012-01-13 Thread Arun Ranganathan
On 1/12/12 12:53 PM, Arun Ranganathan wrote: Oh I'm glad to see this one! Is it Blob and File that can be put into IDB? How do I create a new File (with a name field) from a Blob? Charles: see the thread on making Blobs constructable -- follow

RE: to add Speech API to Charter; deadline January 19

2012-01-13 Thread Deborah Dahl
How prioritization works in practice depends on how a specific Working Group decides to organize its work, but generally, the W3C is very consensus-oriented and tries to make sure that all opinions are respected. -Original Message- From: Dave Bernard

Re: Selection of a document that doesn't have a window

2012-01-13 Thread Aryeh Gregor
On Fri, Jan 13, 2012 at 12:34 PM, Boris Zbarsky bzbar...@mit.edu wrote: I would prefer a definition that doesn't involve defaultView, actually.  I don't expect browsers to converge defaultView behavior any time in the near or medium future, so the testability would be illusory: tests would just

Re: File modification

2012-01-13 Thread Charles Pritchard
On 1/13/12 11:13 AM, Arun Ranganathan wrote: On 1/12/12 12:53 PM, Arun Ranganathan wrote: Oh I'm glad to see this one! Is it Blob and File that can be put into IDB? How do I create a new File (with a name field) from a Blob? Charles: see the thread on making

Re: File modification

2012-01-13 Thread Glenn Maynard
That would be bad; it would require null checks that people would forget to perform due to the rarity of the condition. Instead, it should return a File that fails when read attempts are made. (Of course, those errors are also rare, but it's at least not adding a *new* rare case.) On Jan 13,

Re: Use Cases for Connectionless Push support in Webapps recharter

2012-01-13 Thread Ian Hickson
On Fri, 13 Jan 2012, Arthur Barstow wrote: Hixie - what are your thoughts on these UCs and how they would be spec'ed? For example, would they be in a different spec, an L.next type spec? Well there's two parts to it: the protocol, and the API. If there's an existing protocol for this and

[Bug 15554] New: Hi, The article is very good. Also user can view. HTML5 Web Workers http://www.totaldotnet.com/Article/ShowArticle145_HTML5WebWorker.aspx

2012-01-13 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15554 Summary: Hi, The article is very good. Also user can view. HTML5 Web Workers http://www.totaldotnet.com/Article/ShowArticle145_HTML 5WebWorker.aspx Product: