Closed Bug 662975 Opened 13 years ago Closed 13 years ago

Increase FX Upgrades, Browser Detection & Persistent Messaging

Categories

(www.mozilla.org :: General, defect, P1)

Product:
www.mozilla.org
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 668101

People

(Reporter: christine.brodigan, Assigned: sgarrity)

References

(
URL
)

Details

Attachments

(4 files, 1 obsolete file)

Mockup of warning designs
280.73 KB, image/jpeg
Details
Screenshot of updated warning style
333.43 KB, image/png
Details
screenshot
393.38 KB, image/png
Details
l10n friendly js
1.48 KB, text/plain
Details 
This bug is kind of a fun, but punchy bug. We recently met with the Product Marketing Team and C Beard to discuss ways to increase uptake from users with 3.5 & 3.6.

There's urgency to do this, because we will no longer support those version in the near future.

We'd like to create a persistent message that will live across all pages on mozilla.com that 3.5/6 users will see upon arrival:

"You're currently using an older version of Firefox. For your security, please download the latest version here (it will take less than 30 seconds!). Thanks for keeping the web safe!"
funny, that's something we used to do on mozilla-europe.org 5 years ago to push 1.x users to upgrade to 2.0 !

http://viewvc.svn.mozilla.org/vc/projects/mozilla-europe.org/trunk/en/oldff.js?revision=1073&content-type=text%2Fplain&view=co&pathrev=1073

our message was almost the same :)

"You appear to be using an older version of Firefox. You should upgrade to the latest version which provides additional security and new features"
Will this go through a design process, or should we get right into it?

Could do something like the mobile survey: https://bug656453.bugzilla.mozilla.org/attachment.cgi?id=535322
Great question! Just get right into it!
Is there a similar bug for addons.mozilla.org ? I guess that's another website where old users still go.

We should not warn users with a PowerPC or running Mac OS X 10.4 or older. They can't upgrade to Firefox 4. Maybe they are other changes in system requirements between 3.5 and 4.0.
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: 2.9 → 2.10
What should the "download the latest version here" link point to? I had been thinking just /firefox/new/, but what if you're already on that page?

Is it intended to be a direct download link? These are usually presented as a button, rather than a text link.
Chrissie, thoughts on comment #5?
(In reply to comment #5)
> What should the "download the latest version here" link point to? I had been
> thinking just /firefox/new/, but what if you're already on that page?
> 
> Is it intended to be a direct download link? These are usually presented as
> a button, rather than a text link.

Hey Steven,

Great questions!

1.) I was thinking we would just take the user to /firefox/new

2.) If the user is already on /firefox/new we should just make sure that the language is "peppy" with a warmer salutation: 

Hello! Looks like you're using an older version of Firefox. Protect your data, upgrade for FREE, get additional security & enjoy new features"

3.) As for presentation a download button would be great, we just need to make sure that they have the same "thank you" experience on the subsequent page, so tracking fully works.

Thoughts?
Quick thought: We should loop Matej in for the peppy copy.
(In reply to comment #8)
> Quick thought: We should loop Matej in for the peppy copy.

Hey Matej,

Can you quickly refresh with some "peppy" copy? Currently, I have:

Hello! Looks like you're using an older version of Firefox. Protect your data, upgrade for FREE, get additional security & enjoy new features"

Due by tomorrow morning, June 23, 2011.

:)CB
Any of these work for you?

Hey there. Looks like you're still on an old version of Firefox. Get the free upgrade for the latest technology and safety features.

Want the latest features, data protection and all around improved security? Download the latest version of Firefox free!

Protect your data with the latest version of Firefox. Enjoy new features and additional security, all free.

