[Bug 15898] New: XTech 2000 (http://www.gca.org/attend/2000_conferences/xtech_2000/) is around the corner, and members of W3C team will be there, including Eric Prud'hommeaux, Michael Sperberg-McQu

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15898 Summary: XTech 2000 (http://www.gca.org/attend/2000_conferences/xtech_2000 /) is around the corner, and members of W3C team will be there, including Eric Prud'hommeaux,

[Bug 15898] XTech 2000 (http://www.gca.org/attend/2000_conferences/xtech_2000/) is around the corner, and members of W3C team will be there, including Eric Prud'hommeaux, Michael Sperberg-McQueen,

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15898 Ms2ger ms2...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

Re: Encoding Spec and Encoding for readAsText

On Thu, 26 Jan 2012 22:57:35 +0100, Arun Ranganathan aranganat...@mozilla.com wrote: Few quick questions: 1. Can you review: http://dev.w3.org/2006/webapi/FileAPI/#encoding-determination I think per https://www.w3.org/Bugs/Public/show_bug.cgi?id=15359 we want to let the BOM checking

Re: StreamBuilder threshold

On Thu, 26 Jan 2012 19:05:05 +0100, Feras Moussa fer...@microsoft.com wrote: When designing the StreamBuilder API, we looked at it as a more primitive API which other abstractions (such as multiple consumers) can be built upon. We should not have a StreamBuilder API. We should have a

[Bug 15901] New: Create Participate: box at top of the specification

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15901 Summary: Create Participate: box at top of the specification Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal

[Bug 15902] New: DOMParser created documents should use about:blank as URL

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15902 Summary: DOMParser created documents should use about:blank as URL Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW

Re: StreamBuilder threshold

On 01/26/2012 07:05 PM, Feras Moussa wrote: Can you please clarify what scenario you are looking at regarding multiple consumers? When designing the StreamBuilder API, we looked at it as a more primitive API which other abstractions (such as multiple consumers) can be built upon. (Please

data and blob URLs in HTTP context

Currently Opera and Firefox seem to support data URLs within the context of XMLHttpRequest. Status is 0, status text is the empty string, there are no response headers, and response-related attributes work as expected. This is different from blob URLs in that blob URLs do have a response

Re: [XHR] Invoking open() from event listeners

On Wed, 18 Jan 2012 00:56:12 +0100, Eric U er...@google.com wrote: On Tue, Dec 20, 2011 at 9:24 AM, Anne van Kesteren ann...@opera.com wrote: open() does terminate both abort() and send() (the way it does so is not very clear), but maybe it would be clearer if invoking open() set some kind

Re: data and blob URLs in HTTP context

On 2012-02-05 15:56, Anne van Kesteren wrote: Currently Opera and Firefox seem to support data URLs within the context of XMLHttpRequest. Status is 0, status text is the empty string, there are no response headers, and response-related attributes work as expected. ... No Content-Type response

[FileAPI] No streaming semantics?

I've been playing around with the FileAPI in both Chrome and Firefox. The API presented works very well for small files consistent with perhaps circa 1990s web usage. Previewing small images (~50K), reading and processing small files (a few MB) have been cases where uniformly strong results are

Re: [FileAPI] No streaming semantics?

Use slice; webkitSlice. They just it themselves put together on the media Apis as well. So that's cool. There's an append stream semantic. -Charles On Feb 5, 2012, at 5:18 PM, Justin Summerlin jmer...@jmerlin.net wrote: I've been playing around with the FileAPI in both Chrome and Firefox.