Changed
* `--color-background-*` are now part of the group of `--background-color` tokens
* `--box-background-color` is now part of the group of `--background-color` tokens as `--background-color-box`
* `--color-canvas` is now part of the group of `--background-color` tokens as `--background-color-canvas`
* `--border-interactive-*` are now part of the group of `--border-color` tokens and consequently now start with `--border-color`
* `--color-error-outline` is now an outline-specific token as `--outline-color-error`
* Comment headings were cleaned up as to follow the existing standard
* Better documentation behind the difference of "Base", "Application", and "Component" tiers in the design tokens documentation
* Tokens files are alphabetized
Removed
* `--outline-color-error` had duplicates in both high contrast mode media queries, so its value under `forced-colors` was removed
* "Base" and "Application" headings in tokens files were removed in order to lean in on the alphabetical order organization of token groups and promote a cleaner file and less confusion
* Documentation was edited down to not incude any guidance that we don't adhere to
* Remove duplicate interactive border color high contrast mode tokens in `tokens-brand.css` in favor of `tokens-shared.css`
* Remove `--button-border-color-primary` duplicate in `tokens-brand.css`
* Remove duplicate `--button-text-color` in `tokens-shared.css`
Differential Revision: https://phabricator.services.mozilla.com/D202767
Firstly, this parameter is actually named remoteTypeOverride and
secondly, it is only valid for about: urls when passed to loadURI
Differential Revision: https://phabricator.services.mozilla.com/D204788
- Adds `CookiesBackupResource`, `FormHistoryBackupResource` and `SessionsStoreBackupResource` classes with measurement methods for those resources.
- Exports `BYTES_IN_KB` and new `bytesToFuzzyKilobytes` methods from `BackupResource`
- Fix filename for `BackupResource` tests.
Differential Revision: https://phabricator.services.mozilla.com/D205254
Optimization strategy that uses the mozlint configuration files to decide
whether or not to run a job.
In order to support Firefox and Thunderbird, when registering the strategy,
the path to mozlint config files is needed.
Differential Revision: https://phabricator.services.mozilla.com/D204685
Had to increase the warning limit as I am not sure what exactly the warning was. Also, `mach lint -l rst toolkit/components/contentrelevancy` reported no issues/warnings.
Differential Revision: https://phabricator.services.mozilla.com/D205606
This change enables the JS_USE_APPLE_FAST_WX option for iOS, but uses the
BrowserEngineKit APIs rather than the pthread_jit APIs which are available on
macOS. It is unclear to me if there are other differences with these APIs which
would need to be handled beyond what has been written so far, as this is just a
naive substitution.
Given these functions are explicitly "inline", it may be desirable at some
point to refactor the code to allow the calls to be made inline within
ProcessExecutableMemory.h, however that was left out-of-scope.
Differential Revision: https://phabricator.services.mozilla.com/D203499
This adds a pref to disable jit compilation by calling JS::DisableJitBackend in
the parent process. This will be used on iOS, where the jit entitlements are
only available for sandboxed content processes.
Differential Revision: https://phabricator.services.mozilla.com/D203498
Content intent of completed DownloadNotification now uses a PendingIntent which launches an Activity directly.
Previously, we launched the Activity indirectly from a BroadcastReceiver, which is less performant and is prohibited by the OS since Android 12.
The download notification test has been modified to mock out the file opening behaviour, as this test is just checking the visuals of the notification rather than the onward journeys.
Add notification trampoline test case that fails before the fix was made & passes after, to cover this bug.
Fix a bunch of lint / detekt things - trailing commas, formatting, javadoc comments
Differential Revision: https://phabricator.services.mozilla.com/D205042
Since the AccessibilityUtils will be able to account for a click on a label elements for radio buttons and checkboxes in the bug 1882380, we can remove the `fail-if` notation from two tests that were previously failing a11y-checks.
Depends on D205112
Differential Revision: https://phabricator.services.mozilla.com/D205116
Some tests are reporting failing a11y_checks while the click is sent to a text leaf within a label of a radio button with an appropriate markup, for example when `span` is clicked in [this case](https://searchfox.org/mozilla-central/rev/9cd4ea81e27db6b767f1d9bbbcf47da238dd64fa/toolkit/components/aboutconfig/test/browser/browser_edit.js#418-424):
```
<label>
<input type="radio" name="type" value="Boolean">
<span data-l10n-id="about-config-pref-add-type-boolean">
Boolean
</span>
</label>
```
We need to add a check in the `findInteractiveAccessible()` method to allow for a label accessible to return its related form control to proceed with the a11y-checks suite, incl. the `assertLabeled` check too.
Test that is affected by this change: `toolkit/components/aboutconfig/test/browser/browser_edit.js`
Differential Revision: https://phabricator.services.mozilla.com/D205112
This patch adds some additional documentation about the tp6-bench test to the Raptor Browsertime docs. At the same time, the description given in the perfdocs config.yml file is updated to better reflect what the test currently does.
Differential Revision: https://phabricator.services.mozilla.com/D203821
