mdn / mdn/browser-compat-data

`html.global_attributes.focusgroup` etc. - missing data

Open Beginner friendly
#30,468 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:chrome data:html needs collector test
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?

There's no data for the focusgroup HTML attribute and related APIs.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Browser)

What did you expect to see?

I'd expect the following keys:

  • api.HTMLElement.focusgroup
  • api.HTMLElement.focusgroupStart
  • api.SVGElement.focusgroup
  • api.SVGElement.focusgroupStart
  • html.global_attributes.focusgroup
  • html.global_attributes.focusgroupstart
Did you test this? If so, how?

No, but Chrome Status reports that it shipped in Chrome 150 and the Edge 150 release notes corroborate. @captainbrosset also reported this in

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Do you have anything more you want to share?

There's no published specification text, only the pull request https://github.com/whatwg/html/pull/11723. ☹️

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

Search the repository for the six requested compatibility keys, then review their surrounding data patterns and the linked Chrome Status and Edge release notes. Add support data for the focusgroup attribute and APIs with the reported Chromium, Chrome 150, and Edge 150 evidence, and verify the dataset checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.