Commit d235632

peachesontourMuhammedZakir

and

authored

Update 6-data-storage/03-indexeddb/article.md

Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>

1 parent 7b88ad9 commit d235632Copy full SHA for d235632

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
@@ -121,7 +121,7 @@ So there's a tab with an open connection to DB version `1`, while the second tab
`121`	`121`
`122`	`122`	The problem is that a database is shared between two tabs, as it's the same site, same origin. And it can't be both version `1` and `2`. To perform the update to version `2`, all connections to version 1 must be closed, including the one in the first tab.
`123`	`123`
`124`		-In order to organize that, the `versionchange` event triggers on the "outdated" database object. We should listen for it and close the old database connection (and probably suggest the visitor reloads the page, to load the updated code).
	`124`	+In order to organize that, the `versionchange` event triggers on the "outdated" database object. We should listen for it and close the old database connection (and probably suggest a page reload, to load the updated code).
`125`	`125`
`126`	`126`	If we don't listen for the `versionchange` event and don't close the old connection, then the second, new connection won't be made. The `openRequest` object will emit the `blocked` event instead of `success`. So the second tab won't work.
`127`	`127`

Comments

(0)