I installed the update to Firefox to 6.0.1 (which had downloaded and I had not restarted Firefox since 6.0.2), it then tells me "Your Firefox is out of date. For security reasons, we recommend upgrading to the latest and greatest version. Your Flash Player is out of date. Never fear, we can help. To keep you as safe as possible, we recommend you upgrade your Flash Player. Without it, your browser could be less stable and less secure. So get the free update now or learn more." (I killed the Flash update already as it conflicted with the Firefox process, but Firefox itself is up to date.) The link "latest and greatest version" is http://www.mozilla.org/en-US/firefox/ which then takes me to http://www.mozilla.org/en-US/firefox/fx/ "Good news! Your Firefox is up to date. Now take it with you." and offers me Firefox for Android. Problems with this experience: 1. I just updated Firefox (downloaded update ready to apply on restarting Fx), to hear it isn't up to date is confusing. 2. There's a tension between updating Firefox and updating Flash. Flash appears more urgent visually (there is a warning triangle) but otherwise, the copy says the same thing with different words. 3. I am then routed to a page that tells me "Firefox is up to date". It is hard to find the update, it's under the fold of the page, and I am told I don't need it. By the way, in my confusion, I'm being offered another product (Firefox on Android) I am a sync user, logged in and using Firefox on several Android devices. It isn't unreasonable to imagine as a user that Mozilla might be aware of the devices I connect with (I understand why we cannot, but another Sync user might not understand it).

Thanks Patrick. Laura, Chrissie - what do you guys think? What's the best way to solve?

Can I suggest there are a few things to fix: 1. Fx applies an update when there is another one available. Shouldn't it check for other updates first? 2. Mozilla.org misidentifies 6.0.1 as latest version - that seems fairly straightforward. 3. Update Flash message is not harmonised with update Firefox message: what do we expect the user to do first?

This was the other screenshot, it wasn't clear to me as a user what action I was supposed to take first.

For 1. this should be another bug for the Firefox team. 2. If you're speaking of mozilla.org/firefox, we don't read the minor version number to do the redirect to /fx right now. We should fix that. Both in .htaccess and prefetch.php. 3. I guess we could disable the flash warning if Firefox is not up to date.

(In reply to Anthony Ricaud (:rik) from comment #4) > For 1. this should be another bug for the Firefox team. > > 2. If you're speaking of mozilla.org/firefox, we don't read the minor > version number to do the redirect to /fx right now. We should fix that. Both > in .htaccess and prefetch.php. > > 3. I guess we could disable the flash warning if Firefox is not up to date. Adding Christian and Sean. We did an eye-tracking study on this page and the Flash warning by far was the most effective element. People really needed to know that they needed to update Flash. It's designed to capture attention and it's important to the browsing experience. I'm not sure we should disable it. Let's see what Christian and Sean think.

(In reply to Anthony Ricaud (:rik) from comment #4) > For 1. this should be another bug for the Firefox team. Patrick, can you file and link back to here for reference? > 2. If you're speaking of mozilla.org/firefox, we don't read the minor > version number to do the redirect to /fx right now. We should fix that. Both > in .htaccess and prefetch.php. This sounds right to me - do we file a spinoff bug, or can we fix here? > 3. I guess we could disable the flash warning if Firefox is not up to date. Is it possible to get stats to show how many people who see the Flash warning are also not up to date on Firefox? That would help make the decision. I agree with Chrissie in comment #5 that the Flash warning is an important part of our mission and should be on there if possible, but it'd be helpful to know the #s so we can evaluate tradeoffs.

(In reply to John Slater from comment #6) > (In reply to Anthony Ricaud (:rik) from comment #4) > > For 1. this should be another bug for the Firefox team. > > Patrick, can you file and link back to here for reference? Filed as Bug 685499 - no dependency though.

> Is it possible to get stats to show how many people who see the Flash > warning are also not up to date on Firefox? That would help make the > decision. I agree with Chrissie in comment #5 that the Flash warning is an > important part of our mission and should be on there if possible, but it'd > be helpful to know the #s so we can evaluate tradeoffs. I think this is a wider product question: we know that we want the user to update their Flash plugin and Firefox. The question is, in which order, and how can we message and manage it as painlessly as possible. Until we identify what path we want the user to take, I suspect the experience will remain a confusing one.

The /fx/ page has been revised.