Re: [IndexedDB] blocked event should have default operation to close the connection

2013-10-11 Thread Odin Hørthe Omdal
On Wed, Oct 9, 2013, at 21:10, Joshua Bell wrote: > 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

Re: [IndexedDB] blocked event should have default operation to close the connection

2013-10-09 Thread Joshua Bell
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

Re: [IndexedDB] blocked event should have default operation to close the connection

2013-10-09 Thread João Eiras
On Wed, 09 Oct 2013 17:06:13 +0200, Kyaw Tun 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

[IndexedDB] blocked event should have default operation to close the connection

2013-10-09 Thread Kyaw Tun
An application receive blocked event on IndexedDB database instance when another app open the database with a newer version. The receiving application must close the connection so that other tab receive open success event. Otherwise database open request will be pending. Most developer are unaware