Closed Bug 1359310 Opened 3 years ago Closed 3 years ago

Decide which browser versions we will support: FFx, Chrome, Edge, IE (and mobile?)

Categories

(bugzilla.mozilla.org :: User Interface, enhancement)

Production
enhancement
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: emceeaich, Assigned: emceeaich)

References

Details

FFx should probably track latest ESR version. 

Need usage stats for FFx, Chrome, Edge, and IE.
:atoll, does webops have a distribution of UA types and versions coming to Mozilla web properties?
Flags: needinfo?(rsoderberg)
Webops doesn't run any useragent analyses of production traffic; that's all handled by the various other teams. You might reach out to Matt Pressman or Natalie though for metrics analysis, and cc :jgmize in case this is something we have data about for Bedrock visits.
Flags: needinfo?(rsoderberg)
Proposing:

Firefox Desktop:

ESR, Nightly, Beta, Release, Previous

Chrome Desktop:

Release, Previous, Canary

Edge:

Release, Previous

IE: 

11

Mobile and other browsers:

No guarantees of support are made at this time. 

----

Questions:

What about linux distributions of Firefox? Are there versions not listed which we would need to support?
Do we really have to support ESR? Maybe some enterprise users are using it, but most SaaS like Google Apps or Office 365 only support the current (and previous) Release version.
I strongly encourage NOT supporting Nightly. Yes, the site will work, but Nightly often breaks when exposed to otherwise-normal web content, and we should not under any circumstance be *targeting* support for Nightly users nor taking extra steps to support them.

I'm fine with ESR, though; it's no worse than IE11, at the very least.
(In reply to Kohei Yoshino [:kohei] from comment #4)
> Do we really have to support ESR? Maybe some enterprise users are using it,
> but most SaaS like Google Apps or Office 365 only support the current (and
> previous) Release version.

I'd give weight to Kohei's opinion here, site compatibility is something he has a longitudinal view on.
I also think we should support ESR solely because BMO is the bug tracker into which we ask ESR users to file ESR bugs, so if BMO doesn't support ESR, then that complicates matters unexpectedly.
I think I can summarize everyone's concerns here with a priority list of support:

Tier 1: Current versions of Firefox, Chrome, Edge, and Safari
Tier 2: Current-1 versions of the same + Firefox ESR. If something makes bugzilla totally unusable that is not good, if it is inconvenient we don't fix it.
Tier 3: Old browsers (pre-ESR firefox, IE before Edge). If it works, that's cool. If it doesn't work, we don't have the resources to fix it.
Dylan: +1

I'd just change Tier 3 to: other browsers and versions.

Removing themes will make it easier to support mobile. 

Let me run this past marketing to make sure we're consistent and I think we're good.

Once that's done, we can update the github repo, the wiki, and the read the docs.
After discussing with others, let's move Nightly and Beta to Tier 2 since devs are using them.
Final version:

Tier 1: Current and Current-1 versions of Firefox, Chrome, Edge, and Safari
Tier 2: Firefox ESR, Beta and Nightly. If BMO is unusable, we will fix theses
Tier 3: Other browsers and mobile. If it works, that's cool. If it doesn't work, we will consider a patch.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
We can iterate on this with better usage data, but for now let's go with this.
(In reply to Emma Humphries β˜•οΈ (she/her) [:emceeaich] (UTC-8) +needinfo me from comment #11)
> Tier 1: Current and Current-1 versions of Firefox, Chrome, Edge, and Safari
> Tier 2: Firefox ESR, Beta and Nightly. If BMO is unusable, we will fix theses
> Tier 3: Other browsers and mobile. If it works, that's cool. If it doesn't
> work, we will consider a patch.
>
> We can iterate on this with better usage data, but for now let's go with this.

there's an important point i think you haven't considered.

if firefox doesn't start on windows the user needs to be able to report a bug.

there are versions of windows supported by firefox that ship with IE instead of edge.  by putting IE into 'tier 3' it's possible that these users will either have to download chrome to report a firefox bug, or, more likely, the bug won't be reported.  this use-case is likely to be one that's hard to capture with usage data.

as edge requires windows 10, and firefox still supports windows 7, this means that IE 11 should be a supported browser even if that support is limited to just sign-up, bug creations, and show-bug.
reopening for feedback on comment 13
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I think some redefinition will help, and we do need to support IE 11.

Rather than numbered tiers, I prefer "Full Support" and "Limited Support"

Full Support includes: The latest version of Firefox, the latest Firefox ESR, the latest version of Chrome/Chromium,
the latest version of Safari, and the latest version of Edge.
Limited Support includes: IE 11 and Firefox Nightly.

It is not required to iterate over "Unsupported" versions.
In general we support standards, this list is just what is required to be *tested* against,
and to give priority to bugs filed against those versions. As glob points out, people using IE 11 need to be able to file
bugs, so breaking logging in or bug filing there is not acceptable.
(In reply to Dylan Hardison [:dylan] (he/him) from comment #15)
> I think some redefinition will help, and we do need to support IE 11.
> 
> Rather than numbered tiers, I prefer "Full Support" and "Limited Support"
> 
> Full Support includes: The latest version of Firefox, the latest Firefox
> ESR, the latest version of Chrome/Chromium,
> the latest version of Safari, and the latest version of Edge.
> Limited Support includes: IE 11 and Firefox Nightly.

I recommend "the previous Firefox ESR" in Limited Support, as we overlap ESR releases for a period of time to give organizations (who are stuck on the previous Firefox ESR) a chance to try and upgrade and file bugs if they find any.
With comment 16:

Full Support includes: The latest version of Firefox, the latest Firefox ESR, the latest version of Chrome/Chromium,
the latest version of Safari, and the latest version of Edge.
Limited Support includes: IE 11, the previous Firefox ESR, and Firefox Nightly.
"and the latest version of Firefox Nightly", or similar.
I'd still like to have current-1 in there. 

"""
Full Support includes: The current and previous major versions of Firefox, Chrome, Chromium, Safari, WebKit, and Edge; and the latest Firefox ESR.
Limited Support includes: IE 11, the previous Firefox ESR, and Firefox Nightly.
"""
Could we compromise on "previous major versions" being Limited Support, so that it's clear that BMO *prioritizes* current versions of browsers (for good safety practices, if any other reason)?
"""
Full Support includes: The current versions of Firefox, Chrome, Chromium, Safari, WebKit, and Edge; and the latest Firefox ESR.
Limited Support includes: The previous versions of Firefox, Chrome, Chromium, Safari, WebKit, Edge, and Firefox ESR; IE 11 and Firefox Nightly.
"""

Any other changes? If not I'll close and update the wiki.
Sounds good to me.
+
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
See Also: → 1422435
You need to log in before you can comment on or make changes to this bug.