https://www.w3.org/Bugs/Public/show_bug.cgi?id=17486
Summary: Whatsapp application can not connect to server
Product: WebAppsWG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#top
OS/Vers
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17485
Summary: Whatsapp application can not connect to server
Product: WebAppsWG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#top
OS/Vers
* Ojan Vafai wrote:
>This confusion seems to come up a lot since DOM is part of public-webapps
>but uses a separate mailing list. Maybe it's time to reconsider that
>decision? It's the editors of the specs who have the largest say here IMO.
The confusion is not going to go away by changing the pro
If a keypath passed to createObjectStore fails certain constraints (not
passing arrays or empty strings to autoIncrement) the spec says to throw an
InvalidAccessError.
If a keypath passed to createIndex fails constraints (an array keypath
passed to a multientry index) the spec says to throw a NotS
On Tue, Jun 12, 2012 at 6:30 PM, Pablo Flouret wrote:
> This spec problem can be worked around by observing the error event. If
> the readyState property is now CLOSED (in readyState 2), we set a 30 second
> timeout. When this fires, we create a new eventsource object to replace the
> old one (yo
On Mon, 11 Jun 2012 17:56:00 -0700, Ian Hickson wrote:
On Tue, 17 Apr 2012, Odin Hørthe Omdal wrote:
I tried yanking the network for 10+ minutes, and when I put the cable in
again, both Firefox and Chromium used 25 seconds to reconnect. When only
yanking it for one minute, the reconnection
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14569
public-html-me...@w3.org changed:
What|Removed |Added
CC||public-html-me...@w3.org,
On Wed, Jun 13, 2012 at 1:32 AM, Travis Leithead
wrote:
> I wouldn’t mind. I’m on both lists anyway. Schepers originally saw it as a
> way of scoping DOM3 Events discussions away from the noise on
> public-webapps. I’m not sure that’s a real big concern anymore.
I don't care either way. To look u
On Tue, 12 Jun 2012 15:08:14 +0200, Glenn Maynard wrote:
It would also make sense for the web app to be able to tell that it's in
a retrying state. That is, it's not connected and according to the
current spec would have received an error, but it's not in an error
state either (retries are
