We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Where are the extension button locations stored?

  • 2 Mbohovái
  • 0 oguereko ko apañuãi
  • 1 Hecha
  • Mbohovái ipaháva tln3

more options

I'm wondering where the buttons for extensions/add-ons have their locations stored? I.e. I might have a tab-renamer extension button on one row, and firefox relay, privacy mode, and adblocker on another row. Obviously what row and what positions in the row the buttons occupy(relative index perhaps) are stored, but where?

I'm wondering where the buttons for extensions/add-ons have their locations stored? I.e. I might have a tab-renamer extension button on one row, and firefox relay, privacy mode, and adblocker on another row. Obviously what row and what positions in the row the buttons occupy(relative index perhaps) are stored, but where?

Ñemoĩporã poravopyre

Normally the toolbar customization is stored in the browser.uiCustomization.state pref that you can inspect on the about:config page.

This pref stores its data in JSON format, so you can possibly save this data in a file and open this file in a tab.

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 1

Opaite Mbohovái (2)

more options

Ñemoĩporã poravopyre

Normally the toolbar customization is stored in the browser.uiCustomization.state pref that you can inspect on the about:config page.

This pref stores its data in JSON format, so you can possibly save this data in a file and open this file in a tab.

more options

Thank you very much!