Skip to content

Latest commit

 

History

History
60 lines (41 loc) · 4.12 KB

browser-specific-issue-tracking.md

File metadata and controls

60 lines (41 loc) · 4.12 KB

Reporting Browser-Specific issues

The W3C WebExtension Community Group and Working Group issue tracker is dedicated to aligning on cross-browser behavior, API proposals and specification changes.

If you encounter a bug or unexpected behavior only occurring in one specific browser, please report it directly to that browser. This document describes the different processes for each browser and what steps to follow. When reporting in multiple locations (like both a forum and issue tracker), make sure to cross-reference them.


Blink / Chromium

If a bug occurs in both Chrome and a Chromium-based browser (for example, Microsoft Edge or Opera), it is best reported to the Chromium bug tracker. If it only appears in a specific Chromium-based browser, report it to the specific browser tracker.

Google Chrome & Chromium

Microsoft Edge

  • GitHub (Preferred): MicrosoftEdge-Extensions Issues
  • In-Browser Feedback: Issues can also be tracked at the Feedback Portal.
  • Contact: You can share feedback reports with ext_dev_support@microsoft.com or on X (Twitter) using the hashtag #edgeextensions.
  • Note: For Edge on iOS, see the WebKit section.

Vivaldi

Opera

Naver Whale


Gecko

Mozilla Firefox


WebKit

Apple Safari

Edge on iOS

Edge on iOS uses the WebKit extension APIs. Make sure to test if the issue also appears in Safari. If it does, the Apple Safari instructions should be followed in addition to reporting the issue on GitHub as mentioned in the Microsoft Edge section.

Orion

DNR issues in Orion often also appear in Apple Safari. Make sure to first check if the issue also happens in Apple Safari and report it there.


Document maintenance

This guide was originally authored in #155. If you found an issue in this document or want to add details, you can open an issue with https://github.com/w3c/webextensions/issues/new/choose.