A Desktop user coming to https://www.mozilla.org/en-US/firefox/new/ is using Firefox for Desktop. They are NOT using a current version of the browser. Reqs for Desktop, not up-to-date user: - a user who is "not up-to-date" is using a version of Firefox for Desktop 1+ versions older than the current version. We will not include versions less than 1 since a silent update may be complete and the user hasn't restarted their browser. (will track this possibility once page is live and alter if necessary) - conditional message is displayed across top of page telling user that they are using an old version of Firefox for Desktop - a link to "how do automatic updates work?" on our support site is displayed: https://support.mozilla.org/en-US/kb/update-firefox-latest-version?esab=a%20&s=silent+download&r=0&as=s#w_how-do-automatic-updates-work - a Firefox download button is displayed on the page

Where is the "how do automatic updates work?" link supposed to be? Up in the conditional message, or in the links below the download button? Holly, could you post a demo screenshot?

Use this conditional message copy (with ! icon) for now at top of page until we get final copy: “You are using an older version of Firefox. Updating is quick and easy. “ The second sentence of the conditional message at the top of the page will be a link. “Updating is quick and easy.” sentence links to Auto Updates section of https://support.mozilla.org/en-US/kb/update-firefox-latest-version?esab=a &s=silent+download&r=0&as=s You can see our link styles on this page of the style guide: http://www.mozilla.org/en-US/styleguide/websites/sandstone/colors/ I will make sure final copy accommodates this. The reasoning is to try to catch users that already have a silent update waiting for them before they download a new file. Is this clear enough or would you still like a demo screenshot?

(In reply to Holly Habstritt [:Habber] from comment #0) > A Desktop user coming to https://www.mozilla.org/en-US/firefox/new/ is using > Firefox for Desktop. They are NOT using a current version of the browser. > > > Reqs for Desktop, not up-to-date user: > - a user who is "not up-to-date" is using a version of Firefox for Desktop > 1+ versions older than the current version. We will not include versions > less than 1 since a silent update may be complete and the user hasn't > restarted their browser. (will track this possibility once page is live and > alter if necessary) At the moment, I'm using the isFirefoxUpToDate() function in media/js/base/global.js That function falls back to using the "data-latest-firefox" property from the body tag which itself is set from a constant. Is the current use of that function() appropriate for the "1+ versions older than the current version" outlined above? If not, what's the best way to calculate that cut-off (I realize isFirefoxUpToDate() can accept an optional alternate version to check against). > > - conditional message is displayed across top of page telling user that they > are using an old version of Firefox for Desktop > > - a link to "how do automatic updates work?" on our support site is > displayed: > https://support.mozilla.org/en-US/kb/update-firefox-latest- > version?esab=a%20&s=silent+download&r=0&as=s#w_how-do-automatic-updates-work > > - a Firefox download button is displayed on the page

(In reply to Nick Burka [:cremini] from comment #3) > (In reply to Holly Habstritt [:Habber] from comment #0) > > A Desktop user coming to https://www.mozilla.org/en-US/firefox/new/ is using > > Firefox for Desktop. They are NOT using a current version of the browser. > > > > > > Reqs for Desktop, not up-to-date user: > > - a user who is "not up-to-date" is using a version of Firefox for Desktop > > 1+ versions older than the current version. We will not include versions > > less than 1 since a silent update may be complete and the user hasn't > > restarted their browser. (will track this possibility once page is live and > > alter if necessary) > > At the moment, I'm using the isFirefoxUpToDate() function in > media/js/base/global.js > > That function falls back to using the "data-latest-firefox" property from > the body tag which itself is set from a constant. Is the current use of that > function() appropriate for the "1+ versions older than the current version" > outlined above? If not, what's the best way to calculate that cut-off (I > realize isFirefoxUpToDate() can accept an optional alternate version to > check against). I've answered my own question (after some digging around) and have it working on my local branch for this bug. We'll be submitting a pull request with the changes shortly. > > > > > - conditional message is displayed across top of page telling user that they > > are using an old version of Firefox for Desktop > > > > - a link to "how do automatic updates work?" on our support site is > > displayed: > > https://support.mozilla.org/en-US/kb/update-firefox-latest- > > version?esab=a%20&s=silent+download&r=0&as=s#w_how-do-automatic-updates-work > > > > - a Firefox download button is displayed on the page

Mike/Nick: FYI. In bug 888512, we are creating new locale neutral screenshots that will replace what we have for Mac, Windows, and Linux. We have been using the Windows screenshot for Linux and we may have a specific version, but that is TBD.

Updated Copy: [Cond. message with ! icon] Looks like you’re using an older version of Firefox. Updating is quick and easy. Link “Updating is quick and easy” part of line to: https://support.mozilla.org/kb/update-firefox-latest-version?esab=a &s=silent+download&r=0&as=s

Nick: just confirming that the logic you are using to determine if Firefox is up to date is the isFirefoxUpToDate() function. There was some questions today about Firefox ESR versions, which are 10 and 17 and those people shouldn't be told they are out of date. It is also impossible from a user agent perspective to tell the difference between a normal Firefox 17 and Firefox 17 ESR and thus every 6 versions of Firefox we will be telling a user they are up to date even if they are running a non-ESR build. Does that make sense? Habber: does that make sense too?

Chris: you can see what I ended up using here: https://github.com/nburka/bedrock/blob/bug-868199-unified-download/media/js/firefox/new.js (lines 9-22) It's what isFirefoxUpToDate() does internally, but I'm subtracting 1 from the version to check that it's 2 versions old instead of just 1. I'm not sure how that will work with the ESR releases. What do they put in the <body data-latest-firefox="?"> attribue? Habber - do you know the answer to that? Or should I ask in #www?

(In reply to Nick Burka [:cremini] from comment #8) > Chris: you can see what I ended up using here: > https://github.com/nburka/bedrock/blob/bug-868199-unified-download/media/js/ > firefox/new.js (lines 9-22) > > It's what isFirefoxUpToDate() does internally, but I'm subtracting 1 from > the version to check that it's 2 versions old instead of just 1. > > I'm not sure how that will work with the ESR releases. What do they put in > the <body data-latest-firefox="?"> attribue? > > Habber - do you know the answer to that? Or should I ask in #www? isFirefoxUpToDate takes into account ESR. In the button helper there is a [10, 17] array to exclude those versions from deciding if they are out of date. There is no way through UA strings to tell if versions 10, 17, 24 are ESR or not. That's on purpose so people can't target ESR builds.

Please update copy for banner message, seen here: http://cl.ly/image/0D073U1b3v47 NEW COPY: "Looks like you’re using an older version of Firefox. Update to stay fast and safe." OLD COPY: "Looks like you’re using an older version of Firefox. Updating is quick and easy." Second sentence will continue to link to current SUMO URL until further guidance from SUMO is given. Current link being used for second sentence in banner - https://support.mozilla.org/kb/update-firefox-latest-version?esab=a &s=silent+download&r=0&as=s

Holly, the new copy is in place for the desktop FX out-of-date message.

Thanks, Michael. Could I see a screenshot of it to check the layout? I'm curious if the copy needed to wrap and what it looks like now with the link in place.

(In reply to Holly Habstritt [:Habber] from comment #12) > Could I see a screenshot of it to check the layout? > I'm curious if the copy needed to wrap and what it > looks like now with the link in place. Screenshot attached. This latest code is now up on demo2 as well.

Thanks, Steven.