Closed
Bug 1336042
Opened 8 years ago
Closed 7 years ago
Stop presenting 32 and 64 bit version on the same level on the download page
Categories
(www.mozilla.org :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Sylvestre, Assigned: kohei)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
On this page: https://www.mozilla.org/en-US/firefox/all/
We are showing 32 & 64 bits version at the same level.
I am not UX expert bug maybe we should do something like.
Recommended: Legacy:
Windows 64-bit OS X Linux 64-bit Linux Windows
instead of
Windows Windows 64-bit OS X Linux Linux 64-bit
Reporter | ||
Updated•8 years ago
|
Summary: Stop putting 32 and 64 bit version on the same level on the download page → Stop presenting 32 and 64 bit version on the same level on the download page
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•8 years ago
|
||
Should we also explicitly say "32-bit" for the legacy platforms, maybe?
Assignee | ||
Comment 2•8 years ago
|
||
I'll send a pull request once Bug 1330000 is solved.
Assignee | ||
Comment 3•8 years ago
|
||
Modified the icons as well.
Assignee | ||
Comment 4•8 years ago
|
||
Comment 5•8 years ago
|
||
Aren't we not even offering 64bit on the main download pages yet? I thought there were still some addon compatibility issues that were preventing us from full-on recommending 64bit.
Assignee | ||
Comment 6•8 years ago
|
||
Yeah, the download buttons are only offering the win32 builds so far. Defaulting to win64 is scheduled for April, Firefox 53 if this wiki page is up to date: https://wiki.mozilla.org/Firefox/Win64
Comment 7•8 years ago
|
||
So that seems to me to indicate that we shouldn't yet be referring to win32 builds as "legacy" until at least then, right?
Comment 8•8 years ago
|
||
Do we start recommending Win64 without officially supporting? (bug 558448)
Reporter | ||
Comment 10•8 years ago
|
||
Well, at least on Linux, we are discussing about stopping the support (it is going to take a while but it is an interesting discussions to have).
We don't have this discussion about Windows 32 but we prefer that people start using 64 instead of 32.
I believe we should go ahead now and stop putting them at the same level. But I will let Chris make the final call!
Flags: needinfo?(sledru) → needinfo?(cpeterson)
Comment 11•8 years ago
|
||
Michael, it would be good to get some feedback from someone on the Firefox Onboarding team. What do you recommend?
(In reply to Sylvestre Ledru [:sylvestre] from comment #0)
> I am not UX expert bug maybe we should do something like.
>
> Recommended: Legacy:
> Windows 64-bit OS X Linux 64-bit Linux Windows
> instead of
> Windows Windows 64-bit OS X Linux Linux 64-bit
This proposal includes two changes:
1. labeling some platforms as "recommended" or "legacy"
2. reordering the platform columns
I think we should evaluate their merits independently:
1. I don't think we should label win32 Firefox as "legacy" when 30% of our users are running a win32 OS and will be for many more years. I don't have an opinion about labeling 32-bit Linux as "legacy", but I like Kohei's screenshot in comment 3 that changed "Linux" to "Linux 32-bit".
2. I personally find the reordered platform columns hard to read and not obvious at first why there are Windows columns both before and after Linux columns. :)
(In reply to Kohei Yoshino [:kohei] from comment #6)
> Defaulting to win64 is scheduled for April, Firefox 53 if this wiki page is
> up to date: https://wiki.mozilla.org/Firefox/Win64
As for timing, win64 has slipped 1-2 releases and won't be the default until Firefox 54 (June) or 55 (August). We're blocked on some 64-bit Flash bugs. Until then I don't think we should label win64 as "recommended" or list it before win32. But you could go ahead and land the reordered platform columns, if someone from the Onboarding team thinks that is OK.
Even after win64 is our default, I feel uneasy ever labeling win64 as "recommended" unless the /all page sniffs the UA and detects win64 OS. Offering win32 over win64 is always a safe choice. A win32 OS user will hit a frustrating error if they download and try to run the win64 Firefox installer.
Flags: needinfo?(cpeterson) → needinfo?(mverdi)
Reporter | ||
Comment 12•8 years ago
|
||
"Legacy" wasn't probably the right word. Maybe we should say "64 bits - recommended"
I understand we are not 100% ready for Windows but for Linux, we are. We should do that with Linux to start with.
Comment 13•7 years ago
|
||
I think we should change the "Windows" column label to "Windows 32-bit" (and "Linux" to "Linux 32-bit"). 64-bit is now the Windows stub installer's default for Firefox 55+ and we have just started migrating 1% of 32-bit Windows Firefox 56 users to 64-bit 56.0.1. If users run into problems with 64-bit Firefox, they will want re-install 32-bit Firefox. That will be easier if 32-bit is specifically labeled instead of the generic name "Windows".
I also think changing the column order so Windows 64-bit and 32-bit are not adjacent might be confusing (same for Linux 64-bit and 32-bit). I suggest we list 64-bit first, but keep the two Windows and Linux builds next to each other like:
Windows 64-bit | Windows 32-bit | macOS | Linux 64-bit | Linux 32-bit
Comment 14•7 years ago
|
||
Commits pushed to master at https://github.com/mozilla/bedrock
https://github.com/mozilla/bedrock/commit/a29bff50f0f35edce5e9a27dc39cd0ec3cc1c583
Fix Bug 1336042 - Stop presenting 32 and 64 bit version on the same level on the download page
https://github.com/mozilla/bedrock/commit/5b2d5d2e5e3efe10a332b94d7462d629c48a117d
Merge pull request #4665 from kyoshino/bug-1336042-all-64
Fix Bug 1336042 - Stop presenting 32 and 64 bit version on the same level on the download page
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 15•7 years ago
|
||
The change is now on production.
Status: RESOLVED → VERIFIED
Flags: needinfo?(mverdi)
Comment 16•7 years ago
|
||
Thanks, Kohei! The updated download page looks good.
https://www.mozilla.org/firefox/all/
You need to log in
before you can comment on or make changes to this bug.
Description
•