I should have been explicit about my considerations for telemetry;
apologies for not doing so upfront.
The bug for the removal of telemetry code claims usage was 0.01% of
sessions 9 months ago, before the pref was flipped. I think that's fine
in terms of removing things.
I don't think we should re-add telemetry for this because I don't think
it will tell us anything new/useful at this point - it'll just add
delays and keep the code on the next ESR (meaning we'll have to keep it
in mind for the next 1.5 years or so) when we should be getting rid of it.
As Kris already pointed out in his footnote, the most likely group of
people to have enabled this (given 0 public reports on breakage so far,
as far as I'm aware) are people on ESR or otherwise in enterprise
environments, and our collection rates on telemetry in enterprise
environments are unknown, but guaranteed to be low.
~ Gijs
On 12/01/2018 22:05, Tom Ritter wrote:
Telemetry was removed in 55:
https://bugzilla.mozilla.org/show_bug.cgi?id=1358004
You can still query it on tmo for 54... except it seems to give me a JS error.
-tom
On Fri, Jan 12, 2018 at 3:55 PM, Kris Maglione <kmagli...@mozilla.com> wrote:
Do we have telemetry on the usage of the preference or of remote JAR
channels? If not, it shouldn't be hard to add, and would be a lot safer than
guessing[1]. Either way, I definitely agree that it would be nice to get rid
of this.
-Kris
[1]: Except, of course, that it wouldn't tell us much about enterprise
users, who are probably the most likely people to make use of it.
On Fri, Jan 12, 2018 at 09:47:44PM +0000, Gijs Kruitbosch wrote:
Hello,
jar: is an internal protocol that enables loading resources from inside a
jar/zip file . Firefox is the only browser I'm aware of that supports it.
In Firefox 55, due to security concerns, we put using jar: with remote
content (ie loaded over http(s), ftp - anything apart from file://, really)
behind a hidden (ie about:config) preference that is disabled by default (
https://www.fxsitecompat.com/en-CA/docs/2015/jar-protocol-support-has-been-disabled-by-default/
;
https://developer.mozilla.org/en-US/docs/Mozilla/Security/Security_and_the_jar_protocol
; https://bugzilla.mozilla.org/show_bug.cgi?id=1329336 ).
I would like to unship the preference in Firefox 60 and completely remove
support.
When the code was originally written for Firefox 45, 2 years ago, IBM
Notes broke. That was fixed in Notes/Domino 9.0.1 (
http://www.ibm.com/support/docview.wss?uid=swg21978919 ) in May 2016, so a
good 2 and a bit years before 60 will ship. To my knowledge we are not aware
of any other breakage on the (semi-)public web since then. We also
successfully shipped this default-disabled back in August with 55, and it'll
have been 1 year since then before the previous esr (52) stops being
supported.
As a result, I don't expect there to be any significant use of this
preference anymore, nor do I see any good reason not to remove it. The bug
for the removal is https://bugzilla.mozilla.org/show_bug.cgi?id=1427726 .
Please let me know if you have reason to believe remote jar: still has
significant usage to the point that we cannot remove support in Firefox 60.
Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
