- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 05 Jan 2017 19:17:56 -0800
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 January 2017 03:18:30 UTC
marcoscaceres commented on this pull request. > +other tabs, you should use the "versionchange" event to close the connection to +the database. + +<pre class=lang-javascript> +db.onversionchange = function() { + // First, save any unsaved data: + saveUnsavedData().then(function() { + // Now you need to close the database. + // If the document isn't being actively used, it may be appropriate to reload: + if (!document.hasFocus()) { + location.reload(); + // Reloading will close the database, and also reload with the new JavaScript + // and database definitions. + } else { + // Alternatively you may close the database and display a message to the + // user. You need to ensure this isn't a disruptive user experience. ah - ok. I gotta get my head out of service worker land and message passing. I'm still not totally clear where .onblocked comes into play... if at all? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/pull/133
Received on Friday, 6 January 2017 03:18:30 UTC