Issue metadata
Sign in to add a comment
|
Exceed
Reported by
thiago...@gmail.com,
May 14 2018
|
||||||||||||||||||||||||
Issue description
THIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB
BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE!
Device name:SM-A500M
Android version: 6.0.1
WebView version (from system settings -> Apps -> Android System WebView):67.0.3396.42
Application: Sample Application (using pouchdb) - Ionic Framework 3.9.2
Application version: 0.0.1
URLs (if applicable): none
Steps to reproduce:
(1) any Ionic 3 sample application using Pouchdb using IndexedDB
(2) try - new PouchDB("mydatabase")
Expected result:
DB opened with no errors and this bug ( https://bugs.chromium.org/p/chromium/issues/detail?id=838816) merged to this webview version 67.0.3396.42.
Can this bug be merged to the next beta update?
Actual result:
{"status":500,"name":"indexed_db_went_bad","message":"unknown","reason":"QuotaExceededError"}
,
May 14 2018
It was merged, but it wasn't released. At https://www.chromium.org/developers/calendar there is no other beta release for webview in May and M67 will be released in two weeks! For a serious fix like this one, would be an update to current beta/alpha or a new release with this bug fixed (using 66.0.3359.158). All mobile phone running hybrid apps, with less than one 1GB of free space, using local storage (my case PouchDB, with IndexedDB), with Webview updated, are unable to get the app running. https://stackoverflow.com/questions/50019306/chrome-on-android-granted-quota-for-indexeddb-suddenly-almost-0?rq=1 A lot of developer must not been aware of this yet. Best regards,
,
May 14 2018
thiagorow@ the fix has been merged, which means it will be in the next beta release. That calendar only covers stable releases, not beta releases. Rest assured, we regularly release several betas per cycle (and we aim to release at least another M67 beta before M67 stable). If you want an "alpha" release, consider Chrome's dev or canary channels--that CL has landed in both channels. Lastly, if you still have concerns about this fix not being released, please follow up on *that bug*. Filing a separate issue isn't helpful.
,
May 15 2018
The initial issue achieved its goal: detailed the problem, fix was made and merged. Make no sense add any comments there. My point is that this fix is so serious that should be released as stable/beta as soon as possible. I can't understand why I'm the only complaining about this. Let's wait for the next beta/stable webview release. Thank you ntfschr@ |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ntfschr@chromium.org
, May 14 2018Status: Duplicate (was: Unconfirmed)