Browser-specific issue tracking

[carlosjeurissen]

Introduction
As developers we often encounter browser-specific issues. Due to the nature of this community group and as mentioned by members in the past, this community group might not be ideal for browser-specific issues.

In addition, it can be very useful to have a dedicated issue for each browser for specific feature implementations / issues if we agree on implementing / fixing them to track progress.

Thus, it would be very useful to know the best approach per browser on how to report these issues.

Below I summarize the approach for each browser that I am currently aware of. If this can be confirmed / further completed it would be very welcome for every developer / publisher out there.

Google Chrome
Currently issues can be reported at:
https://bugs.chromium.org/p/chromium/issues/list

Issues are public and have unique identifiers.

For extension questions / discussion there is the Chromium Extensions Google Group.

Mozilla Firefox
Currently issues can be reported at:
https://bugzilla.mozilla.org/enter_bug.cgi?product=WebExtensions

Issues are public and have unique identifiers.

Apple Safari
Since Apple is moving extensions to WebKit, issues can be reported here:
https://bugs.webkit.org/enter_bug.cgi?product=WebKit&component=WebKit%20Extensions

Issues can also be reported using their Feedback Assistant:
https://feedbackassistant.apple.com/
https://developer.apple.com/forums/tags/safari-extensions

Microsoft Edge
Preferred way of reporting issues are on GitHub specifically:
https://github.com/microsoft/MicrosoftEdge-Extensions/issues/

In-browser feedback is also possible which can then be tracked at https://feedbackportal.microsoft.com/feedback/forum/b8da43d5-ef1b-ec11-b6e7-0022481f8472

In addition, said feedback report can be shared with ext_dev_support@microsoft.com or on Twitter with hashtag #edgeextensions for additional exposure.

Opera
Issues can be reported on the forum:
https://forums.opera.com/

Naver Whale
Issues can be reported on the forum:
https://whale.naver.com/en/

Vivaldi
Issues can be reported on the forum:
https://forum.vivaldi.net/

[birtles]

Apple Safari Issues can be reported on the Forum to be public: https://developer.apple.com/forums/tags/safari-extensions

Yet often Apple requests issues to be reported on their Feedback Assistant: https://feedbackassistant.apple.com/

Those issues will be private tho and almost every time there is no response and there is no way to find out if the issue got resolved or see the status of the issue.

I've reported Web Extensions issues in Safari in the WebKit Bugzilla before and at least they seem to have been reflected in the internal radar bug tracking system (e.g. https://bugs.webkit.org/show_bug.cgi?id=232781)

[carlosjeurissen]

I've reported Web Extensions issues in Safari in the WebKit Bugzilla before and at least they seem to have been reflected in the internal radar bug tracking system (e.g. https://bugs.webkit.org/show_bug.cgi?id=232781)

@birtles Thanks for sharing! Updated the main issue to reflect this. It would be good to know which way of submitting issues is preferred by Apple.

[zombie]

Mozilla Firefox
Currently issues can be reported at:
https://bugzilla.mozilla.org/

A more specific place for web extensions in Firefox would be
https://bugzilla.mozilla.org/enter_bug.cgi?product=WebExtensions

[xeenon]

Apple prefers https://feedbackassistant.apple.com/, but mentioning issues on the forums with a feedback ID is helpful too. You can also ping me on Twitter (xeenon) with a feedback ID.

[Rob--W]

I have pinned this issue, because it is useful for others to find where they can report browser-specific issues so that the issue tracker here can focus on topics that need attention from multiple browser vendors (and the wider community).

[mukul-p]

Update for Microsoft Edge Extensions

1. Most preferred - in-browser feedback (and that can be tracked at https://feedbackportal.microsoft.com)
2. (mailto:ext_dev_support@microsoft.com).
3. Alternatively, a developer can also post to https://twitter.com/search?q=%23edgeextensions

PS: We are working on to setup a github forum for tracking issues.

[carlosjeurissen]

Apple prefers https://feedbackassistant.apple.com/, but mentioning issues on the forums with a feedback ID is helpful too. You can also ping me on Twitter (xeenon) with a feedback ID.

Added to the main post. Just to clarify, can https://bugs.webkit.org/ also be used for bugs in extensions but simply not preferred by Apple? Or does https://bugs.webkit.org/ not cover extensions by definition?

[mukul-p]

Update for Microsoft Edge Extensions

1. Most preferred - in-browser feedback (and that can be tracked at https://feedbackportal.microsoft.com)
2. (mailto:ext_dev_support@microsoft.com).
3. Alternatively, a developer can also post to https://twitter.com/search?q=%23edgeextensions

PS: We are working on to setup a github forum for tracking issues.

Hi,
We have added a single github forum specifically for Edge Extension Issues
https://github.com/microsoft/MicrosoftEdge-Extensions/issues/
Thanks