mdn / mdn/browser-compat-data

css.at-rules.counter-style.symbols - add subfeatures for specific `<symbol>` values?

Open
#29,344 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:css needs collector test p3
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

According to @captainbrosset over in https://github.com/web-platform-dx/web-features/pull/3881#discussion_r2986429856:

Safari is the only browser to support images as symbols. Other browsers only support text/ident symbols. It would be great to mint a new feature just for image counter styles. I guess that would require a sub-feature in BCD.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

A subfeature for each of:

  • <image>
  • <string>
  • <custom-ident>
Did you test this? If so, how?

I didn't test this, but I trust @captainbrosset. 😄

We'll need a test case here, probably.

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

https://drafts.csswg.org/css-counter-styles/#typedef-symbol

Do you have anything more you want to share?

No response

MDN URL

No response

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 the existing css.at-rules.counter-style.symbols compatibility data and the CSS Counter Styles typedef specification linked in the issue. Confirm the browser-support distinctions for , , and , then add a test case and verify that the resulting subfeatures represent those distinctions.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.