angular-docs-cn/packages/service-worker/worker/test
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
..
BUILD.bazel feat(service-worker): add support for configuring navigations URLs (#23339) 2018-04-13 13:13:36 -07:00
async.ts feat(service-worker): introduce the @angular/service-worker package (#19274) 2017-09-28 16:18:12 -07:00
data_spec.ts feat(service-worker): add support for configuring navigations URLs (#23339) 2018-04-13 13:13:36 -07:00
happy_spec.ts fix(service-worker): correctly handle requests with empty `clientId` (#23625) 2018-05-09 11:50:02 -07:00
idle_spec.ts build: add bazel test rules for remainder of packages (#21053) 2017-12-22 13:10:51 -08:00
prefetch_spec.ts build: add bazel test rules for remainder of packages (#21053) 2017-12-22 13:10:51 -08:00