Bug 1754441 Comment 24 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Verified the fix on the latest Nightly (100.0a1/20220328213646) under Windows 10 x64, Ubuntu 16.04 LTS and macOS 11.3.1.

InstallTrigger and InstallTrigger.install are currently controlled by new about:config prefs -  “extensions.InstallTrigger.enabled” and “extensions.InstallTriggerImpl.enabled” set by default to “true”.

Flipping “extensions.InstallTrigger.enabled” to false will hide InstallTrigger global completely and flipping “extensions.InstallTriggerImpl.enabled” to false will make InstallTrigger global to be still visible but set to null.

Corresponding deprecation warning messages are logged to console when accessing the deprecated features:
- “InstallTrigger is deprecated and will be removed in the future” when accessing InstallTrigger
- “InstallTrigger.install() is deprecated and will be removed in the future. For more help https://extensionworkshop.com/documentation/publish/self-distribution/ when accessing InstallTrigger.install

Telemetry is properly collected when accessing the deprecated features:
- Accessing the InstallTrigger global collects telemetry in the following two histograms:
USE_COUNTER2_DEPRECATED_InstallTriggerDeprecated_PAGE USE_COUNTER2_DEPRECATED_InstallTriggerDeprecated_DOCUMENT
- Accessing the InstallTrigger.install methods collects telemetry in the following two histograms:
USE_COUNTER2_DEPRECATED_InstallTriggerInstallDeprecated_PAGE USE_COUNTER2_DEPRECATED_InstallTriggerInstallDeprecated_DOCUMENT

The new prefs are properly shown in both about:support and about:telemetry once changed from their default values

The prefs can also be properly set/reverted via the RemoteSettings “main/addons-manager-settings” collection with the same expected results as when manually setting the prefs.
Verified the fix on the latest Nightly (100.0a1/20220328213646) under Windows 10 x64, Ubuntu 16.04 LTS and macOS 11.3.1.

InstallTrigger and InstallTrigger.install are currently controlled by new about:config prefs -  “extensions.InstallTrigger.enabled” and “extensions.InstallTriggerImpl.enabled” set by default to “true”.

Flipping “extensions.InstallTrigger.enabled” to false will hide InstallTrigger global completely and flipping “extensions.InstallTriggerImpl.enabled” to false will make InstallTrigger global to be still visible but set to null.

Corresponding deprecation warning messages are logged to console when accessing the deprecated features:
- “InstallTrigger is deprecated and will be removed in the future” when accessing InstallTrigger
- “InstallTrigger.install() is deprecated and will be removed in the future. For more help https://extensionworkshop.com/documentation/publish/self-distribution/" when accessing InstallTrigger.install

Telemetry is properly collected when accessing the deprecated features:
- Accessing the InstallTrigger global collects telemetry in the following two histograms:
USE_COUNTER2_DEPRECATED_InstallTriggerDeprecated_PAGE 
USE_COUNTER2_DEPRECATED_InstallTriggerDeprecated_DOCUMENT
- Accessing the InstallTrigger.install methods collects telemetry in the following two histograms:
USE_COUNTER2_DEPRECATED_InstallTriggerInstallDeprecated_PAGE 
USE_COUNTER2_DEPRECATED_InstallTriggerInstallDeprecated_DOCUMENT

The new prefs are properly shown in both about:support and about:telemetry once changed from their default values

The prefs can also be properly set/reverted via the RemoteSettings “main/addons-manager-settings” collection with the same expected results as when manually setting the prefs.

Back to Bug 1754441 Comment 24