Remove or update probes expiring in Firefox 137: FX_URLBAR_PROVIDER_CLIPBOARD_READ_TIME_MS before Gecko version gets increase to 137 on 2025-02-03
Categories
(Firefox :: Address Bar, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: aryx, NeedInfo)
References
Details
(Whiteboard: [probe-expiry-alert][sng])
Attachments
(1 file)
The following Firefox probes will expire in the next major Firefox nightly release: version 137 [1].
FX_URLBAR_PROVIDER_CLIPBOARD_READ_TIME_MS
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
- If one, some, or all of the metrics are still required, please submit a patch to extend their expiry.
If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.
Your Friendly, Neighborhood Telemetry Team
[1] https://wiki.mozilla.org/Release_Management/Calendar
This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.
Updated•29 days ago
|
Updated•29 days ago
|
Comment 1•29 days ago
|
||
From a point of view, this will be unused for a while, as the feature is stalled disabled due to a platform problem (reading large strings from the clipboard causes UI jank).
From another point of view, if we ever solve that technical problem, we'll want this (or a similar probe) to measure long term effects.
Assignee | ||
Comment 2•28 days ago
|
||
browser/components/urlbar/tests/browser/browser_clipboard.js
uses this.
Assignee | ||
Updated•28 days ago
|
Comment 3•25 days ago
|
||
The bug is marked as tracked for firefox136 (nightly). However, the bug still isn't assigned.
:cbellini, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 4•21 days ago
|
||
We are comfortable with this probe expiring, as the related functionality's dev effort is currently paused. We'll re-add it when we resume.
Comment 5•18 days ago
|
||
This is a reminder regarding comment #3!
The bug is marked as tracked for firefox136 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.
Comment 6•14 days ago
•
|
||
(In reply to Chris Bellini (:cbellini) from comment #4)
We are comfortable with this probe expiring, as the related functionality's dev effort is currently paused. We'll re-add it when we resume.
:cbellini next week is the last week of Nightly for Fx136 before central is bumped to Fx137 on merge day.
If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
Could this be assigned?
Comment 7•11 days ago
|
||
This is a reminder regarding comment #3!
The bug is marked as tracked for firefox136 (nightly). We have limited time to fix this, the soft freeze is in 3 days. However, the bug still isn't assigned.
Assignee | ||
Comment 8•9 days ago
|
||
Reminder: This must be fixed by this Friday (Jan 31).
Comment 9•9 days ago
|
||
Pinged cbellini in Slack
Assignee | ||
Comment 10•9 days ago
|
||
Updated•9 days ago
|
Comment 11•4 days ago
|
||
Comment 12•4 days ago
|
||
Comment 13•4 days ago
|
||
bugherder |
Comment 14•3 days ago
|
||
bugherder |
Description
•