Client vs Environment

[annevk]

I will likely rename client to environment in Fetch as it represents an "environment settings object" (from HTML). I don't think it's exposed as a name anywhere yet, however it could be somewhat confusing if we have underlying concepts and exposed concepts with different names.

[KenjiBaheux]

Confirming that this is not exposed in blink (currently out of scope).

[jakearchibald]

When I see environments I think development vs production.

[annevk]

So the observable places for this API-wise would be FetchEvent.client or Request.client (TBD which one) and ServiceWorkerGlobalScope.getClients(). (Assuming ServiceWorkerClient is split into BrowsingContext, Worker, and SharedWorker.)

Correct? I think I would be okay with client remaining the term to use here.

Pinging @Hixie as a heads up, though I believe he did not care much either way.