waldner

Same here.

This actually fails with node 12.2.0, see the attached messages. [errors.txt](https://github.com/swillner/netcdf4-js/files/3169249/errors.txt)

Created https://github.com/swillner/netcdf4-js/pull/22.

That is not a listed context for the context menus (see https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus/ContextType), so it'll probably need change at some other level. I will have to investigate.

It looks like the navigation flow is quite elaborate, do you have any preference regarding where you'd like to hook into? https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webNavigation

My preference would be for [webNavigation.onCreatedNavigationTarget](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webNavigation/onCreatedNavigationTarget) or [webNavigation.onBeforeNavigate](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webNavigation/onBeforeNavigate)

Yet another option would be to use the `webRequest` API, which is slightly different (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest)

I'm doing some tests with both the webNavigation and webRequest APIs and I'm getting quite confused by the inconsistency of the results. Will keep experimenting.

So using any of the `webRequest` API methods seems out of the question, as IIUC you want your command to run once when you navigate to a new page; since...

Can you try loading the uncompressed extension in debug mode from this branch: https://github.com/waldner/Firefox-RunWith/tree/feature/navigation ? (export your current config before doing that, if you want to preserve it for later...