caches.match() should not reject on missing name |
|||
Issue descriptionSpec change: https://github.com/slightlyoff/ServiceWorker/issues/891 Previously: caches.match(url, {name:'no_such_cache'}) --> rejects Now: caches.match(url, {name:'no_such_cache'}) --> resolves undefined The cache is NOT implicitly created.
,
Jul 20 2016
CL: https://codereview.chromium.org/2161423003/
,
Jul 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9916998beca540fc96101352626d49fd0193dca8 commit 9916998beca540fc96101352626d49fd0193dca8 Author: jinho.bang <jinho.bang@samsung.com> Date: Thu Jul 21 10:57:55 2016 CacheStorage: caches.match with bad cacheName should resolve with undefined. Make caches.match(request, options)'s promise resolve with undefined (rather than reject) when options.cacheName is given but no corresponding Cache object is found. Related spec issue: https://github.com/slightlyoff/ServiceWorker/issues/891 BUG= 610349 Review-Url: https://codereview.chromium.org/2161423003 Cr-Commit-Position: refs/heads/master@{#406817} [modify] https://crrev.com/9916998beca540fc96101352626d49fd0193dca8/third_party/WebKit/LayoutTests/http/tests/cachestorage/script-tests/cache-storage-match.js [modify] https://crrev.com/9916998beca540fc96101352626d49fd0193dca8/third_party/WebKit/Source/modules/cachestorage/CacheStorage.cpp [modify] https://crrev.com/9916998beca540fc96101352626d49fd0193dca8/third_party/WebKit/Source/modules/cachestorage/CacheStorageError.cpp
,
Jul 23 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jsb...@chromium.org
, May 9 2016