That old version of Firefox you've got is pretty good, but if you want the latest in features and security, you should get the free upgrade now.
I like the first option, but would change safety to security. Does this address the case Steven mentioned in comment #5 though?
I think it would be good that this upgrading code is website neutral, this way we could use it on any mozilla site and we could also propose it for community site and maybe even non-mozilla sites that would like to propose that on their sites.
(In reply to comment #11)
> I like the first option, but would change safety to security. Does this
> address the case Steven mentioned in comment #5 though?

How about:

Hey there. Looks like you're using an old version of Firefox. We're here to help! 

Getting the free upgrade takes less than a minute, and without it you're missing out on the latest technology and security features. Update now or learn more.

Steven see:
https://skitch.com/chrissiebrodigan/fgn29/screen-shot-2011-06-22-at-10.08.11-am

a button & text link would be fly. 

Thoughts all?
(In reply to comment #13)
> How about:
> 
> Hey there. Looks like you're using an old version of Firefox. We're here to
> help! 
> 
> Getting the free upgrade takes less than a minute, and without it you're
> missing out on the latest technology and security features. Update now or
> learn more.

Looks great. I would just break up the first line of the blurb into two:

Getting the free upgrade takes less than a minute. Without it you're missing out on the latest technology and security features. Update now or learn more.
Let's also track to see how this performs vs. our other upgrade campaigns. Steven - please use this tracking tag on the destination URLs:

www.x.com/?WT.mc_ID=ubanner
(In reply to comment #15)
> Let's also track to see how this performs vs. our other upgrade campaigns.
> Steven - please use this tracking tag on the destination URLs:
> 
> www.x.com/?WT.mc_ID=ubanner

Lofo = rockstar

Pascal = +1, we'll share the code back to see if you can implement as well. Let's circle back on this when you're here in Mountain View first week of July.

:)CB
Priority: -- → P1
Should the message be dismiss-able? (this would involve a cookie to remember not to show it again)
I'm not entirely clear on copy for this message. In Comment #7 that we use different copy if we're already on /new/ - is that still the case?

Also, where should the "learn more" point to?

I'd suggest avoiding having both text links and a button - I think a simple message with a single call-to-action would be best.
Here is a mockup with two variations on a header message.

The first uses a simple mono-chrome warning icon, the second, a creature illustration. I used the Yeti because I had him lying around - it's not really a good fit for this message (is it?).

I think a friendly creature illustration could can really help this type of message feel helpful/friendly rather than robotic/scary/annoying.

I also find, after seeing it in context, that it's text heavy. Could could trim the copy at all?

Still need clarification on the 'learn more' text too (see my previous comment).
Steven,

If possible, can we use both and the one that performs the best becomes the one we always use? If not, we can A/B with Blake.

1.) Yeti!

2.) update now - links to http://www.mozilla.com/en-US/firefox/new/

3.) learn more - links to http://www.mozilla.com/en-US/firefox/central/

Copy:

     Hey there! Looks like you're using an old version of Firefox.

     Get the free upgrade in less than a minute. Don't miss out on new technology & security features.

Thoughts?

Best,
CB
Can we say "the latest" instead of new? I'd also consider reversing the order of the body copy:

Hey there! Looks like you're using an old version of Firefox.

