You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[data] impl updates and features creation (w3c#274)
See w3c#271.
Major pass through all the data files to:
- complete the references to the different status platforms;
- add references to MDN Browser Compatibility data in particular;
- create subfeatures when needed;
- move the URL to the first line;
- use `url` consistently throughout the data files
Note the update also fixes a couple of bugs in `extract-impl-data.js`.
Copy file name to clipboardexpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ Depending on the advancement of the underlying specification, the JSON object ca
58
58
*`url`: should point to the URL of the latest version of the specification. This URL will be used to collect additional data about the spec (standardization status, Working Groups that produce it, editors draft, etc) and as target of links that reference the feature. URL may contain a fragment to point to a specific section in a specification. If the `url` property is not specified, the framework assumes that the underlying specification is a W3C specification, that the filename is its short name, and that the URL of the spec is `https://www.w3.org/TR/[filename]/`.
59
59
*`impl`: for specifications for which browser implementations are expected, the `impl` property explains where to look for implementation info. Described below in [Describing implementation status](#describing-implementation-status).
60
60
*`polyfills`: for specifications for which there are polyfills available that would be worth reporting, the `polyfills` property lists these polyfills. It should be an array of objects that have a `url` property that links to the polyfill's home page on the Web, and a `label` property with the name of polyfill.
61
-
*`features`: in case the reference to the specification would benefit from being more specific than the specification as a whole, and/or in case available implementation information is more fine-grained than the spec level, the `features` property makes it possible to list features in the spec. It must be an array of objects, each object describing a feature through the following properties:
61
+
*`features`: in case the reference to the specification would benefit from being more specific than the specification as a whole, and/or in case available implementation information is more fine-grained than the spec level, the `features` property makes it possible to list features in the spec. It must be an object whose keys are an internal feature ID, and whose values are an object describing the feature with the following properties:
62
62
*`title`: a label for the feature. Property is mandatory.
63
63
*`url`: a URL to the feature in the spec. Fragments such as `#my-feature` are allowed. Property is optional.
64
64
*`impl`: where to look for implementation info. Described below in [Describing implementation status](#describing-implementation-status).
@@ -83,7 +83,7 @@ Here is an example of a JSON file that describes the "Intersection Observer" spe
0 commit comments