[IndexedDB] Full text indexing

Hi all. Disclaimer: last time I posted to this mailing list someone correctly pointed out that I'd not read the spec properly. Apologies if I've done the same again. I'm very enthusiastic about the whole offline web app thing, and as this is a public forum I thought I may as well fire off a couple

ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events]

ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/118 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters wrote in

Re: [CORS] What constitutes a "network error"?

20.07.2010, в 14:37, Jonas Sicking написал(а): > However I haven't been able to find a clear definition of what counts > as a "network error". Does this include successful HTTP requests that > return 4xx or 5xx status codes? Or just errors in the lower level of > the stack, such as aborted TCP co

Re: [CORS] What constitutes a "network error"?

On Wed, Jul 21, 2010 at 1:14 PM, Alexey Proskuryakov wrote: > > 20.07.2010, в 14:37, Jonas Sicking написал(а): > >> However I haven't been able to find a clear definition of what counts >> as a "network error". Does this include successful HTTP requests that >> return 4xx or 5xx status codes? Or j

Re: ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events]

On Wed, Jul 21, 2010 at 10:11 AM, Web Applications Working Group Issue Tracker wrote: > > ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic > event duplication for links [DOM3 Events] > > http://www.w3.org/2008/webapps/track/issues/118 > > Raised by: Doug Schepers > On

Re: Lifetime of Blob URL

Tying a 'lifetime' of a string url to a blob which is not even needed at the point of use seems to be creating a mechanism that doesn't generally work: function getImageUrl() { var a_blob = ... load a blob in some way, perhaps via XHR return a_blob.url; } ... // sometime during initialization

[Bug 9766] We should expose the subprotocol for the case of the client not specifying one but the server specifying one

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9766 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 9973] If the entry's name is "sec-websocket-protocol" 0 please don't put normative requirements in parenthesis

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9973 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug 9989] Is the number of replacement characters supposed to be well-defined? If not this should be explicitly noted. If it is then more detail is required.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9989 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug 10129] The end of this WebSocket section links to EventSource with "fail the connection". It should link to the WebSocket "fail the connection" instead.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10129 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug 10213] The definition of "absolute url" makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this defini

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug 10213] The definition of "absolute url" makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this defini

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213 Boris Zbarsky changed: What|Removed |Added Status|RESOLVED|REOPENED CC|