canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627
edits
Firefox/Go Faster/Releasing an add-on mechanics: Difference between revisions
Firefox/Go Faster/Releasing an add-on mechanics (view source)
Revision as of 18:16, 30 June 2016
, 30 June 2016→Set up a rule in Balrog: Improve channel-prefs.js location
(→Setting up Balrog: Add info about dev server.) |
(→Set up a rule in Balrog: Improve channel-prefs.js location) |
||
| Line 96: | Line 96: | ||
Testing in Firefox: | Testing in Firefox: | ||
* Note: currently system add-ons updates don't apply until you restart Firefox. | * Note: currently system add-ons updates don't apply until you restart Firefox. | ||
* You may need to change <code>/path/to/binary/folder | * You may need to change <code>/path/to/binary/folder/defaults/pref/channel-prefs.js</code> to point to the specified channel (on Mac this would be <code>Name.app/Contents/Resources/defaults/pref/channel-prefs.js</code> | ||
* Add-on manager activity can be monitored by setting <code>extensions.logging.enabled</code> to true. | * Add-on manager activity can be monitored by setting <code>extensions.logging.enabled</code> to true. | ||
* You can force an add-on update with the [https://addons.mozilla.org/en-US/firefox/addon/timer-fire/ timer-fire add-on] | * You can force an add-on update with the [https://addons.mozilla.org/en-US/firefox/addon/timer-fire/ timer-fire add-on] | ||