1407111 - Tools for debugging WebExtensions using the nativeMessaging API

Status: NEW

(WebExtensions :: General, enhancement, P5)

Description

[Szmozsánszky István [:flaki]]

While trying to get my Estonian ID card working on Arch Linux (https://github.com/open-eid/chrome-token-signing/wiki/Extension) I realized how few affordances are given to the user in terms of debugging what goes wrong in addons using the nativeMessaging API.

Just being able to enable a verbose mode logging the webextension's lifetime events would already be a huge help, due to the inherent complexity of what's happening when the nativeMessaging is used (e.g. is the native messaging native client app accessible? was it launched? what went wrong? etc.).
https://developer.chrome.com/extensions/nativeMessaging#native-messaging-debugging

Comment 1

[Andrew Swan [:aswan]]

Have you seen https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_messaging#Troubleshooting

Do you have specific suggestions for what's missing from the existing browser console logs?

Comment 2

[Firefox Bug Husbandry Bot]

Bulk move of bugs per https://bugzilla.mozilla.org/show_bug.cgi?id=1483958

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.