Don't miss out on the latest technology & security features. Get the free upgrade in less than a minute.
(In reply to comment #21)
> Can we say "the latest" instead of new? I'd also consider reversing the
> order of the body copy:
> 
> Hey there! Looks like you're using an old version of Firefox.
> 
> Don't miss out on the latest technology & security features. Get the free
> upgrade in less than a minute.

Yeeeeees! Great edits!
Steven - 

If we use both versions use two different tracking codes:

1. Yeti: www.x.com/?WT.mc_ID=ybanner
2. Non-Yeti: www.x.com/?WT.mc_ID=cbanner
Steven,

Here's an example of what Mozilla's Army of Awesome launched last week in the same vein: https://support.mozilla.com/en-US/kb/Firefox%20crashes?s=firefox+crashes&as=s&ref=aoa

-CB
and what about the case where we're already on the /firefox/new/ page? (or the /central/ page, for that matter)?
(In reply to comment #25)
> and what about the case where we're already on the /firefox/new/ page? (or
> the /central/ page, for that matter)?

I think for now, to stay in scope, we just display the same message. We can look at alternate messaging for the next release. Thoughts?
I stole the illustration from the blog, and I think it works better than both the exclamation-mark-triangle, and the yeti. Screenshot attached.

This is implemented in trunk in r91385.

Please review: http://www-trunk.stage.mozilla.com/

Also note that this is en-US only for now.
(In reply to comment #27)
> Created attachment 541752 [details]
> Screenshot of updated warning style
> 
> I stole the illustration from the blog, and I think it works better than
> both the exclamation-mark-triangle, and the yeti. Screenshot attached.
> 
> This is implemented in trunk in r91385.
> 
> Please review: http://www-trunk.stage.mozilla.com/
> 
> Also note that this is en-US only for now.

Great! Woo-hooooooo!
Attached image screenshot — 
See attached screenshot

The notification section does not highlight the download link well enough. The download button is also broken.
(In reply to comment #29)
> Created attachment 541782 [details]
> screenshot
> 
> See attached screenshot
> 
> The notification section does not highlight the download link well enough.
> The download button is also broken.

For this phase of the project, the design is approved (we will revisit in a separate Phase 2).

The download button should be fixed to work for the release.
(In reply to comment #29)
> The notification section does not highlight the download link well enough.
> The download button is also broken.

Raymond, what version of Firefox was this? I can't replicate.
Firefox 3.6.13 using user-agent switcher addon
A fix in trunk in r91564.

This is unrelated to the download button issue - still working on that.
It appears that the broken download button is an odd edge case that arises from using a Windows-based user agent string on a mac via the User Agent Switcher for testing.

I've tested in an actually copy of 3.6 and we're fine.

Merged to stage in r91569.
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → FIXED
Reopening for myself - I think I introduced a PHP warning:

Warning: ini_set() [ref.outcontrol]: Cannot change zlib.output_compression - headers already sent in /data/mozilla_trunk/includes/min/config.php on line 180

 in r91564.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #36)
> Reopening for myself - I think I introduced a PHP warning:

Fixed in trunk in r91581. Merged to stage in r91583.

That leaves two merges to go to production: r91569 and r91583.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Keywords: qawanted
Resolution: --- → FIXED
I'm gonna reopen this since it displays the message for PPC and 10.4 users even though they can't upgrade.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
the strings and links are also hardcoded in the js file, no way for locales to define their own.

ex:

update_heading.innerHTML = 'Hey there! Looks like you’re using an old version of Firefox.';
(In reply to comment #39)
> I'm gonna reopen this since it displays the message for PPC and 10.4 users
> even though they can't upgrade.

Good point. There's also a list of unsupported Windows platforms in js/download.old.js (win95, winNT, etc.). I'm not keen on duplicating that code though, and including it on all pages doesn't seem great either (though we are already including it on many pages due to existing download buttons). It minifies to just under 10Kb.

Any suggestions?

(In reply to comment #40)
> the strings and links are also hardcoded in the js file, no way for locales
> to define their own.
> ex:
> update_heading.innerHTML = 'Hey there! Looks like you’re using an old
> version of Firefox.';

Another good point. I was instructed to get something quick implemented for en-US and we can improve for l10n afterwards (I guess it's afterwards now).

Pascal, can you take a look at the rest of the JS? I think it's probably going to have to be re-factored due to the way the tags are created and assembled in JS - beyond just allowing replacement strings to be passed in from the parent HTML file. Can you take a look at confirm? Thanks.

Might make sense to spin both of these out into separate bugs (one for unsupported versions and one for l10n support)?
I am going to attach a version of the javascript that would be more l10n friendly :)
Attached file l10n friendly js (obsolete) — 
Here is the javascript, since we were using innerHTML anyway, I removed the unnecessary DOM-based text insertions that were leading to slicing the sentences in chunks.

I also added a couple of commodity functions for l10n strings and urls that are defined before the script is loaded at the page level.
Attached file l10n friendly js — 
updated file, there was an unused variable in the previously attached file
Attachment #542843 - Attachment is obsolete: true
Pascal,

110n friendly js = awesome (and, apologies we needed to get it out this release and kept the scope super tight under that deadline).

Steven,

Should we open a new bug for this?

LMK,
CB
Chrissie, no problem, I understand :)
Regarding the copy, I have a few thoughts:
* we tell people to upgrade in the first sentence but the link says "update", usually we use 'update' for small changes and 'upgrade' as 'major update'. Is the use of the two terms intended? If not, can we use upgrade in both? There are languages in which it may be tricky to find two different verbs and I expect some localizers to ask why they are not the same.
* the "Hey there!" part sounds very... direct to my French ears :) I wonder if it will work well in the United Kingdom too.
* "Get the free upgrade in less than a minute." is likely to not be true everywhere, many of our users in less connected areas of the world probably don't have that much bandwidth and will need several minutes
(In reply to comment #47)
> Regarding the copy, I have a few thoughts:
> * we tell people to upgrade in the first sentence but the link says
> "update", usually we use 'update' for small changes and 'upgrade' as 'major
> update'. Is the use of the two terms intended? If not, can we use upgrade in
> both? There are languages in which it may be tricky to find two different
> verbs and I expect some localizers to ask why they are not the same.

I think that's probably just a typo and it should be "upgrade" in both places.

> * the "Hey there!" part sounds very... direct to my French ears :) I wonder
> if it will work well in the United Kingdom too.

I'm fine with making that an optional bit for localizing, but would like to keep it in en-US (though some kind of greeting would be nice).

> * "Get the free upgrade in less than a minute." is likely to not be true
> everywhere, many of our users in less connected areas of the world probably
> don't have that much bandwidth and will need several minutes

If that's the case, I would change that line to "Get the free upgrade or learn more." Then we can put the links right into that line and lose the third line.
Target Milestone: 2.10 → 3.0
(In reply to comment #41)
> Good point. There's also a list of unsupported Windows platforms in
> js/download.old.js (win95, winNT, etc.). I'm not keen on duplicating that
> code though, and including it on all pages doesn't seem great either (though
> we are already including it on many pages due to existing download buttons).
> It minifies to just under 10Kb.
> 
> Any suggestions?

This gPlatformUnsupported regex seems rather old and only contain OSes that don't have a 3.0 version. So we should update it to include platforms that have been dropped since.

Instead of adding the update-v3.js file to all pages, we could just do something like this in the HTML (pseudo-code):
if (isFirefox 3) includeJSFile();

We just import the regexp code in the HTML so that makes one less HTTP request for most users.
@Anthony, I believe the javascript is inlined currently, no extra http request
(In reply to comment #49)
> This gPlatformUnsupported regex seems rather old and only contain OSes that
> don't have a 3.0 version. So we should update it to include platforms that
> have been dropped since.

That probably deserves a separate bug.

> Instead of adding the update-v3.js file to all pages, we could just do
> something like this in the HTML (pseudo-code):
> if (isFirefox 3) includeJSFile();

Rik, I did consider that, but the total JS ended up being so small, that it was easier to including inline (no extra HTTP request) for everyone, rather than add an extra request for 3.x users. Now that the JS payload may be getting larger, that might make sense.
Not sure if this went live or not before it was reopened, but I'm not seeing the tags from Comment 15 and comment 23 coming through to Webtrends so let's please make sure we add them if they're not already. 

Raymond - can you QA that?
Target Milestone: 3.0 → 3.1
(In reply to comment #52)
> Not sure if this went live or not before it was reopened, but I'm not seeing
> the tags from Comment 15 and comment 23 coming through to Webtrends so let's
> please make sure we add them if they're not already. 
> 
> Raymond - can you QA that?

On staging, I can see the tags but when i visit the page using a PPC Firefox user-agent I am redirected to https://www-trunk.stage.mozilla.com/en-US/m/
Target Milestone: 3.1 → 3.0
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → DUPLICATE
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: