Megalist is a feature where a user can manage their personal data from one place. This is available as an entry in the browser sidebar by adding the pref “browser.megalist.enabled”.
This initial patch includes:
* Displaying logins, credit cards, and addresses in the browser sidebar
* Editing login, credit card, or address
* Rendering site favicons
* Importing logins
* Copying field values
* Filtering records using search text
* Conceal / reveal password
What’s not included:
* Creating a login, credit card, or address
* Deleting
* Sorting records
* Tests
* Documentation
**Architecture**
At a high-level, the relationship between modules can be outlined as such:
DataSource <—> Aggregator <—> View Model <—> View
The **MegalistViewModel** is responsible for providing the data that will be displayed in the view (MegalistView). It is responsible for organizing data accessed from the Aggregator into a list and send this data as “snapshots” to the view. The MegalistParent/Child actors facilitate the communication between the browser context and content.
The **Aggregator** is responsible for connecting a data source to the ViewModel. It can connect multiple data sources to the ViewModel.
The **data source **defines how the data is fetched and represented in Megalist as a group of “lines”. At this level, we define specific functionality on what commands can act on this data and what is exposed to the ViewModel.
Differential Revision: https://phabricator.services.mozilla.com/D202678
- 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
This patch removes the custom post-startup-delay for the sina pageload tests on android to fix the high frequency intermittent we're seeing. This change was originally added after condprof was disabled. We've since re-enabled it, so we can remove this change.
Differential Revision: https://phabricator.services.mozilla.com/D205566
Now that Firefox's Android UA string includes "Linux" to more closely match Chrome's Android UA string (to fix some webcompat issues), tests need to check for "Linux && !Android" to distinguish desktop Linux from Android.
These tests' Linux checks were added in bug 1849108.
Differential Revision: https://phabricator.services.mozilla.com/D204324
Values were static_casted where required. Some functions in WritingModes.h were
rewritten such that bitwise operations aren't being used. Added static_casts to
avoid (debug) build errors from debugging printfs in layout/tables/nsCellMap.cpp.
Differential Revision: https://phabricator.services.mozilla.com/D205510
When turning the feature gating pref on and running tests, it revealed one oversight:
When test files are run and we reset telemetry, we don't properly unload the internal
state of CategorizationRecorder. Doing so means that we can keep the "threshold" variable
in a non-zero state despite reseting all telemetry, which can cause submit() to fire when
we don't expect it.
Differential Revision: https://phabricator.services.mozilla.com/D205507
This patch adds a toolchain task for pdfs to be used in the talos pdfpaint test. This is done with a fetch task for the Mozilla pdf.js repository, and a toolchain task that gathers the pdfs from that repository. The toolchain task also handles downloading additional PDFs from files that contain links to them. The additional shell script is used to run the script that gathers the PDFs and allow us to use the in-tree redo python package.
Differential Revision: https://phabricator.services.mozilla.com/D204903
* Add light-dark transformer for generating web CSS
* Use value object in design-tokens.json
* Add HCM media queries to built CSS
* Add MPL license and how to edit file header
* Strip '-default' from token names and values
* Refactor generated media query placement within file.
* generate multiple CSS files from a single JSON file.
* add the :host(.anonymous-content-host) selector to the built CSS
* Output tokens in pre-defined order
* Generate CSS layer declarations and relevant selectors
* Sort tokens by t-shirt size and state semantically not alphabetically
* Add remaining tokens to design-tokens.json
* Add design tokens JSON docs
---------
Co-authored-by: Jules Simplicio <jsimplicio@mozilla.com>
Co-authored-by: Hanna Jones <hjones@mozilla.com>
Co-authored-by: Mark Striemer <mstriemer@mozilla.com>
Co-authored-by: Tim Giles <tgiles@mozilla.com>
Differential Revision: https://phabricator.services.mozilla.com/D204108
We have shipped them for more than 3 months and we don't have issue
right now. Chromium also removed the flags, so it should be fine to drop
them to make the code simpler.
Differential Revision: https://phabricator.services.mozilla.com/D205615
The asserts added in the first patch turned up this existing problem.
AllocChars takes a context so is assumed to report an error on failure.
Differential Revision: https://phabricator.services.mozilla.com/D205553
Jan announced changes to the module in Dec 2023:
https://groups.google.com/a/mozilla.org/g/governance/c/pXQkIm4V8so/m/FNBN0ForAAAJ
I'm reflecting these changes for Jan of:
- Jari is an IDB peer and so is added to mots.yaml
- Bevis is moved to an emeritus peer and this was the last active use of his
anchor his identifier so I removed it.
- I see from the docs that anchors can be used in the emeritus list but this
seems rarely used and the docs provide no guidance on when this is
appropriate and I didn't see this until after I'd made the changes.
- :baku is moved to emeritus by name.
- He actually is used by anchor in other places?
Differential Revision: https://phabricator.services.mozilla.com/D205643
Substitute
use-system-python: false
by
use-python: default
or if one wants to use a different version (available by taskcluster,
i.e. 3.11 as of this commit)
use-python: X.Y
Differential Revision: https://phabricator.services.mozilla.com/D204951
When running `mach try fuzzy` locally, notarization jobs end up in the
full graph, because level isn't forced to 1. As part of try's decision
task though, they're filtered out in the mac_notarization transforms.
Adding them to UNCOMMON_TRY_TASK_LABELS means they won't be selected
at least in the non-`--full` case.
Differential Revision: https://phabricator.services.mozilla.com/D205693
