These messages can be viewed using the adb logcat command. In addition to the console messages output through WebIDE, there may also be messages relating to the validation of the extension’s manifest.json files. Viewing manifest validation messages using the console You can review and modify the document's HTML and CSS in Inspector, as you would with any webpage.įor more details on using the web developer tools, see Firefox Developer Tools. First, click the page select icon ( ) to open the HTML document you want to inspect. To inspect the popup's HTML and CSS, use Inspector. Any messages logged by your code display in Console. In the Debugger you can set breakpoints, step through code, modify the extension's state, and do everything else you'd expect to be able to do in a debugger. Now you can access any of the JavaScript in your extension.Ĭontent scripts can be reached and debugged when connected to the main process or to a tab target where a content script is running. Load a page in which your extension exercises. You do this using the split console, press esc to activate this mode. The web developer toolbox displays in Debugger.įor much of the debugging work, it's useful to be able to view Console with Inspector or Debugger. Click your device in the left-hand column and scroll down to find Processes in the list of active features in the browser.Ĭlick Inspect next to Main Process. You will need to have at least one tab opened in order for your extension to load. Now start your extension on the Android device using web-ext run. If prompted, allow the incoming connection on your Android device. Your device is listed in the left-hand column, click Connect. With your device connected over USB or Wi-Fi, open about:debugging and enable the device connection. Using web development tools to debug your extension

To make use of these features, first set up Firefox remote debugging over USB or Wi-Fi. You can debug your extension in the web developer tools and view any manifest.json validation messages using adb logcat.

As a workaround, we recommend that you temporarily change the extension to open the popup extension page into a tab to be able to inspect it.

Removing your extension from distributionĬurrently, you cannot inspect the markup of Fenix's browserAction popups using the Firefox Developer Tools Inspector (see bug 1637616).

Will I ever be able to sell through AMO?.

Use plain language in any privacy policy or license agreement.

Select the right platforms and versions.

The add-on description can be longer, but not too long.

Focus on key features in your screenshots.

Make sure your summary is just long enough.

Free mozilla firefox for android