mdn
Add more spec_urls; set some standard_tracks to false (APIs A-E)
This is a bit of a test PR to see if we could add spec_urls everywhere (especially for behavioral sub features). Some things came up where we should probably agree on spec_url consistency for a few common sub features:
- worker_support
- iterable sub features (forEach, keys, values, iterator, etc)
- secure_context_required I decided to use the spec_url for the interface itself, happy to hear other thoughts.
Also, I think when a sub aspect of e.g. a method is described then it is okay to link to the same spec section as the method. So, basically the sub feature gets the same spec_url as the parent feature.
I marked standard_track false for a few things: CSSPrimitiveValue, CSSValue, CSSValueList, DOMError, FeaturePolicy. Doesn't look like these will be going anywhere.
Fixes https://github.com/mdn/browser-compat-data/issues/27456.
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This is a bit of a test PR
Is it okay to merge?
Yes, thanks for taking a look! I will proceed with more additions like this given that no one seems to hate it :)
Let's mark as draft for now then, I'll happily go through the changes to double check once complete.
This pull request has merge conflicts that must be resolved before it can be merged.