Changed requirements for automated web storage in Chrome
Some time ago I built a web application which sought to escalate privileges from the user so as to gain persistent storage privileges (to store a good amount of data). At the time and apparently now as well, Chrome advertised that sites could automatically get persistent storage by having one's site among one's bookmarks or by the user having granted the site notification permissions.
I am wondering if there has been an (undocumented) change in these requirements because it seems my web app now always skips over the permission asking for notification permissions because await navigator.storage.persist()
always resolves to a true value, despite the fact that I no longer have the site I am testing (localhost) among my bookmarks and have removed the notifications permission for localhost.
Does anyone have information on what the current standards are for automa开发者_运维百科tic storage persistence at least as far as Chrome? Are there any other site permissions I may have granted which might be treating localhost/127.0.0.1 as having escalated privileges?
精彩评论