• 3ff3442d7933c99269bfe0b1a50425d1b62e7ee7
• Richard Pospesel
• 2021-08-06 16:39:03 +0200
• Bug 40597: Implement TorSettings module
• - migrated in-page settings read/write implementation from about:preferences#tor to the TorSettings module - TorSettings initially loads settings from the tor daemon, and saves them to firefox prefs - TorSettings notifies observers when a setting has changed; currently only QuickStart notification is implemented for parity with previous preference notify logic in about:torconnect and about:preferences#tor - about:preferences#tor, and about:torconnect now read and write settings thorugh the TorSettings module - all tor settings live in the torbrowser.settings.* preference branch - removed unused pref modify permission for about:torconnect content page from AsyncPrefs.jsm Bug 40645: Migrate Moat APIs to Moat.jsm module

• 1222e90d0f0c89eac895848c9332e535e80777a5
• Henry Wilkes
• 2023-04-05 17:23:08 +0100
• fixup! Bug 40597: Implement TorSettings module
• Bug 41608 - Tidy up the TorConnect API for broad error states that the different UI components can share. Rename the `hasBootstrapEverFailed` to `potentiallyBlocked` as a specific failure state. Add the `hasEverFailed` boolean property as a catch-all failure state. Add an `enabled` boolean property, which just maps to whether we own the tor process.

• d6c9dd4fa2331e4a8d98891006baf3c3bc60cecd
• Henry Wilkes
• 2023-04-05 18:03:26 +0100
• fixup! Bug 40597: Implement TorSettings module
• Bug 41608 - Remove unused TorMonitorService.bootstrapErrorOccurred

• 2a8e78df94ff82e4606c87286fb4f233a576f2ab
• Henry Wilkes
• 2023-04-06 10:57:37 +0100
• fixup! Bug 40597: Implement TorSettings module
• Bug 41608 - Add the canBeginBootstrap and canBeginAutoBootstrap properties to determine whether it is possible to enter the corresponding TorConnectState from the current state. Add options to openTorConnect to begin bootstrapping or auto-bootstrapping once opened.