📦 Release @webref/css@7.0.3-alpha

[github-actions]

⚠ NEVER add commits to this pull request.

🤖 This pull request was automatically created to facilitate human review of @webref/css changes triggered by curated data at ab3462c.

🧐 Please review the diff below and version numbers. If all looks good, merge this pull request to release the changes to npm.

📦 Latest released @webref/css package was v7.0.2-alpha. Merging this pull request will release v7.0.3-alpha. Make sure that the bump is the right one for the changes.

✍ If any change needs to be made before release, do not add a commit to this pull request. Changes should rather be handled in a separate pull request and pushed to the main branch. You may leave this pull request open in the meantime, or close it. The pre-release job will automatically update this pull request or create a new one once the updates have made their way to the main branch.

🛈 The actual change introduced by this pull request is a version bump in packages/css/package.json. You do not need to review that change. The bumped version is not the version that will be released when this pull request is merged, but rather the version that will be released next time.

diff --ignore-trailing-space '--exclude=package.json' '--exclude=README.md' '--exclude=CHANGELOG.md' '--unified=3' webref/node_modules/@webref/css/css.json packages/css/css.json
--- webref/node_modules/@webref/css/css.json
+++ packages/css/css.json
@@ -1167,7 +1167,7 @@
       "prose": "The color-interpolate() interpolation notation represents an interpolated <color> value, with the following syntax:",
       "href": "https://drafts.csswg.org/css-values-5/#funcdef-color-interpolate",
       "type": "function",
-      "syntax": "color-interpolate( [ <progress-source> && [ by <easing-function> ]? && <easing-function>? && <color-interpolation-method>? ] , <input-position>{1,2} : <color>, [ [ <easing-function> || <color-interpolation-method> ], <input-position>{1,2} : <color> ]#? )"
+      "syntax": "color-interpolate( [ <progress-source> && [ by <easing-function> ]? && <easing-function>? && <color-interpolation-method>? ] , <input-position>{1,2} : <color>, [ [ <easing-function> || <color-interpolation-method> ]?, <input-position>{1,2} : <color> ]#? )"
     },
     {
       "name": "color-layers()",
@@ -2336,7 +2336,7 @@
         "WebkitAppearance",
         "webkitAppearance"
       ],
-      "syntax": "none | auto | base | <compat-auto> | <compat-special> | base"
+      "syntax": "none | auto | base | base-select | <compat-auto> | <compat-special> | base"
     },
     {
       "name": "-webkit-backface-visibility",
@@ -3510,7 +3510,7 @@
       "styleDeclaration": [
         "appearance"
       ],
-      "syntax": "none | auto | base | <compat-auto> | <compat-special> | base"
+      "syntax": "none | auto | base | base-select | <compat-auto> | <compat-special> | base"
     },
     {
       "name": "aspect-ratio",
@@ -17418,8 +17418,32 @@
     },
     {
       "name": "style-feature",
-      "prose": "A container style query allows querying the computed values of the query container. It is a boolean combination of individual style features (<style-feature>) that each query a single, specific property of the query container. The syntax of a <style-feature> is either the same as for a valid declaration [CSS-SYNTAX-3], a supported CSS property, or a <custom-property-name>.",
       "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-feature",
+      "type": "type",
+      "syntax": "<style-feature-plain> | <style-feature-boolean> | <style-range>"
+    },
+    {
+      "name": "style-feature-boolean",
+      "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-feature-boolean",
+      "type": "type",
+      "syntax": "<style-feature-name>"
+    },
+    {
+      "name": "style-feature-name",
+      "prose": "A container style query allows querying the computed values of the query container. It is a boolean combination of individual style features (<style-feature>) that each query a single, specific property of the query container. The syntax of a <style-feature> is either the same as for a valid declaration[CSS-SYNTAX-3], a <style-feature-name> or a valid style range(<style-range>). The <style-feature-name> can be either a supported CSS property or a valid <custom-property-name>. The <style-feature-value> production matches any valid <declaration-value> as long as it doesn’t contain <mf-lt>, <mf-gt> and <mf-eq> tokens.",
+      "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-feature-name",
+      "type": "type"
+    },
+    {
+      "name": "style-feature-plain",
+      "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-feature-plain",
+      "type": "type",
+      "syntax": "<style-feature-name> : <style-feature-value>"
+    },
+    {
+      "name": "style-feature-value",
+      "prose": "A container style query allows querying the computed values of the query container. It is a boolean combination of individual style features (<style-feature>) that each query a single, specific property of the query container. The syntax of a <style-feature> is either the same as for a valid declaration[CSS-SYNTAX-3], a <style-feature-name> or a valid style range(<style-range>). The <style-feature-name> can be either a supported CSS property or a valid <custom-property-name>. The <style-feature-value> production matches any valid <declaration-value> as long as it doesn’t contain <mf-lt>, <mf-gt> and <mf-eq> tokens.",
+      "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-feature-value",
       "type": "type"
     },
     {
@@ -17435,6 +17459,18 @@
       "syntax": "not <style-in-parens> | <style-in-parens> [ [ and <style-in-parens> ]* | [ or <style-in-parens> ]* ] | <style-feature>"
     },
     {
+      "name": "style-range",
+      "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-range",
+      "type": "type",
+      "syntax": "<style-range-value> <mf-comparison> <style-range-value> | <style-range-value> <mf-lt> <style-range-value> <mf-lt> <style-range-value> | <style-range-value> <mf-gt> <style-range-value> <mf-gt> <style-range-value>"
+    },
+    {
+      "name": "style-range-value",
+      "href": "https://drafts.csswg.org/css-conditional-5/#typedef-style-range-value",
+      "type": "type",
+      "syntax": "<custom-property-name> | <style-feature-value>"
+    },
+    {
       "name": "subclass-selector",
       "href": "https://drafts.csswg.org/selectors-4/#typedef-subclass-selector",
       "type": "type",

[tidoust]

Note: the diff is currently made against latest release of v6, which isn't exactly useful. Need to look into it.

[tidoust]

Diff computing has now been fixed.

The diff shows a syntax value for appearance that has two occurrences of base. That's not ideal but should not cause major troubles. I note that it is not the only case where this happens, and it's usually due to a spec extending the meaning of a value for a different context (here in css-forms-1 compared to base definition in css-ui-4). Getting rid of duplicate options in syntaxes would require parsing the base syntax, and we don't have that logic in the crawler.