Add batching to IndexedDBObserver changes |
|
Issue descriptionfor compatibility with lifecycle, changes should be allowed to be batched up quite a bit. This should happen by default so that it doesn't suprise web developers. Maybe the rule should be - batch up observations until there are no longer transactions running that add to it, probably with a timeout as well. |
|
►
Sign in to add a comment |
|
Comment 1 by dmu...@chromium.org
, Jan 3Labels: -Type-Bug Hotlist-GoodFirstBug Type-Feature
Owner: ----
Status: Available (was: Assigned)