Closed Bug 1694849 Opened 3 years ago Closed 3 years ago

Remove or update probes expiring in Firefox 89: devtools.accessibility.tabbing_order_activated

Categories

(DevTools :: Accessibility Tools, task)

task

Tracking

(firefox-esr78 unaffected, firefox86 unaffected, firefox87 unaffected, firefox88- unaffected, firefox89+ fixed)

RESOLVED FIXED
89 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox86 --- unaffected
firefox87 --- unaffected
firefox88 - unaffected
firefox89 + fixed

People

(Reporter: telemetry-probes, Assigned: morgan)

References

Details

(Whiteboard: [probe-expiry-alert])

Attachments

(2 files)

The following Firefox probes will expire in the next major Firefox nightly release: version 89 [1].

devtools.accessibility.tabbing_order_activated

What to do about this:

  1. 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).
  2. If one, some, or all of the metrics are still required, please submit a Data Collection Review [2] and patch to extend their expiry. There is a shorter form for data collection renewal [3].

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
[2] https://wiki.mozilla.org/Firefox/Data_Collection
[3] https://github.com/mozilla/data-review/blob/master/renewal_request.md

This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.

This will let the test devtools/client/accessibility/test/browser/browser_tabbing_order_telemetry.js fail when the Gecko version number gets increased to 89 on 2021-03-22. Please extend the probe or remove it before that date.

Asa, do we still want telemetry concerning when the tabbing order tool in the Dev Tools A11y Panel is activated? On one hand, it's useful to have the data so we know whether it's getting usage. On the other hand, we don't have anyone staffed to work on it anyway, which may make it hard to justify extending the probe to the data stewards.

Flags: needinfo?(jteh) → needinfo?(asa)

(In reply to James Teh [:Jamie] from comment #2)

Asa, do we still want telemetry concerning when the tabbing order tool in the Dev Tools A11y Panel is activated?

I don't think we'll be actively monitoring this because, as you said, there's no one working in this area right now. I think we can let it expire and if we pick up the investment in dev tools in the future, we can always add it back if it seems needed then.

Flags: needinfo?(asa)

Given the fix needs to have landed before the central-to-beta merge next Monday, what is the plan here: Test removal or test disabling?

Flags: needinfo?(jteh)
Assignee: nobody → aryx.bugmail
Status: NEW → ASSIGNED
Pushed by archaeopteryx@coole-files.de:
https://hg.mozilla.org/mozilla-central/rev/7bff3dc37b07
disable devtools a11y's browser_tabbing_order_telemetry.js because its probe expires with switch to Firefox 89. a=test-disabling

Morgan, might you have cycles to deal with this? We need to:

  1. Remove the test;
  2. Update the Dev Tools A11y Panel code to remove the telemetry submission for this probe; and
  3. Remove the probe from Scalars.yaml.
Flags: needinfo?(jteh) → needinfo?(mreschenberg)

Yep I'll take this :) thanks for the flag

Flags: needinfo?(mreschenberg)
Assignee: aryx.bugmail → mreschenberg
Attachment #9211617 - Attachment description: WIP: Bug 1694849: Remove devtools.accessibility.tabbing_order_activated probe and associated test r?Jamie → Bug 1694849: Remove devtools.accessibility.tabbing_order_activated probe and associated test r?Jamie
Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/41dac4a019c3
Remove devtools.accessibility.tabbing_order_activated probe and associated test r=Jamie
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Keywords: leave-open
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: