breautek commented on issue #1210:
URL: https://github.com/apache/cordova-docs/issues/1210#issuecomment-3708085099

   @Shiva903-hue We can probably expand on [storage 
page](https://cordova.apache.org/docs/en/dev/cordova/storage/storage.html) (see 
https://github.com/apache/cordova-docs/blob/master/www/docs/en/dev/cordova/storage/storage.md)
 for caches but we should try to refrain from documenting the feature because 
it's a web feature. We can link to resources such as MDN that can document the 
web feature which will be much more complete and more likely to be updated as 
web standards change. We can however summarize the web feature and how they 
work in conjunction in webviews, especially if they exhibit caveats within a 
webview vs a typical browser context.
   
   It's not a feature I actually ever use, at least not directly, and I'm not 
very knowledgeable about this particular API. I'd have to trust the community 
input for accuracy.
   
   I assume they exhibit similar issues as other web storage contexts where 
they are webview and origin dependent (so changing the origin like setting a 
different scheme, or changing webview implementations will prevent access to 
the original cache object, if they persist across app restarts).
   
   > Platform differences and expectations (Android WebView vs iOS WKWebView)
   
   If possible, I'd throw Electron in the mix too, for completeness, but not 
required. Android and iOS platforms are definitely the most important platforms 
to cover imo.
   
   > I’ll avoid making assumptions about exact storage limits and will focus on 
documented behavior and practical guidance.
   
   100% 👍 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to