@webref/css 6.10.0 → 6.10.2

package/css-shapes.json

@@ -8,7 +8,7 @@
       "name": "shape-outside",
       "value": "none | [ <basic-shape> || <shape-box> ] | <image>",
       "initial": "none",
-      "appliesTo": "floats",
+      "appliesTo": "floats and initial letter boxes",
       "inherited": "no",
       "percentages": "n/a",
       "computedValue": "as defined for <basic-shape> (with <shape-box> following, if supplied); else the computed <image>; else the keyword as specified",
@@ -66,7 +66,7 @@
       "name": "shape-margin",
       "value": "<length-percentage [0,∞]>",
       "initial": "0",
-      "appliesTo": "floats",
+      "appliesTo": "floats and initial letter boxes",
       "inherited": "no",
       "percentages": "refer to the inline size of the containing block",
       "computedValue": "computed <length-percentage> value",
@@ -96,53 +96,48 @@
       "values": [
         {
           "name": "inset()",
-          "value": "inset( <length-percentage>{1,4} [ round <'border-radius'> ]? )",
-          "type": "function"
+          "prose": "Defines an inset rectangle via insets from each edge of the reference box. If less than four <length-percentage> values are provided, the omitted values default in the same way as the margin shorthand: an omitted second or third value defaults to the first, and an omitted fourth value defaults to the second. The four <length-percentage>s define the position of the top, right, bottom, and left edges of a rectangle, respectively, as insets from the corresponding edges of the reference box. A pair of insets in either dimension that add up to more than the used dimension (such as left and right insets of 75% apiece) use the CSS Backgrounds 3 § 4.5 Overlapping Curves rules to proportionally reduce the inset effect to 100%. For example, specifying inset(75% 0 50% 0) has the top+bottom edges summing to 125% of the reference box’s height. They’re proportionally reduced to sum to 100%, identical to specifying inset(60% 0 40% 0). The optional <'border-radius'> argument(s) define rounded corners for the rectangle using the border-radius shorthand syntax.",
+          "type": "function",
+          "value": "inset( <length-percentage>{1,4} [ round <'border-radius'> ]? )"
         },
         {
           "name": "xywh()",
-          "value": "xywh( <length-percentage>{2} <length-percentage [0,∞]>{2} [ round <'border-radius'> ]? )",
-          "type": "function"
+          "prose": "Defines a rectangle via offsets from the top and left edge of the reference box, and a specified width and height. The four <length-percentage>s define, respectively, the inset from the left edge of the reference box, the inset from the top edge of the reference box, the width of the rectangle, and the height of the rectangle. The optional <'border-radius'> argument(s) define rounded corners for the inset rectangle using the border-radius shorthand syntax.",
+          "type": "function",
+          "value": "xywh( <length-percentage>{2} <length-percentage [0,∞]>{2} [ round <'border-radius'> ]? )"
         },
         {
           "name": "rect()",
-          "value": "rect( [ <length-percentage> | auto ]{4} [ round <'border-radius'> ]? )",
-          "type": "function"
+          "prose": "Defines a rectangle via insets from the top and left edges of the reference box. The four <length-percentage>s define the position of the top, right, bottom, and left edges of a rectangle, respectively, as insets from the top edge of the reference box (for the first and third values) or the left edge of the reference box (for the second and fourth values). An auto value makes the edge of the box coincide with the corresponding edge of the reference box: it’s equivalent to 0% as the first (top) or fourth (left) value, and equivalent to 100% as the second (right) or third (bottom) value. The second (right) and third (bottom) values are floored by the fourth (left) and second (top) values, respectively. For example, specifying rect(10px 0 0 20px) would place the bottom edge higher than the top edge, and the right edge further left than the left edge, so both are corrected to not cross over the other edge, identical to specifying rect(10px 20px 10px 20px). The optional <'border-radius'> argument(s) define rounded corners for the rectangle using the border-radius shorthand syntax.)",
+          "type": "function",
+          "value": "rect( [ <length-percentage> | auto ]{4} [ round <'border-radius'> ]? )"
         },
         {
           "name": "circle()",
-          "value": "circle( <shape-radius>? [ at <position> ]? )",
-          "type": "function"
+          "prose": "The <radial-size> argument defines the circle’s radius. Rather than referring to the gradient box, values are resolved against the [=/reference box=]. Two <length-percentage> values are invalid. The <position> argument defines the center of the circle. Unless otherwise specified, this defaults to center if omitted.",
+          "type": "function",
+          "value": "circle( <radial-size>? [ at <position> ]? )"
         },
         {
           "name": "ellipse()",
-          "value": "ellipse( [ <shape-radius>{2} ]? [ at <position> ]? )",
-          "type": "function"
+          "prose": "The <radial-size> argument defines the horizontal and vertical radiuses of the ellipse. Rather than referring to the gradient box, values are resolved against the [=/reference box=]. The <position> argument defines the center of the ellipse. Unless otherwise specified, this defaults to center if omitted.",
+          "type": "function",
+          "value": "ellipse( <radial-size>? [ at <position> ]? )"
         },
         {
           "name": "polygon()",
-          "value": "polygon( <'fill-rule'>? , [<length-percentage> <length-percentage>]# )",
-          "type": "function"
+          "prose": "The <'fill-rule'> specifies the filling rule used to determine the interior Defaults to nonzero if omitted. Each <length-percentage> pair specifies a vertex of the polygon, as a horizontal and vertical offset from the left and top edges of the [=/reference box=]. The UA must close a polygon by connecting the last vertex with the first vertex of the list.",
+          "type": "function",
+          "value": "polygon( <'fill-rule'>? , [<length-percentage> <length-percentage>]# )"
         },
         {
           "name": "path()",
-          "value": "path( <'fill-rule'>? , <string> )",
+          "prose": "The <'fill-rule'> specifies the filling rule used to determine the interior Defaults to nonzero if omitted. The <string> represents an SVG Path data string. A path data string that does not conform to the to the grammar and parsing rules of SVG 1.1, or that does conform but defines an empty path, is invalid and causes the entire path() to be invalid. The initial position is defined by the first “move to” argument in the path string. For the initial direction follow SVG 1.1. The UA must close a path with an implicit closepath command (\"z\" or \"Z\") if it is not present in the string for properties that require a closed loop (such as shape-outside and clip-path).",
           "type": "function",
-          "values": [
-            {
-              "name": "<string>",
-              "type": "value",
-              "value": "<string>"
-            }
-          ]
+          "value": "path( <'fill-rule'>? , <string> )"
         }
       ]
     },
