Closed Bug 1215235 Opened 5 years ago Closed 4 years ago

Drop support for jar: URIs by default

Categories

(Core :: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
mozilla45
Tracking Status
firefox45 blocking disabled
firefox46 --- disabled
firefox47 --- disabled
firefox48 --- disabled
firefox49 --- disabled
firefox-esr45 --- disabled
firefox50 --- disabled
firefox51 --- disabled
firefox52 --- disabled

People

(Reporter: ehsan, Assigned: baku)

References

Details

(Keywords: dev-doc-complete, site-compat, Whiteboard: [tor 20123][sb?][necko-active])

Attachments

(1 file)

The discussion is happening on dev-platform, this bug tracks the implementation.
Just make sure that you don't break app: at the same time since it's jar:file: in disguise.
Attached patch jar.patchSplinter Review
Attachment #8682618 - Flags: review?(bzbarsky)
Comment on attachment 8682618 [details] [diff] [review]
jar.patch

r=me
Attachment #8682618 - Flags: review?(bzbarsky) → review+
https://hg.mozilla.org/mozilla-central/rev/f38885365d1a
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Depends on: 1255139
for easier reference here is the link to the dev.platform discussion

https://groups.google.com/forum/#!searchin/mozilla.dev.platform/$20jar$3A$20URIs/mozilla.dev.platform/CFd4w8GzdEI/0DDE_cF8BAAJ

Eric, is there a place on MDN (or could their be) that lists out all the upcoming things we might do, or plan to do, that have the possibility of braking web compat or that we know for sure that will?

Getting more web dev's and app developers to look at this kind of centralize resource page, and helping them a way to find their way to the appropriate discussion, and understanding the upcoming schedule for compat breaking changes might be a way of avoiding discovery of incompatibilities *after* we ship and help in the timing and staging of changes like this one.
(In reply to chris hofmann from comment #9)
> Eric, is there a place on MDN (or could their be) that lists out all the
> upcoming things we might do, or plan to do, that have the possibility of
> braking web compat or that we know for sure that will?

That's exactly what I'm working on: https://www.fxsitecompat.com/en-CA/versions/future/
Updating the flags again. We should probably try this again with Firefox 53, given that 52 will be the next ESR.
Given IBM fixed their iNotes issue in May and enterprise users will/should be using Firefox 52 ESR, Firefox 53 shipping in April 2017 could be the new target.
Status: RESOLVED → REOPENED
Flags: needinfo?(amarchesini)
Resolution: FIXED → ---
Whiteboard: [tor 20123]
Whiteboard: [tor 20123] → [tor 20123][sb?]
Whiteboard: [tor 20123][sb?] → [tor 20123][sb?][necko-active]
Kohei, please don't reopen bugs that have patches landed.  If you want to reopen the discussion to drop remote jar: URIs again, please file a new bug.

Also note that the telemetry probe which we have for this <https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-10-19&keys=__none__!__none__!__none__&max_channel_version=release%252F49&measure=REMOTE_JAR_PROTOCOL_USED&min_channel_version=release%252F47&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-09-16&table=0&trim=1&use_submission_date=0> still shows users hitting this in the wild, we will not consider removing this again at this point before that probe drops down to about 0.
Status: REOPENED → RESOLVED
Closed: 5 years ago4 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → FIXED
The patch here has been backed out in Bug 1255139, so this bug should still be open I guess...?
Resolution: FIXED → WONTFIX
See Also: → 1329336
See bug 1329336 for a new attempt at making this change.
You need to log in before you can comment on or make changes to this bug.