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 practice, we have never enabled showing the "Recent" list in the Jump
List, and have only ever shown "Frequent" by default. For now, we only
implement "Frequent".
The "Frequent" SQL query was derived by examining
nsNavHistory::ConstructQueryString and deriving the resulting SQL
query string that the original frequent visits query was using.
This is as opposed to using the actual original buildFrequent
routine, as that uses deprecated Places APIs.
Differential Revision: https://phabricator.services.mozilla.com/D189406
In practice, we have never enabled showing the "Recent" list in the Jump
List, and have only ever shown "Frequent" by default. For now, we only
implement "Frequent".
The "Frequent" SQL query was derived by examining
nsNavHistory::ConstructQueryString and deriving the resulting SQL
query string that the original frequent visits query was using.
This is as opposed to using the actual original buildFrequent
routine, as that uses deprecated Places APIs.
Differential Revision: https://phabricator.services.mozilla.com/D189406
In practice, we have never enabled showing the "Recent" list in the Jump
List, and have only ever shown "Frequent" by default. For now, we only
implement "Frequent".
The "Frequent" SQL query was derived by examining
nsNavHistory::ConstructQueryString and deriving the resulting SQL
query string that the original frequent visits query was using.
This is as opposed to using the actual original buildFrequent
routine, as that uses deprecated Places APIs.
Differential Revision: https://phabricator.services.mozilla.com/D189406
The patch add a CookieBannerExceptionCleaner and a
CookieBannerExecutedRecordCleaner to ClearDataService. The cleaners
clear the cookie banner handling data. We will also clear the executed
record when cleaning cookies or dom storage so that the cookie banner
handling will run again after cleaning.
Differential Revision: https://phabricator.services.mozilla.com/D190764
The patch add a CookieBannerExceptionCleaner and a
CookieBannerExecutedRecordCleaner to ClearDataService. The cleaners
clear the cookie banner handling data. We will also clear the executed
record when cleaning cookies or dom storage so that the cookie banner
handling will run again after cleaning.
Differential Revision: https://phabricator.services.mozilla.com/D190764
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
