# History In bug 1111042 it was brought to our attention that we should research improvements on how we render download buttons. Bug 1112417 was opened as the large investigation into this issue. There is an immediate action we can take here that will stop the issue that surfaced in bug 1111042, and that is to show the list of all available downloads if we're unable to verify that the user is on a compatible platform. This is an improvement on the current UX which will block the user from accessing the download. # Request Update the download pages to show the list of available builds (e.g. http://cl.ly/image/1C410a2E3x0Y, http://cl.ly/image/080P1d090g3z) if we're unable to verify that the user meets the system requirements. The list of builds will be accompanied by a message along the lines of, "We were unable to verify that your system meets the requirements for Firefox. Here is a list of download links you may find helpful." :matej - will you please help with this message?

Totally happy to help. Just need to know when it's due. Thanks.

Awesome, thanks Matej. If you could get us a message by Jan 7th that would be great.

(In reply to Cory Price [:ckprice] from comment #2) > Awesome, thanks Matej. If you could get us a message by Jan 7th that would > be great. I'll do my best to get it done by Wednesday, but after that I'm on PTO until Jan. 12. I'll keep you posted. Thanks.

Would this work? "Your system may not meet the requirements for Firefox, but you can try one of these versions:" We could also say "downloads" instead of "versions." Mostly I'm trying to get away from saying "we," since that always brings up the question of who "we" is.

Schalk, Alex, and Jon - What do you think of pursuing this work? Valuable? Or too much complexity tied into the button?

(In reply to Jennifer Bertsch [:jbertsch] from comment #5) > Schalk, Alex, and Jon - What do you think of pursuing this work? Valuable? > Or too much complexity tied into the button? Very much yes. Of all the download button changes, this is the one I would like to see the most. If we're ever unsure of someone's device / platform, we should at least give users the benefit of the doubt and still provide an opportunity for them to try downloading.

Agree this is worth pursuing. Based on local testing, our current logic goes like this: 1. If the user is on an undetectable/unknown platform (other), we display the button for each platform (http://cl.ly/image/1C410a2E3x0Y) 2. If the user is on a known unsupported platform (oldwin, oldmac), we display a message that the user's platform doesn't meet the requirements (https://infinit.io/_/33fs9dX) Is the task then to display the buttons (with some extra copy?) along side the requirements message in case #2 above?

(In reply to Jon Petto [:jpetto] from comment #7) > Is the task then to display the buttons (with some extra copy?) along side > the requirements message in case #2 above? That's my understanding too, yes. Matej suggested a string in Comment 4 that might be slightly more suitable than the current requirements message.

I will add the messaging suggested by Matej as part of the download button overhaul.

Fixed as part of Bug 1213372