Closed
Bug 1353123
Opened 8 years ago
Closed 8 years ago
Extend Remote Jar Telemetry so it doesn't expire.
Categories
(Core :: Networking: JAR, enhancement)
Core
Networking: JAR
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: tjr, Assigned: tjr)
References
Details
Attachments
(1 file)
59 bytes,
text/x-review-board-request
|
Details |
We want to disable remote jar loading sometime soon, but the telemetry probe is set to expire in 55. Extend it a little longer.
Comment hidden (mozreview-request) |
Assignee | ||
Updated•8 years ago
|
Attachment #8854114 -
Flags: review?(benjamin)
Comment 2•8 years ago
|
||
Tom what have you learned from the existing data? Is it inconclusive that we need to keep collecting it?
Flags: needinfo?(tom)
Assignee | ||
Comment 3•8 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #2)
> Tom what have you learned from the existing data? Is it inconclusive that we
> need to keep collecting it?
Well, we know it's used in an overwhelmingly tiny number of sessions, .01% or so, and exclusively on Windows.
When we disable it, the probe will tell us if anyone bothers to turn it back on and use it after doing so.
If we don't care about knowing that, I suppose we could let the probe expire (if we also believe we are okay with removing it either now or in a future release.)
Flags: needinfo?(tom)
Comment 4•8 years ago
|
||
I totally don't believe that it's worth measuring how many people turn it back on. Diminishing returns!
Although I'll note that "0.01% of sessions" isn't overwhelmingly tiny in the grand scheme of web compat.
Assignee | ||
Comment 5•8 years ago
|
||
Okay, we'll let it expire then!
Assignee: nobody → tom
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Attachment #8854114 -
Flags: review?(benjamin)
You need to log in
before you can comment on or make changes to this bug.
Description
•