Tag everything with worker support?

Worker support of APIs is quite a challenge to track and maintain docs for - it can vary across an API and be spotty across browsers. It also isn't necessarily obvious to a user how they go about using some APIs.

I think it might make sense to "standardise" this in BCD and roll it out more or less for every single Web API.

• There are four types of workers - dedicated, shared, service, chrome. I don't know if we'd need to indicate these separately or not.
• It is useful to note the API used to access the feature in both main thread (often via window or window.navigator) and the web service (usually some context)

There are a few good examples where this has been done in an adhoc way:

• FileReaderSync ([mdn]((https://developer.mozilla.org/en-US/docs/Web/API/FileReaderSync) | bcd) has separate keys indicating support for service workers and for other workers.
  
• CacheStorage (mdn) has a note indicating how it is used in both web workers and main thread.
  

FYI @chrisdavidmills @Elchi3 @ddbeck Would appreciate your thinking on this. To me this is a similar problem to documenting secure contexts.

Start by comparing the existing worker-support entries in FileReaderSync.json and CacheStorage.json with the linked MDN Web Workers documentation. Clarify how dedicated, shared, service, and chrome workers and their access contexts should be represented, then determine which Web API data files would need the standardized treatment. Done means the representation and rollout scope are agreed and consistently applied.