Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

cannot debug addon

  • 5 Antworten
  • 1 hat dieses Problem
  • 18 Aufrufe
  • Letzte Antwort von admin101

admin101
admin101
more options

Hi,

Thanks to Mozilla for continuing to develop such a clean browser, with movies made of GIF instead of much larger files.

So we have developed an extension or add-on for many years using the same method. But recently ( maybe I forgot ), with a new developer profile, I am unable to edit any files because the .xpi extension in the extensions folder, is compressed and cannot be navigated in a file Explorer.

In the past, I just install the extension and change the file extension from .xpi to .zip, and then extract into a folder with the same name. Then delete the .xpi/.zip folder, and the new folder acts as a pointer for the same instance of installation. And I can just modify the files in that folder usually and I don't need to restart the browser to see the changes. But lately I cannot do this.

What is the best way to debug the add-on with the least number of steps?

Thanks,

Josh

Hi, Thanks to Mozilla for continuing to develop such a clean browser, with movies made of GIF instead of much larger files. So we have developed an extension or add-on for many years using the same method. But recently ( maybe I forgot ), with a new developer profile, I am unable to edit any files because the .xpi extension in the extensions folder, is compressed and cannot be navigated in a file Explorer. In the past, I just install the extension and change the file extension from .xpi to .zip, and then extract into a folder with the same name. Then delete the .xpi/.zip folder, and the new folder acts as a pointer for the same instance of installation. And I can just modify the files in that folder usually and I don't need to restart the browser to see the changes. But lately I cannot do this. What is the best way to debug the add-on with the least number of steps? Thanks, Josh

Ausgewählte Lösung

admin101 said

For example, these days I have to edit the JavaScript file, CTR+S, then open new Mozilla developer edition, open the debugging tab, then click the open temporary add-on, then select the file, check the operation of the add-on.

Once you temporarily load the extension via about:debugging, after modifying any of its source files, you just have to click the Reload button to reload the extension. (See attached screenshot.)

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (5)

Eve
Eve
more options

You should be able to point to a given file inside a folder (unzipped/compressed) with the appropriate contents (manifest.json, js, icon/48.png) to load an addon temporarily, then you can just reload it each time you make changes to those files? per https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension (obviously this isn't your first but details this method)

In about:debugging#/runtime/this-firefox

I think that'd be simplest, but someone might have a better method.

admin101
admin101 Fragesteller
more options

Hi evhenry,

Thanks for the support.

Yes I know about loading the add-on from there, but it just seems quite cumbersome to keep reloading.

Josh

Geändert am von admin101

admin101
admin101 Fragesteller
more options

For example, these days I have to edit the JavaScript file, CTR+S, then open new Mozilla developer edition, open the debugging tab, then click the open temporary add-on, then select the file, check the operation of the add-on.

Previously, after editing the JavaScript file, CTR+S, ALT+TAB to Mozilla developer edition, then check the operation of the add-on.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Ausgewählte Lösung

admin101 said

For example, these days I have to edit the JavaScript file, CTR+S, then open new Mozilla developer edition, open the debugging tab, then click the open temporary add-on, then select the file, check the operation of the add-on.

Once you temporarily load the extension via about:debugging, after modifying any of its source files, you just have to click the Reload button to reload the extension. (See attached screenshot.)

admin101
admin101 Fragesteller
more options

admin101 said

For example, these days I have to edit the JavaScript file, CTR+S, then open new Mozilla developer edition, open the debugging tab, then click the open temporary add-on, then select the file, check the operation of the add-on. Previously, after editing the JavaScript file, CTR+S, ALT+TAB to Mozilla developer edition, then check the operation of the add-on.

Thanks! That's very helpful.