- From: Joshua Bell <jsbell@google.com>
- Date: Wed, 9 Oct 2013 12:10:55 -0700
- To: Joćo Eiras <joaoe@opera.com>
- Cc: Webapps WG <public-webapps@w3.org>
Received on Wednesday, 9 October 2013 19:11:22 UTC
To do this in a backwards compatible way, we could add an option on open() that, if an upgrade is required, any other connections are forcibly closed; instead of a "versionchange" event the connections would be sent a "close" event, similar to the case in [1] Open question about whether the close waits on in-flight transactions or if they are aborted. [1] http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0022.html On Wed, Oct 9, 2013 at 8:40 AM, Joćo Eiras <joaoe@opera.com> wrote: > On Wed, 09 Oct 2013 17:06:13 +0200, Kyaw Tun <kyawtun@yathit.com> wrote: > > My suggestion is to make close method as default operation of blocked >> event. For that app, that require to save data should listen blocked event >> and invoke preventDefault() and finally close the connection. >> > > Hi. > > This was already discussed in length here > > http://lists.w3.org/Archives/**Public/public-webapps/** > 2012JulSep/0215.html<http://lists.w3.org/Archives/Public/public-webapps/2012JulSep/0215.html> > > TL,DR: the status quo of the implementations (still experimental in 2012) > dictated that the behavior is to be preserved. > > Bye. > >
Received on Wednesday, 9 October 2013 19:11:22 UTC