Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Jonas Sicking
On Tue, Mar 27, 2012 at 4:59 PM, Glenn Maynard gl...@zewt.org wrote: I didn't realize this was actually added to the spec: The optional options dictionary argument contains a key, oneTimeOnly that defaults to false. If set to true, then the first time the Blob URI is dereferenced, user agents

Re: [xhr] statusText is underdefined

2012-03-28 Thread Julian Reschke
On 2012-03-28 00:35, Glenn Adams wrote: On Tue, Mar 27, 2012 at 4:17 PM, Boris Zbarsky bzbar...@mit.edu mailto:bzbar...@mit.edu wrote: On 3/27/12 2:46 PM, Glenn Adams wrote: Is this really a problem? Yes. We've run into bug reports in the past of sites sending some

Re: [xhr] statusText is underdefined

2012-03-28 Thread Anne van Kesteren
On Tue, 27 Mar 2012 22:23:15 +0100, Boris Zbarsky bzbar...@mit.edu wrote: But the HTTP status text is a sequence of bytes, while the return value for statusText is a DOMString. The conversion from one to the other needs to be defined. Would using

Re: [xhr] statusText is underdefined

2012-03-28 Thread Glenn Adams
On Wed, Mar 28, 2012 at 1:33 AM, Julian Reschke julian.resc...@gmx.dewrote: On 2012-03-28 00:35, Glenn Adams wrote: On Tue, Mar 27, 2012 at 4:17 PM, Boris Zbarsky bzbar...@mit.edu mailto:bzbar...@mit.edu wrote: On 3/27/12 2:46 PM, Glenn Adams wrote: Is this really a problem?

Re: [xhr] statusText is underdefined

2012-03-28 Thread Glenn Adams
On Wed, Mar 28, 2012 at 2:33 AM, Anne van Kesteren ann...@opera.com wrote: On Tue, 27 Mar 2012 22:23:15 +0100, Boris Zbarsky bzbar...@mit.edu wrote: But the HTTP status text is a sequence of bytes, while the return value for statusText is a DOMString. The conversion from one to the other

Re: [xhr] statusText is underdefined

2012-03-28 Thread Boris Zbarsky
On 3/28/12 1:33 AM, Anne van Kesteren wrote: On Tue, 27 Mar 2012 22:23:15 +0100, Boris Zbarsky bzbar...@mit.edu wrote: But the HTTP status text is a sequence of bytes, while the return value for statusText is a DOMString. The conversion from one to the other needs to be defined. Would using

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Anne van Kesteren
On Wed, 28 Mar 2012 08:19:55 +0100, Jonas Sicking jo...@sicking.cc wrote: I think we need to define that APIs like xhr.open(...) and the img.src setter synchronously dereference the URL before returning. What does dereferencing mean exactly? xhr.open() resolves URLs currently and then

Re: [xhr] statusText is underdefined

2012-03-28 Thread Anne van Kesteren
On Wed, 28 Mar 2012 08:53:30 +0100, Boris Zbarsky bzbar...@mit.edu wrote: On 3/28/12 1:33 AM, Anne van Kesteren wrote: Would using http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#inflate-a-byte-sequence-into-a-domstring be sufficient I don't know. I believe Gecko's behavior is to treat

Re: [xhr] statusText is underdefined

2012-03-28 Thread Anne van Kesteren
On Wed, 28 Mar 2012 08:52:25 +0100, Glenn Adams gl...@skynav.com wrote: Well, that would define a specific, definite algorithm. Never mind that it would introduce random bytes into DOMStrings that may or may not have anything to do with character data. That's false. Using iso-8859-1 is

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Jonas Sicking
On Wed, Mar 28, 2012 at 2:17 AM, Anne van Kesteren ann...@opera.com wrote: On Wed, 28 Mar 2012 08:19:55 +0100, Jonas Sicking jo...@sicking.cc wrote: I think we need to define that APIs like xhr.open(...) and the img.src setter synchronously dereference the URL before returning. What does

Re: [xhr] statusText is underdefined

