mdn / mdn/browser-compat-data

api.PerformanceObserver.observe - "type" option was added in Safari 13

Open
#24,584 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:safari data:api 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?

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

What information was incorrect, unhelpful, or incomplete?

The information claims that Safari 11 added full support for PerformanceObserver. Safari 11 and 12 had partial support. Safari 13 has full support. Safari 11 and 12 did not support the "type" option.

What browsers does this problem apply to, if applicable?

Safari

What did you expect to see?

Safari 13 has full support for PerformanceObserver. Safari 11/12 has partial support.

Did you test this? If so, how?

I had relied on MDN information when deploying a feature to production, and received a significant error rate from Safari 11/12 customers. This information is verified in https://bugs.webkit.org/show_bug.cgi?id=209216.

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

https://bugs.webkit.org/show_bug.cgi?id=209216

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/PerformanceObserver/observe

MDN metadata
MDN page report details
  • Query: api.PerformanceObserver.observe
  • Report started: 2024-09-30T17:18:15.270Z

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

Open the compatibility-data entry for api.PerformanceObserver.observe referenced by the MDN URL, then compare its Safari data with WebKit bug 209216. Correct the Safari support information so Safari 11 and 12 show partial support and Safari 13 shows full support, then run the repository's data validation checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.