George Kalpakas e0ed59e55f fix(service-worker): correctly handle requests with empty `clientId` (#23625) ... Requests from clients that are not assigned a client ID by the browser will produce `fetch` events with `null` or empty (`''`) `clientId`s. Previously, the ServiceWorker only handled `null` values correctly. Yet empty strings are also valid (see for example [here][1] and [there][2]). With this commit, the SW will interpret _all_ falsy `clientId` values the same (i.e. "no client ID assigned") and handle them appropriately. Related Chromium issue/discussion: [#832105][3] [1]: 4cc72bd0f1/docs/index.bs (L1392) [2]: https://w3c.github.io/ServiceWorker/#fetchevent-interface [3]: https://bugs.chromium.org/p/chromium/issues/detail?id=832105 Fixes #23526 PR Close #23625		2018-05-09 11:50:02 -07:00
..
src	fix(service-worker): correctly handle requests with empty `clientId` (#23625)	2018-05-09 11:50:02 -07:00
test	fix(service-worker): correctly handle requests with empty `clientId` (#23625)	2018-05-09 11:50:02 -07:00
testing	test(service-worker): support mock requests with null/empty client ID (#23625)	2018-05-09 11:50:02 -07:00
BUILD.bazel	build(service-worker): properly build npm_package with Bazel (#23090)	2018-04-04 10:26:38 -07:00
main.ts	feat(service-worker): introduce the @angular/service-worker package (#19274)	2017-09-28 16:18:12 -07:00
rollup-worker.config.js	feat(service-worker): introduce the @angular/service-worker package (#19274)	2017-09-28 16:18:12 -07:00
tsconfig.json	refactor(bazel): convert most ts_library to ng_module (#22176)	2018-02-15 14:08:53 -08:00