2012-03-28 Thread Boris Zbarsky
On 3/28/12 2:48 AM, Anne van Kesteren wrote: Wow, inflating is what the specification currently requires for header fields, for what it's worth. Yes, Gecko has different behavior here for the status text and for header fields. I have no idea whether that's on purpose; I suspect it's mostly

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Anne van Kesteren
On Wed, 28 Mar 2012 10:51:59 +0200, Jonas Sicking jo...@sicking.cc wrote: On Wed, Mar 28, 2012 at 2:17 AM, Anne van Kesteren ann...@opera.com wrote: What does dereferencing mean exactly? It means initiating the load or some such. Implementation-wise for blob URLs it would likely mean going

[Bug 16557] New: Figure out bytes to code point mapping for statusText

2012-03-28 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16557 Summary: Figure out bytes to code point mapping for statusText Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal

Re: [xhr] statusText is underdefined

2012-03-28 Thread Glenn Adams
On Wed, Mar 28, 2012 at 3:50 AM, Anne van Kesteren ann...@opera.com wrote: On Wed, 28 Mar 2012 08:52:25 +0100, Glenn Adams gl...@skynav.com wrote: Well, that would define a specific, definite algorithm. Never mind that it would introduce random bytes into DOMStrings that may or may not have

Re: [xhr] statusText is underdefined

2012-03-28 Thread Glenn Adams
On Wed, Mar 28, 2012 at 4:48 AM, Julian Reschke julian.resc...@gmx.dewrote: On 2012-03-28 09:48, Glenn Adams wrote: I'm not sure what you mean by citing ISO-8859-1 and UTF-8 in the same context. Please elaborate. If you have UTF-8 on the wire and the client handles it as ISO-8859-1, the

Re: [xhr] statusText is underdefined

2012-03-28 Thread Boris Zbarsky
On 3/28/12 10:42 AM, Glenn Adams wrote: Any use of DOMString to serve as a holder for arbitrary binary data (including inflating from UTF-8 bytes into 16-bit code units), should be specifically marked as such. For what it's worth, I would be reasonably happy if we had a non-DOMString IDL type

Re: [xhr] statusText is underdefined

2012-03-28 Thread Anne van Kesteren
On Wed, 28 Mar 2012 20:10:53 +0200, Boris Zbarsky bzbar...@mit.edu wrote: On 3/28/12 10:42 AM, Glenn Adams wrote: Any use of DOMString to serve as a holder for arbitrary binary data (including inflating from UTF-8 bytes into 16-bit code units), should be specifically marked as such. For what

Re: [xhr] statusText is underdefined

2012-03-28 Thread Glenn Adams
On Tue, Mar 27, 2012 at 3:23 PM, Boris Zbarsky bzbar...@mit.edu wrote: The spec says: Return the HTTP status text. But the HTTP status text is a sequence of bytes, while the return value for statusText is a DOMString. The conversion from one to the other needs to be defined. If I may

Re: [xhr] statusText is underdefined

2012-03-28 Thread Cameron McCormack
Boris Zbarsky: For what it's worth, I would be reasonably happy if we had a non-DOMString IDL type to indicate raw byte sequence strings, with WebIDL defining byte-inflation as the conversion from such things to JS strings... Anne van Kesteren: That's an interesting idea. We could also use

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Glenn Maynard
On Wed, Mar 28, 2012 at 2:19 AM, Jonas Sicking jo...@sicking.cc wrote: All of this will definitely be a lot of work to specify (and possibly implement). But I don't see any other options to get interoperability with Blobs and blob-URLs. It's definitely not a problem restricted to oneTimeOnly.

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Glenn Maynard
Here's another proposal, which is an iteration of the previous. It's based on the microtask concept, which is creeping up here and there but hasn't yet been properly defined. The idea is that microtasks can be queued (call it queue a microtask), and the microtask queue is executed by the event

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Jonas Sicking
On Wed, Mar 28, 2012 at 4:36 PM, Glenn Maynard gl...@zewt.org wrote: Here's another proposal, which is an iteration of the previous.  It's based on the microtask concept, which is creeping up here and there but hasn't yet been properly defined.  The idea is that microtasks can be queued (call

Re: File API oneTimeOnly is too poorly defined

2012-03-28 Thread Glenn Maynard
On Wed, Mar 28, 2012 at 7:49 PM, Jonas Sicking jo...@sicking.cc wrote: This would still require work in each URL-consuming spec, to define taking a reference to the underlying blob's data when it receives an object URL. I think this is inherent to the feature. This is an interesting