-    {
-      "name": "<shape-radius>",
-      "value": "<length-percentage [0,∞]> | closest-side | farthest-side",
-      "type": "type"
-    },
     {
       "name": "<basic-shape-rect>",
       "type": "type",

package/css-speech.json

@@ -525,7 +525,7 @@
       "values": [
         {
           "name": "<family-name>",
-          "prose": "Values are specific voice instances (e.g., Mike, comedian, mary, carlos2, \"valley girl\"). Like font-family names, voice names must either be given quoted as strings, or unquoted as a sequence of one or more CSS identifiers. If a sequence of identifiers is given as a voice name, the computed value is the name converted to a string by joining all the identifiers in the sequence by single spaces. Voice names that happen to be the same as the gender keywords (male, female and neutral) or that happen to match the CSS-wide keywords or preserve must be quoted to disambiguate with these keywords. The keyword default is reserved for future use and must also be quoted when used as voice names. It is recommended to quote voice names that contain white space, digits, or punctuation characters other than hyphens—even if these voice names are valid in unquoted form—in order to improve code clarity. For example: voice-family: \"john doe\", \"Henry the-8th\";",
+          "prose": "Values are specific voice instances (e.g., Mike, comedian, mary, carlos2, \"valley girl\"). Like font-family names, voice names must either be given quoted as strings, or unquoted as a sequence of one or more CSS identifiers. If a sequence of identifiers is given as a voice name, the computed value is the name converted to a string by joining all the identifiers in the sequence by single spaces. Voice names that happen to be the same as the gender keywords (male, female and neutral) or that happen to match the CSS-wide keywords or preserve must be quoted to disambiguate with these keywords. The keyword default is reserved for future use and must also be quoted when used as voice names. It is recommended to quote voice names that contain white space, digits, or punctuation characters other than hyphens—​even if these voice names are valid in unquoted form—​in order to improve code clarity. For example: voice-family: \"john doe\", \"Henry the-8th\";",
           "type": "value",
           "value": "<family-name>"
         },

package/css-text-4.json

@@ -898,7 +898,7 @@
       "values": [
         {
           "name": "auto",
-          "prose": "The UA determines the justification algorithm to follow, based on a balance between performance and adequate presentation quality. Since justification rules vary by writing system and language, UAs should, where possible, use a justification algorithm appropriate to the text. For example, the UA could use by default a justification method that is a simple universal compromise for all writing systems—such as primarily expanding word separators and between CJK typographic letter units along with secondarily expanding between Southeast Asian typographic letter units. Then, in cases where the content language of the paragraph is known, it could choose a more language-tailored justification behavior e.g. following the Requirements for Japanese Text Layout for Japanese [JLREQ], using cursive elongation for Arabic, using inter-word for German, etc. An example of cursively-justified Arabic text, rendered by Tasmeem. Like English, Arabic can be justified by adjusting the spacing between words, but in most styles it can also be justified by calligraphically elongating or compressing the letterforms themselves. In this example, the upper text is extended to fill the line by the use of elongated (kashida) forms and swash forms, while the bottom line is compressed slightly by using a stacked combination for the characters between ت and م. By employing traditional calligraphic techniques, a typesetter can justify the line while preserving flow and color, providing a very high quality justification effect. However, this is by its nature a very script-specific effect. Mixed-script text with text-justify: auto: this interpretation uses a universal-compromise justification method, expanding at spaces as well as between CJK and Southeast Asian letters. This effectively uses inter-word + inter-ideograph spacing for lines that have word-separators and/or CJK characters and falls back to inter-cluster behavior for lines that don’t or for which the space stretches too far.",
+          "prose": "The UA determines the justification algorithm to follow, based on a balance between performance and adequate presentation quality. Since justification rules vary by writing system and language, UAs should, where possible, use a justification algorithm appropriate to the text. For example, the UA could use by default a justification method that is a simple universal compromise for all writing systems—​such as primarily expanding word separators and between CJK typographic letter units along with secondarily expanding between Southeast Asian typographic letter units. Then, in cases where the content language of the paragraph is known, it could choose a more language-tailored justification behavior e.g. following the Requirements for Japanese Text Layout for Japanese [JLREQ], using cursive elongation for Arabic, using inter-word for German, etc. An example of cursively-justified Arabic text, rendered by Tasmeem. Like English, Arabic can be justified by adjusting the spacing between words, but in most styles it can also be justified by calligraphically elongating or compressing the letterforms themselves. In this example, the upper text is extended to fill the line by the use of elongated (kashida) forms and swash forms, while the bottom line is compressed slightly by using a stacked combination for the characters between ت and م. By employing traditional calligraphic techniques, a typesetter can justify the line while preserving flow and color, providing a very high quality justification effect. However, this is by its nature a very script-specific effect. Mixed-script text with text-justify: auto: this interpretation uses a universal-compromise justification method, expanding at spaces as well as between CJK and Southeast Asian letters. This effectively uses inter-word + inter-ideograph spacing for lines that have word-separators and/or CJK characters and falls back to inter-cluster behavior for lines that don’t or for which the space stretches too far.",
           "type": "value",
           "value": "auto"
         },
@@ -1138,7 +1138,7 @@
     {
       "name": "text-spacing-trim",
       "value": "<spacing-trim> | auto",
-      "initial": "space-first",
+      "initial": "normal",
       "appliesTo": "text",
       "inherited": "yes",
       "percentages": "N/A",
@@ -1152,6 +1152,12 @@
           "type": "value",
           "value": "space-all"
         },
+        {
+          "name": "normal",
+          "prose": "Set fullwidth opening punctuation with full-width glyphs (spaced) at the start of each line; set fullwidth closing punctuation with half-width glyphs (flush) at the end of each line if it does not otherwise fit prior to justification, else set the punctuation with full-width glyphs; and collapse spacing between punctuation glyphs as described below.",
+          "type": "value",
+          "value": "normal"
+        },
         {
           "name": "trim-auto",
           "prose": "Set fullwidth opening punctuation with half-width glyphs (flush) at the start of each line; set fullwidth closing punctuation with half-width glyphs (flush) at the end of each line; and collapse spacing between punctuation glyphs as described below.",
@@ -1160,15 +1166,15 @@
         },
         {
           "name": "space-first",
-          "prose": "Set fullwidth opening punctuation with full-width glyphs (spaced) on the first line the block container and each line after a forced line break. Otherwise as trim-auto (unless allow-end is also specified).",
+          "prose": "Set fullwidth opening punctuation with full-width glyphs (spaced) on the first line the block container and each line after a forced line break. Otherwise as trim-auto.",
           "type": "value",
           "value": "space-first"
         },
         {
-          "name": "allow-end",
-          "prose": "Set fullwidth closing punctuation with half-width glyphs (flush) at the end of each line if it does not otherwise fit prior to justification, else set the punctuation with full-width glyphs. Otherwise as trim-auto (unless space-first is also specified).",
+          "name": "trim-start",
+          "prose": "Set fullwidth opening punctuation with half-width glyphs (flush) at the start of each line. Otherwise as normal.",
           "type": "value",
-          "value": "allow-end"
+          "value": "trim-start"
         },
         {
           "name": "trim-all",
@@ -1190,7 +1196,7 @@
     },
     {
       "name": "text-spacing",
-      "value": "normal | none | auto | <spacing-trim> || <autospace>",
+      "value": "none | auto | <spacing-trim> || <autospace>",
       "initial": "see individual properties",
       "appliesTo": "text",
       "inherited": "yes",
@@ -1199,12 +1205,6 @@
       "animationType": "discrete",
       "canonicalOrder": "per grammar",
       "values": [
-        {
-          "name": "normal",
-          "prose": "Specifies the baseline behavior, setting each sub-property to its initial value. Equivalent to space-first ideograph-alpha ideograph-numeric.",
-          "type": "value",
-          "value": "normal"
-        },
         {
           "name": "none",
           "prose": "Turns off all text-spacing features: sets text-spacing-trim to space-all and text-autospace to no-autospace.",
@@ -1335,7 +1335,7 @@
     {
       "name": "<spacing-trim>",
       "type": "type",
-      "value": "space-all | trim-auto | [ allow-end || space-first ] | trim-all"
+      "value": "space-all | normal | trim-auto | trim-start | space-first | trim-all"
     }
   ]
 }

package/css-text.json

@@ -413,7 +413,7 @@
       "values": [
         {
           "name": "auto",
-          "prose": "The UA determines the justification algorithm to follow, based on a balance between performance and adequate presentation quality. Since justification rules vary by writing system and language, UAs should, where possible, use a justification algorithm appropriate to the text. For example, the UA could use by default a justification method that is a simple universal compromise for all writing systems—such as primarily expanding word separators and between CJK typographic letter units along with secondarily expanding between Southeast Asian typographic letter units. Then, in cases where the content language of the paragraph is known, it could choose a more language-tailored justification behavior e.g. following the Requirements for Japanese Text Layout for Japanese [JLREQ], using cursive elongation for Arabic, using inter-word for German, etc. An example of cursively-justified Arabic text, rendered by Tasmeem. Like English, Arabic can be justified by adjusting the spacing between words, but in most styles it can also be justified by calligraphically elongating or compressing the letterforms themselves. In this example, the upper text is extended to fill the line by the use of elongated (kashida) forms and swash forms, while the bottom line is compressed slightly by using a stacked combination for the characters between ت and م. By employing traditional calligraphic techniques, a typesetter can justify the line while preserving flow and color, providing a very high quality justification effect. However, this is by its nature a very script-specific effect. Mixed-script text with text-justify: auto: this interpretation uses a universal-compromise justification method, expanding at spaces as well as between CJK and Southeast Asian letters. This effectively uses inter-word + inter-ideograph spacing for lines that have word-separators and/or CJK characters and falls back to inter-cluster behavior for lines that don’t or for which the space stretches too far.",
+          "prose": "The UA determines the justification algorithm to follow, based on a balance between performance and adequate presentation quality. Since justification rules vary by writing system and language, UAs should, where possible, use a justification algorithm appropriate to the text. For example, the UA could use by default a justification method that is a simple universal compromise for all writing systems—​such as primarily expanding word separators and between CJK typographic letter units along with secondarily expanding between Southeast Asian typographic letter units. Then, in cases where the content language of the paragraph is known, it could choose a more language-tailored justification behavior e.g. following the Requirements for Japanese Text Layout for Japanese [JLREQ], using cursive elongation for Arabic, using inter-word for German, etc. An example of cursively-justified Arabic text, rendered by Tasmeem. Like English, Arabic can be justified by adjusting the spacing between words, but in most styles it can also be justified by calligraphically elongating or compressing the letterforms themselves. In this example, the upper text is extended to fill the line by the use of elongated (kashida) forms and swash forms, while the bottom line is compressed slightly by using a stacked combination for the characters between ت and م. By employing traditional calligraphic techniques, a typesetter can justify the line while preserving flow and color, providing a very high quality justification effect. However, this is by its nature a very script-specific effect. Mixed-script text with text-justify: auto: this interpretation uses a universal-compromise justification method, expanding at spaces as well as between CJK and Southeast Asian letters. This effectively uses inter-word + inter-ideograph spacing for lines that have word-separators and/or CJK characters and falls back to inter-cluster behavior for lines that don’t or for which the space stretches too far.",
           "type": "value",
           "value": "auto"
         },

package/css-transitions.json

@@ -1,6 +1,6 @@
 {
   "spec": {
-    "title": "CSS Transitions",
+    "title": "CSS Transitions Level 1",
     "url": "https://drafts.csswg.org/css-transitions-1/"
   },
   "properties": [

package/css-values.json

@@ -516,7 +516,7 @@
     },
     {
       "name": "clamp()",
-      "prose": "The clamp() function takes three calculations—a minimum value, a central value, and a maximum value—and represents its central calculation, clamped according to its min and max calculations, favoring the min calculation if it conflicts with the max. (That is, given clamp(MIN, VAL, MAX), it represents exactly the same value as max(MIN, min(VAL, MAX))).",
+      "prose": "The clamp() function takes three calculations—​a minimum value, a central value, and a maximum value—​and represents its central calculation, clamped according to its min and max calculations, favoring the min calculation if it conflicts with the max. (That is, given clamp(MIN, VAL, MAX), it represents exactly the same value as max(MIN, min(VAL, MAX))).",
       "type": "function",
       "value": "clamp( <calc-sum>#{3} )"
     },

package/css-view-transitions.json

@@ -6,7 +6,7 @@
   "properties": [
     {
       "name": "view-transition-name",
-      "value": "none | <custom-ident>",
+      "value": "none | auto | <custom-ident>",
       "initial": "none",
       "appliesTo": "all elements",
       "inherited": "no",
@@ -21,9 +21,15 @@
           "type": "value",
           "value": "none"
         },
+        {
+          "name": "auto",
+          "prose": "This should be treated as an invalid value, despite being a valid <custom-ident>. The property value remains unchanged.",
+          "type": "value",
+          "value": "auto"
+        },
         {
           "name": "<custom-ident>",
-          "prose": "The element participates independently in a view transition—as either an old or new element—with the specified view transition name. The value none is excluded from <custom-ident> here.",
+          "prose": "The element participates independently in a view transition—​as either an old or new element—​with the specified view transition name. The value none is excluded from <custom-ident> here.",
           "type": "value",
           "value": "<custom-ident>"
         }

package/mediaqueries-5.json

@@ -487,7 +487,7 @@
             },
             {
               "name": "custom",
-              "prose": "Indicates that the user has indicated wanting a specific set of colors to be used, but the contrast implied by these particular colors is such that neither more nor less match. A user calling for cyan text over a rust background is not—at least in terms of luminosity—expressing a need for particularly high or low contrast, but this is not a lack of a preference either.",
+              "prose": "Indicates that the user has indicated wanting a specific set of colors to be used, but the contrast implied by these particular colors is such that neither more nor less match. A user calling for cyan text over a rust background is not—​at least in terms of luminosity—​expressing a need for particularly high or low contrast, but this is not a lack of a preference either.",
               "type": "value",
               "value": "custom"
             }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@webref/css",
   "description": "CSS definitions of the web platform",
-  "version": "6.10.0",
+  "version": "6.10.2",
   "repository": {
     "type": "git",
     "url": "https://github.com/w3c/webref.git"

package/scroll-animations.json

@@ -315,7 +315,7 @@
         },
         {
           "name": "<dashed-ident>",
-          "prose": "Declares the name of a matching named timeline defined by a descendant—whose scope is not already explicitly declared by a descendant using timeline-scope—to be in scope for this element and its descendants. If no such timeline exists, or if more than one such timeline exists, instead declares an inactive timeline with the specified name.",
+          "prose": "Declares the name of a matching named timeline defined by a descendant—​whose scope is not already explicitly declared by a descendant using timeline-scope—​to be in scope for this element and its descendants. If no such timeline exists, or if more than one such timeline exists, instead declares an inactive timeline with the specified name.",
           "type": "value",
           "value": "<dashed-ident>"
         }

package/selectors.json

@@ -20,7 +20,7 @@
     },
     {
       "name": ":where()",
-      "prose": "The Specificity-adjustment pseudo-class, :where(), is a functional pseudo-class with the same syntax and functionality as :is(). Unlike :is(), neither the :where() pseudo-class, nor any of its arguments, contribute to the specificity of the selector—its specificity is always zero."
+      "prose": "The Specificity-adjustment pseudo-class, :where(), is a functional pseudo-class with the same syntax and functionality as :is(). Unlike :is(), neither the :where() pseudo-class, nor any of its arguments, contribute to the specificity of the selector—​its specificity is always zero."
     },
     {
       "name": ":has()",