`action.getPopup()` - Note historic Safari exception in `action.getPopup()` return URL

Open Beginner friendly
#31,057 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
json
Domain
documentation

Research direction

Read the action.getPopup() entry on the MDN page linked in the issue and check the WebExtensions discussion at w3c/webextensions#1142 for the historical behavior and version details. Find the corresponding browser compatibility data entry for this API in the repository and add a note that Safari returned only the path before the relevant version. Done when the Safari compatibility data records that exception with its version.

Written by the indexing model from the issue text.

Description

needs triage
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?

In webExtensions, Safari used to return the path for the browser.action.getPopup() API, as noted here:
https://github.com/w3c/webextensions/issues/1142

What browsers does this problem apply to, if applicable?

Safari

What did you expect to see?

A note stating before safari version x.x, the getPopup method returned just the path.

Did you test this? If so, how?

Manually tested.

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

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/action/getPopup

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

@xeenon FYI

Dominant language
JSON
Stars
5.8k
Forks
2.7k
Avg merge
2d 20h
Merged PRs (30d)
160

Getting set up

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.

More from mdn/browser-compat-data

All issues in mdn/browser-compat-data

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.