api.Document.browsingTopics - The Topics API is not supported in Edge
Nobody has claimed this yet.
- 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?
Edge's support for the Topics API follows Chrome's. This is incorrect.
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
What did you expect to see?
The API surface might be exposed, but Edge does not run models or expect data to be returned. The calls are no-op.
Did you test this? If so, how?
No. I talked directly to my colleague on the Edge team who works on this area of the code.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/Topics_API
MDN metadata
MDN page report details
- Query:
api.Document.browsingTopics - Report started: 2025-11-24T08:28:00.688Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the BCD entry queried as api.Document.browsingTopics from the linked MDN page, and review how Edge is represented alongside Chromium browsers. Done means the compatibility data no longer implies that Edge functionally supports the Topics API, reflecting the reported no-op behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100