CSS properties: intro sentence in values section part 3 - #44936
Conversation
github-actions
Bot
added
Content:CSS
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Preview URLs (23 pages)
Flaws (15)Note! 16 documents with no flaws that don't need to be listed. 🎉 Found an unexpected or unresolvable flaw? Please report it here. URL:
URL:
URL:
URL:
URL:
URL:
URL:
(comment last updated: 2026-07-29 08:33:07) |
…e/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
editing it elsewhere and don't want conflicts
dipikabh
left a comment
dipikabh
left a comment
There was a problem hiding this comment.
Nice, thank you for making the placement consistent across the property pages!
That said, I believe these changes deviate from the guideline we have at https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Page_structures/Syntax_sections#css_reference_syntax, which advises to place the optional text before "Values". If we're settling on consistently including the "Optional explanation text" inside the "Values section", would you mind updating that guidance as well?
While I like having the lead-in line in "Values", I'd prefer it to not repeat the values and keywords, since they are named again in the list that follows immediately after. The part we want to emphasize is how many values and how they are separated. I've added suggestions inline.
| ### Values | ||
|
|
||
| The `column-rule` property accepts a comma-separated list of values, including: | ||
| This property is specified as a comma-separated list of values, each value being one of the following value types: |
There was a problem hiding this comment.
| This property is specified as a comma-separated list of values, each value being one of the following value types: | |
| This property is specified as a comma-separated list of values. Each value can be one of the following value types: |
| @@ -79,7 +79,7 @@ Generally, `flex-shrink` is used alongside the {{cssxref("flex-grow")}} and {{cs | |||
|
|
|||
| ## Values | |||
There was a problem hiding this comment.
This section needs to be moved before "Description"
| ## Values | |
| ### Values |
| font-language-override: unset; | ||
| ``` | ||
|
|
||
| The `font-language-override` property is specified as the keyword `normal` or a `<string>`. |
There was a problem hiding this comment.
duplicate:
|
|
||
| ### Values | ||
|
|
||
| This property is specified as a `<dashed-ident>`, a `paletter-mix()` function, or one of the following keyword values: |
There was a problem hiding this comment.
The listed values are not just the keywords but also include <dashed-ident> and palette-mix(). Can we update this to:
| This property is specified as a `<dashed-ident>`, a `paletter-mix()` function, or one of the following keyword values: | |
| This property is specified as a single value from the following list: |
|
|
||
| ### Values | ||
|
|
||
| This property is specified as one of the following keyword values or a `dynamic-range-limit-mix()` function: |
There was a problem hiding this comment.
| This property is specified as one of the following keyword values or a `dynamic-range-limit-mix()` function: | |
| This property is specified as a single value from the following list: |
|
|
||
| ### Values | ||
|
|
||
| This property is specified as a `<string>` or the keyword `normal`: |
There was a problem hiding this comment.
| This property is specified as a `<string>` or the keyword `normal`: | |
| This property is specified as a single value from the following list: |
| - One of the shorthand values `strict` or `content` | ||
|
|
||
| The keywords have the following meanings: | ||
| This property is specified as the keyword `none`, `strict`, or `content`, or a space-separated list of keyword values: |
There was a problem hiding this comment.
This info from original looks crucial - "one or more"
| This property is specified as the keyword `none`, `strict`, or `content`, or a space-separated list of keyword values: | |
| This property is specified as a single value (`none`, `strict`, or `content`) or as a space-separated list of one or more of `size` (or `inline-size`), `layout`, `style`, and `paint`, in any order: |
|
|
||
| ### Values | ||
|
|
||
| The `counter-set` property is specified as either a space-separated list of `<custom-ident>` values, each optionally followed by an `<integer>`, or the keyword `none`: |
There was a problem hiding this comment.
| The `counter-set` property is specified as either a space-separated list of `<custom-ident>` values, each optionally followed by an `<integer>`, or the keyword `none`: | |
| This property is specified as either a space-separated list of `<custom-ident>` values, each optionally followed by an `<integer>`, or the keyword `none`: |
| ## Values | ||
|
|
||
| The `flex-shrink` property is specified as a single `<number>`. | ||
| This property is specified as one `<number>` value: |
There was a problem hiding this comment.
| This property is specified as one `<number>` value: | |
| This property is specified as the following value: |
| ### Values | ||
|
|
||
| This property is specified as one keyword, `<color>`, or `url()` with an optional `<color>`: | ||
| This property is specified as a `<color>`, a `url()` optionally followed by a `<color>` or the keyword `none`, or one of the following keyword values: |
There was a problem hiding this comment.
This again mixes "one of the following keyword values" when the list also includes <color>, <url>, and none. The description for <url> already covers the values that can be optionally attached so we can drop that detail from this lead-in prose:
| This property is specified as a `<color>`, a `url()` optionally followed by a `<color>` or the keyword `none`, or one of the following keyword values: | |
| This property is specified as a single value from the following list or as two values when using `<url>`: |
3 participants
CSS properties include a "Values" section.
Sometimes there is an intro to the values. sometimes there isn't.
This is the third PR in an attempt to make things consistent. This PR addresses some of the properties that had no intro sentence in the values section that and didn't need a whole bunch of other work done
continuation of #44833