IndexedDB refresh is very difficult to discover
Reported by
gaehj...@gmail.com,
Jan 6 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: 1. Load a page/script with IDB features 2. 'Clear site data' 3. Reload page/script What is the expected behavior? I would expect the IndexedDB display to refresh automatically when the page reloads and a fresh instance of the db is opened. What went wrong? When the site data is cleared, the IDB instance disappears from the display, but when a new instance is created Did this work before? No Chrome version: 63.0.3239.132 Channel: stable OS Version: Flash Version: Many developers experience a steep learning curve when using the IndexedDB API for the first time, and it is unclear that the display needs to be refreshed and instead seems to indicate an error in one's own codebase. In my own experience, I was unable to discover the 'Refresh IndexedDB' option in the right-click menu, despite looking for such a feature. I would expect to find a refresh icon somewhere in the IDB panel, as it appears in the objectStore display when one is present. Or I would expect it to refresh automatically, since that is the behavior when the site data is cleared. Improving this behavior seems like it would be a good way of improving the overall experience with IndexedDB and it's API, which is notoriously difficult to begin with. The MDN example is a good page to test with: https://mdn.mozillademos.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB$samples/Full_IndexedDB_example
,
Jan 8 2018
As per comment #0 i.e "I would expect to find a refresh icon somewhere in the IDB panel, as it appears in the objectStore display when one is present. Or I would expect it to refresh automatically, since that is the behavior when the site data is cleared. Improving this behavior seems like it would be a good way of improving the overall experience with IndexedDB" it seems to be a feature request. Hence, marking it as untriaged for further inputs from dev team. Thanks...!!
,
Jan 8 2018
,
Jan 10 2018
This was fixed a few weeks ago. I am not sure if it makes it into Chrome 64. |
||||
►
Sign in to add a comment |
||||
Comment 1 by woxxom@gmail.com
, Jan 6 2018