Open Bug 1879396 Opened 2 years ago Updated 1 year ago

[meta] End of life the built-in Screenshots extension

Categories

(Firefox :: Screenshots, task, P3)

task

Tracking

()

People

(Reporter: sfoster, Unassigned)

References

Details

(Keywords: meta)

Once the component implementation of Screenshots is shipped and stable, we should remove the built-in extension.

Summary: End of life the built-in Screenshots extension → [meta] End of life the built-in Screenshots extension
Depends on: 1882427
Blocks: 1721741

Sam, is it now time to remove the add-on?

I'm asking because I'm trying to figure out what to do with the screenshots.{download,upload,copy,visible,full_page, custom,element} legacy telemetry scalars (while working on migrating all legacy telemetry scalars to glean in bug 1927093).

Flags: needinfo?(sfoster)

I've taken a quick look at the data and the latest version of Firefox that has sent any data from the screenshot extension in the past week was Fx126 (at least according to main_1pct). This is consistent with a hypothesis that no one has bothered to switch back from the screenshot component since it hit release in June.

(In reply to Florian Quèze [:florian] from comment #1)

Sam, is it now time to remove the add-on?

I'm asking because I'm trying to figure out what to do with the screenshots.{download,upload,copy,visible,full_page, custom,element} legacy telemetry scalars (while working on migrating all legacy telemetry scalars to glean in bug 1927093).

Removing the system extension is a whole thing. I think we're waiting for a gap in the high-priority feature shipping schedule to give this the time and space we think it will need. But I think you can certainly unhook the telemetry in the meantime if that's going to be simpler than porting it over. I don't think its adding much value at this point. We know there's a long tail of users who are still using it, and they are a not-large number and if they've not switched by now, its likely they never will.

Flags: needinfo?(sfoster)
Depends on: 1930150
You need to log in before you can comment on or make changes to this bug.