Assumption: Browser Usage Telemetry (ideally) records only and all interesting
interactions with Firefox Desktop's UI, and preserving syntax and semantics
when instrumenting using events is valuable.
Value this provides over existing keyed scalars:
* Order of operations (did three tabs open and then three tabs close, or did
a single tab open-close three times?)
* Flow control (several atomic interactions combine to a user task. flow_id
grouping allows us to see that easily in analysis. e.g. Open a tab, open
prefs, privacy prefs, change a setting.)
* Glean
This is aiming for prototype quality and a prototype lifetime, to see if it's
worth investing more than just a week or two into.
Differential Revision: https://phabricator.services.mozilla.com/D207908
The current process creates the OpenSearchEngine and gets it to load its data. Once the data is loaded,
it notifies the SearchService that is ready to be added.
This changes the structure so that the SearchService loads the data, creates the engine and then adds it
straight away.
This also means that the contextual search provider can be simplified and doesn't need to tell the engine
not to add itself to the SearchService.
Differential Revision: https://phabricator.services.mozilla.com/D198814
Can be tested locally using this snippet (which I think I took from a test...):
```js
let addonId = "test";
let policy = new WebExtensionPolicy({
name: "Scapegoat",
id: addonId,
mozExtensionHostname: Services.uuid.generateUUID().number.slice(1, -1),
baseURL: "file:///",
allowedOrigins: new MatchPatternSet([]),
localizeCallback() {},
});
policy.active = true;
ProcessHangMonitor.showNotification(window, { addonId, scriptBrowser: { browsingContext: { watchedByDevTools: false }} });
```
Depends on D194315
Differential Revision: https://phabricator.services.mozilla.com/D194316
Can be tested locally using this snippet (which I think I took from a test...):
```js
let addonId = "test";
let policy = new WebExtensionPolicy({
name: "Scapegoat",
id: addonId,
mozExtensionHostname: Services.uuid.generateUUID().number.slice(1, -1),
baseURL: "file:///",
allowedOrigins: new MatchPatternSet([]),
localizeCallback() {},
});
policy.active = true;
ProcessHangMonitor.showNotification(window, { addonId, scriptBrowser: { browsingContext: { watchedByDevTools: false }} });
```
Differential Revision: https://phabricator.services.mozilla.com/D194316
Can be tested locally using this snippet (which I think I took from a test...):
```js
let addonId = "test";
let policy = new WebExtensionPolicy({
name: "Scapegoat",
id: addonId,
mozExtensionHostname: Services.uuid.generateUUID().number.slice(1, -1),
baseURL: "file:///",
allowedOrigins: new MatchPatternSet([]),
localizeCallback() {},
});
policy.active = true;
ProcessHangMonitor.showNotification(window, { addonId, scriptBrowser: { browsingContext: { watchedByDevTools: false }} });
```
Differential Revision: https://phabricator.services.mozilla.com/D194316
As of 11amPT December 7, Contextual Services is now looking exclusively at
Glean-sent data for Firefox versions 116+. (See DSRE-1489)
Differential Revision: https://phabricator.services.mozilla.com/D195910
We intentionally turn off a11y_checks for these click events, because the test is checking the telemetry functionality and the following 3 clicks are targeting disabled controls to test the changes in scalars (for more refer to the bug 1864576 comment 2 and bug 1854999 comment 4).
Also, we are adding the test `label` to the custom widget `12foo` to satisfy the a11y_check expecting to click on a control with an accessible name.
Since the test file is now passing, we are removing the `fail-if` notation that was added by the bug 1854506 before the investigation in the meta bug 1854507.
Differential Revision: https://phabricator.services.mozilla.com/D195595
In an effort to understand if data collected via the Geckoview Streaming
API differs materially from that collected in Glean, we will implement
some temporary data collections that cover the existing use cases of the
former.
Differential Revision: https://phabricator.services.mozilla.com/D191119
We are working on [enabling Tier 2 a11y-checks to ensure our products have basic accessibility built-in (bug 1692110)](https://bugzilla.mozilla.org/show_bug.cgi?id=1692110) and before that, we need to prepare the existing code base. While we triage and investigate existent tests that would fail once the a11y-checks are enabled in the CI, we are going to fail-if the failing tests altogether and then handle each one of them individually.
This task is to add `fail-if` condition of the failing tests while we continue investigation into the reasons these tests failed and to be able to backtrack these tests once they're resolved.
Related bugs:
- Disabling tests: meta bug 1848402
- Investigation and remediation for components with disabled tests: meta bugs 1848394 and 1854227, Tabbed Browser-specific meta bug 1854507
- Explore capturing click events for a11y_checks: bug 1692110
Depends on D188914
Differential Revision: https://phabricator.services.mozilla.com/D188915
We are working on [enabling Tier 2 a11y-checks to ensure our products have basic accessibility built-in (bug 1692110)](https://bugzilla.mozilla.org/show_bug.cgi?id=1692110) and before that, we need to prepare the existing code base. While we triage and investigate existent tests that would fail once the a11y-checks are enabled in the CI, we are going to skip the failing tests altogether and then handle each one of them individually.
This task is to skip with `fail-if` condition of the failing tests while we continue investigation into the reasons these tests failed and to be able to backtrack these tests once they're resolved.
Related bugs:
- Disabling tests: meta bug 1848402
- Investigation and remediation for components with disabled tests: meta bugs 1848394 and 1854227, Tabbed Browser-specific meta bug 1854507
- Explore capturing click events for a11y_checks: bug 1692110
Differential Revision: https://phabricator.services.mozilla.com/D188915
