After talking with Clearleft about a number of the changes we want to make, they thought it would be best to take a look at redoing our install buttons across the board so that they can all be consistent. We'll need some install buttons for 5.7 for the user profile pages, but those can either be normal links or the existing buttons, since the new buttons are mostly similar for public add-ons. But by the end of this week we should have all of the new designs for all of the cases in the massive flowchart.
Created attachment 425855 [details] a few buttons, v1 Here's the direction they're going. There are a few issues that I pointed out to them and a bunch of missing cases, but just wanted to give a preview.
A couple of notes: 1) I think the buttons for listed add-ons should visually be more similar (or event equal) to the sandboxed add-on buttons, and not the same as public add-on buttons. I like the striped pattern. Maybe with a different color? 2) I think the warning should be more verbose. It should say something like "Unreviewed add-ons can read and change your preferences, access your passwords, send your information to third parties, install other software in your computer, ...". I would also add a link to the bottom of the bubble that expands on this.
Created attachment 426064 [details] buttons, v2 Some additional button states. Next he'll be adding the larger button versions for the listing pages and the JS-disabled states. I also asked for some iconography in the pop-ups so that they don't turn into "whatever" buttons, especially for unreviewed add-ons.
After trying to figure out how to handle the JS-disabled case for these pop-ups, Clearleft wants to know if it would be okay to have an interstitial page that the buttons link to where the message would be displayed and then users would either accept the message or cancel and go back. I'm fine with this. People with JS disabled have chosen to lead hard lives on the web, and we're still providing the same functionality for them to download their add-on. Note that if JS is disabled we can't do most of these compatibility checks anyway, so the only dialogs this would apply to are self-hosted and unreviewed add-ons, which are important dialogs. I'm going to tell them that proceeding with this method is fine, but if anyone has serious objections to this, please let me know.
Created attachment 427015 [details] button matrix, v4
Created attachment 427358 [details] button matrix, v5
Created attachment 427359 [details] button states, v2
A concern with the "install anyway" button I have is that users may not be aware that Firefox won't let them do that without overriding its compatibility checking. You may wish to link to a help page about this issue from the popup bubble so that users don't get confused why it won't actually install.
Questions about the button matrix: 1. The text for "Other browsers" in row 1 is Firefox-specific. What do we show when we're looking at thunderbird add-ons a) in Firefox b) in Thunderbird? 2. If I'm in Firefox looking at /thunderbird, all the buttons are going to be concealed. Is this really what we want? 3. Are we really going to maintain what the current version of Firefox is, and where you can download a nightly? 4. Do all the Firefox buttons point at http://mozilla.com? Where do those buttons point for other browsers? 5. How much do we care about the interstitial pages for non-js? All the download URLs will have to come out of the server pointing to something other than an xpi. Then js will have to munge all those URLs. It's not impossible, just annoying, and complicates everyone's life for users we don't care that much about. Can we assume that non-js users deserve whatever comes down to them? They're probably not scared by our warnings anyways. # Glossary concealed: dimmed text, white background
6. How do these interact? a) Wrong platform + old/new version b) Unreviewed + either part of (a) c) unreviewed + eula d) any combination I'm missing
(In reply to comment #16) > Can we assume that non-js users deserve whatever comes down to > them? They're probably not scared by our warnings anyways. I don't know how many different warnings there are, but maybe a one-sentence noscript for each of these warnings (containing a useful link, to either the FAQ or getfirefox.com or something) will suffice?
(In reply to comment #16) > Questions about the button matrix: > 1. The text for "Other browsers" in row 1 is Firefox-specific. What do we show > when we're looking at thunderbird add-ons a) in Firefox b) in Thunderbird? The "other browser" pitch/warning only shows up for Firefox. If you're browsing /seamonkey we don't tell you to get SeaMonkey, and if you're browsing in /thunderbird we can't tell if the person doesn't have Thunderbird. > 2. If I'm in Firefox looking at /thunderbird, all the buttons are going to be > concealed. Is this really what we want? Why are they all concealed? They should all be active and say "Download Now" unless it's not compatible with their OS. If the user is browsing in a Thunderbird user agent, they can act just like Firefox does and say Add to Thunderbird and show when incompatible with that TB version. > 3. Are we really going to maintain what the current version of Firefox is, and > where you can download a nightly? I don't think we maintain the current version in order to achieve this functionality. Please look at what we do currently. I'll post the URL to link to later -- we'd only link to alpha/beta releases, not nightlies. > 4. Do all the Firefox buttons point at http://mozilla.com? Where do those > buttons point for other browsers? Firefox buttons point to getfirefox.com?src=amo. There are no other browsers to point to. > 5. How much do we care about the interstitial pages for non-js? All the > download URLs will have to come out of the server pointing to something other > than an xpi. Then js will have to munge all those URLs. It's not impossible, > just annoying, and complicates everyone's life for users we don't care that > much about. Can we assume that non-js users deserve whatever comes down to > them? They're probably not scared by our warnings anyways. Can you show me what you propose the original page would look like without JS for an unreviewed add-on?
(In reply to comment #17) > 6. How do these interact? a) Wrong platform + old/new version b) Unreviewed + > either part of (a) c) unreviewed + eula d) any combination I'm missing a) the popup should have both the incompatible text and icon and the old/new version text and icon. the buttons should be whatever they would be based on the old/new text. b) pop up experimental warning first. if they click the button there, then popup whatever additional warnings need to be shown. c) there's a mockup of featured + eula, so just swap out featured with unreviewed. we'll get the full click through when they have to accept the eula (the "Accept and Install" button should be the unreviewed button and popup)
(In reply to comment #19) > Can you show me what you propose the original page would look like without JS > for an unreviewed add-on? http://img.skitch.com/20100317-tk25u8cc6s5rhaa8jcirufhbwf.png
We need to display the warning even for JS disablers. It can be in an interstitial page or it can link to the details page and the details page can have the warning expanded and they don't have to click through it.
Started here: http://github.com/jbalogh/zamboni/commit/fda5ce40 Finished here: http://github.com/jbalogh/zamboni/commit/24a7a7ae