Chris H-C
Chris H-C
When horizontal, pinned tabs would remain in the tab bar in a fixed partition while the rest of the tabs were scrolled. In VerticalTabs they don't. I think it'd be...
As requested in https://github.com/amtunlimited/average-response/blob/71a4e9653d13f888f5158fc1d8226dc37c8bee3e/script.js#L32 you can find the API's documentation here: https://github.com/mozilla/python_mozaggregator/#api
mozilla-central is moving from hg to git sometime in the medium term. When that happens, we can expect hgweb to either stop or change, which will interfere with the Telemetry...
Expiry reminder bugs and emails typically look something like `Remove or update probes expiring in Firefox 112: WEBAUTHN_*` I posit they'd be catchier and more informative if they include the...
See discussion in #376, but in summary: Metrics from `browser/base/metrics.yaml` made it into `org_mozilla_firefox` via the dependency on `gecko`, but that metrics file will contain only metrics that are sent...
The emails we get on the mailing list are informative, but I think they could be better. I think it'd be really helpful if the emails contained: * Front matter...
[Presently we order](https://firefox-source-docs.mozilla.org/toolkit/components/glean/user/new_definitions_file.html#where-do-i-define-new-metrics-and-pings) Firefox on Glean consumers to manually file bugs whenever they add new `metrics.yaml` or `pings.yaml` files to `metrics_index.py`. This isn't the most ergonomic way to deal with...
I'm finding it tricky to read the list of expired metrics in the mail. Here's how it reads, from a recent go 'round: ```` ``` TIME_TO_LOAD_EVENT_END_PRELOAD_MS TIME_TO_LOAD_EVENT_START_NO_PRELOAD_MS blocklist.mlbf_stash_time_oldest TIME_TO_LOAD_EVENT_END_NO_PRELOAD_MS COOKIE_PURGING_TRACKERS_USER_INTERACTION_REMAINING_DAYS...
I think it would be helpful to send on, say, a yearly cadence a brace of emails to owners of permanent (non-expiring) metrics to remind them of which metrics they...
Firefox Desktop defines its crash annotations (present in crash reports sent to https://crash-stats.mozilla.org and optionally "crash" pings sent via Telemetry) in [CrashAnnotations.yaml](https://hg.mozilla.org/mozilla-central/raw-file/tip/toolkit/crashreporter/CrashAnnotations.yaml). Seems like the sort of thing we should...