76a8b8897c
This uses the existing `browser.launched_to_handle :: system_notification` event. This is expedient and looks ahead to making the WDBA a background task, where we likely will set the privileged `name` of the toast to `default-browser-agent` or similar. The alternative is to add a `browser.launched_to_handle :: default_browser_agent` event. I started with this and it's simply duplication. The data analysis phase will look almost identical with either implementation: it's either filtering on the event name or on the `name` key in the event extras. Differential Revision: https://phabricator.services.mozilla.com/D179257
27 lines
813 B
INI
27 lines
813 B
INI
[DEFAULT]
|
|
support-files =
|
|
head.js
|
|
../../../../dom/security/test/csp/dummy.pdf
|
|
|
|
[browser_browserGlue_showModal_trigger.js]
|
|
[browser_browserGlue_telemetry.js]
|
|
[browser_browserGlue_upgradeDialog_trigger.js]
|
|
[browser_bug538331.js]
|
|
skip-if = !updater
|
|
reason = test depends on update channel
|
|
[browser_contentpermissionprompt.js]
|
|
[browser_default_bookmark_toolbar_visibility.js]
|
|
[browser_default_browser_prompt.js]
|
|
[browser_initial_tab_remoteType.js]
|
|
https_first_disabled = true
|
|
[browser_quit_disabled.js]
|
|
# On macOS we can't change browser.quitShortcut.disabled during runtime.
|
|
skip-if = os == 'mac'
|
|
[browser_quit_multiple_tabs.js]
|
|
[browser_quit_shortcut_warning.js]
|
|
[browser_startup_homepage.js]
|
|
[browser_system_notification_telemetry.js]
|
|
run-if = os == 'win'
|
|
[browser_to_handle_telemetry.js]
|
|
run-if = os == 'win'
|