mdn / mdn/browser-compat-data

css.properties.list-style-type - incorrectly reports support for many keys

Open
#24,545 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:css help wanted p2
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

The list-style-item supports predefined list style types, custom strings, and identifiers for custom counters. The collector is checking for support using CSS.supports('list-style-item', 'value'), and because of the breadth of values, this will return true for anything passed as the value. This means that the some of the changes introduced by https://github.com/mdn/browser-compat-data/issues/4148 are not accurate.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

The following are NOT in the spec as predefined list style types. These should not be marked as standard-track, likely should be marked as deprecated, and the support should be reevaluated.

  • afar
  • amharic
  • amharic-abegede
  • asterisks
  • binary
  • ethiopic
  • ethiopic-abegede
  • ethiopic-abegede-am-et
  • ethiopic-abegede-gez
  • ethiopic-abegede-ti-er
  • ethiopic-abegede-ti-et
  • ethiopic-halehame
  • ethiopic-halehame-aa-er
  • ethiopic-halehame-aa-et
  • ethiopic-halehame-am
  • ethiopic-halehame-am-et
  • ethiopic-halehame-gez
  • ethiopic-halehame-om-et
  • ethiopic-halehame-sid-et
  • ethiopic-halehame-so-et
  • ethiopic-halehame-ti-er
  • ethiopic-halehame-ti-et
  • ethiopic-halehame-tig
  • footnotes
  • hangul
  • hangul-consonant
  • lower-hexadecimal
  • lower-norwegian
  • octal
  • oromo
  • sidama
  • somali
  • tigre
  • tigrinya-er
  • tigrinya-er-abegede
  • tigrinya-et
  • tigrinya-et-abegede
  • upper-greek
  • upper-hexadecimal
  • upper-norwegian
  • urdu
Did you test this? If so, how?

Tested CSS.supports in Safari, Chrome, Firefox.

Also tested individual values, and some are actually supported, despite not being in the spec.
https://codepen.io/jamessw/pen/mdNJVVN

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

https://drafts.csswg.org/css-lists-3/#text-markers
https://drafts.csswg.org/css-counter-styles-3/#predefined-counters

Do you have anything more you want to share?

Surfaced in https://github.com/web-platform-dx/web-features/pull/1764

BCD URL

https://github.com/mdn/browser-compat-data/blob/main/css/properties/list-style-type.json

MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/list-style-type#browser_compatibility

MDN metadata

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting css/properties/list-style-type.json and the linked CSS Lists and CSS Counter Styles specifications. Review the support data for the listed values, using the reported CSS.supports behavior and related web-platform-dx pull request as context. Done means non-predefined values have appropriate status and support data based on the specification and browser behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.