422734 - please QA the What's New page on the new Mozilla.com

Status: VERIFIED FIXED

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

Description

[John Slater]

Hi Stephen. Please QA as discussed.

Thanks,
John

Comment 1

[Pascal Chevrel:pascalc]

<a href="">View the Change Log</a>
<a href="">Learn more about our security process</a>

The above links to the change log/security pages links back to the whatsnew page

Comment 2

[Pascal Chevrel:pascalc]

<h2>You've been updated to the latest version of Firefox.</h2>

This message is not right on the long term, we should fix this issue that we had with Firefox 2, see bug #390332

Comment 3

[Reed Loden [:reed]]

Since we have product-details specifying which version is the most recent, we should either use PHP or JS to redirect users to some other page or show some other text saying they aren't on the latest version of Firefox. I agree this is something we should fix for the Firefox 3 refresh.

Comment 4

[Pascal Chevrel:pascalc]

I would be in favor of PHP testing if it is the most recent and conditionnally display one of the 2 texts. 

Comment 5

[Stephen Donner [:stephend] Not actively reading bugmail]

In addition to what Pascal and Reed have pointed out:

1) "View the Change Log" seems weird, given that we call them the "Release Notes" everywhere else

(Page validates, and looks fine in IE 6/7/Opera/Safari, even with JavaScript disabled, but seriously, since this is an in-product page, only the validation and JS-disabled view matter.)

Comment 6

[John Slater]

Re: Pascal & Reed's comments, that's a great point. Tell me if this is oversimplifying things, but can't we just have an alternate headline that reads "You've Been Updated to Firefox Version 3.x.x" and then an alternate subhead that reads "You can download the latest and greatest version here."?

Assuming that's all technically feasible, it seems like a pretty clean & easy way around this problem.

Re: Stephen's comment about "Change Log", I'm cc'ing Beltzner, who suggested that language for this page. Mike, can you advise?

Thanks,
John

Comment 7

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to comment #6)
> Re: Pascal & Reed's comments, that's a great point. Tell me if this is
> oversimplifying things, but can't we just have an alternate headline that reads
> "You've Been Updated to Firefox Version 3.x.x" and then an alternate subhead
> that reads "You can download the latest and greatest version here."?

Suggest:

<h1>You're now running Firefox %versionNumber.</h1>
<h3>We recommend you get the update to the latest version _here_, or by selecting "Check for Updates" in the "Help" menu.</h3>

> Assuming that's all technically feasible, it seems like a pretty clean & easy
> way around this problem.
> 
> Re: Stephen's comment about "Change Log", I'm cc'ing Beltzner, who suggested
> that language for this page. Mike, can you advise?

Yeah, "View the release notes" is fine. I think I'd been dreaming about having some sort of summary changelog, but the goal was to answer the user-question around "uh, what changed?"

Comment 8

[John Slater]

(In reply to comment #7)
> Suggest:
> 
> <h1>You're now running Firefox %versionNumber.</h1>
> <h3>We recommend you get the update to the latest version _here_, or by
> selecting "Check for Updates" in the "Help" menu.</h3>
Sounds great to me. Steven, can you code this up so the page can sniff the version number and serve up the appropriate headline?

> Yeah, "View the release notes" is fine. I think I'd been dreaming about having
> some sort of summary changelog, but the goal was to answer the user-question
> around "uh, what changed?"
Ok, let's go with "View the release notes" then. 

Thanks all,
John 

Comment 9

[Marco Zehe (:MarcoZ)]

Page's fine from my end.

Comment 10

[Steven Garrity [:sgarrity]]

Yeah, I think we can do the version detection based on the user-agent string. I'll get on this right away.

Comment 11

[Steven Garrity [:sgarrity]]

Since this version check will have to happen with Javascript, I need a more generic headline for cases where JS is disabled, or we fail to find the version number (bad UserAgent string, non Firefox browser, etc.).

Use what's there now?

"You've been updated to the latest version of Firefox."

Something more generic?

"Thanks for updating Firefox."

?

Comment 12

[John Slater]

(In reply to comment #11)
 Something more generic?
> 
> "Thanks for updating Firefox."
Thanks Steven. Let's use the more generic option you proposed for when JS is disabled.

Also, I'm making this bug dependent on 390332 so we can kill two birds with one stone.

Comment 13

[John Slater]

Steven, do you need anything else from us in order to implement this version checking? I think the text suggestion you made will work well, so as far as I'm concerned this plan has a thumbs up from me.

Comment 14

[Steven Garrity [:sgarrity]]

I've got the version checking stuff implemented. Can people test it out and make sure I got it right?

The sub-heading:
"You can download the latest and greatest version _here_."

Maybe we should re-word so we can link "latest and greatest version" rather than "here"?

Comment 15

[Marco Zehe (:MarcoZ)]

(In reply to comment #14)
> The sub-heading:
> "You can download the latest and greatest version _here_."
> 
> Maybe we should re-word so we can link "latest and greatest version" rather
> than "here"?

From an accessibilit standpoint, please yes! A link name of "latest and greatest" is more meaningful than a link named "here", especially if it appears more than once on a page. Screen readers often have a facility to list all links on a page, and having the word "here" is often more confusing than actually helpful. :-)

Comment 16

[John Slater]

How about this for a new subhead:

"For security reasons, we recommend downloading the _latest and greatest version_."

Thanks all,
J

Comment 17

[Steven Garrity [:sgarrity]]

(In reply to comment #16)
> How about this for a new subhead:
> "For security reasons, we recommend downloading the _latest and greatest
> version_."

Updated in r12215.

Comment 18

[Stephen Donner [:stephend] Not actively reading bugmail]

How do I test the version-checking?  I've hit this page with a 2.0.0.13 build on Linux and get the same page as with a Mac OS X 10.4 nightly trunk build of Firefox 3.

Comment 19

[Steven Garrity [:sgarrity]]

The stage site still has 2.0.0.13 listed as the "latest version" of Firefox, so you'll need an older release (2.0.0.12, etc.) to trigger the version check.

Comment 20

[Stephen Donner [:stephend] Not actively reading bugmail]

Attachment: Screenshot of 2.0.0.12; should trigger version check

Comment 21

[Stephen Donner [:stephend] Not actively reading bugmail]

Attachment: Screenshot of 2.0.0.12; should trigger version check--correct image :-)

Comment 22

[Steven Garrity [:sgarrity]]

I *think* I might have this issue fixed in r12289. Stephen, can you check it out?

Comment 23

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #22)
> I *think* I might have this issue fixed in r12289. Stephen, can you check it
> out?

Looks good with 2.0.0.12 on Windows; I'd like to do a bit more testing on other platforms/older versions later today.

Comment 24

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #23)
> (In reply to comment #22)
> > I *think* I might have this issue fixed in r12289. Stephen, can you check it
> > out?
> 
> Looks good with 2.0.0.12 on Windows; I'd like to do a bit more testing on other
> platforms/older versions later today.

I did that testing and it's fine; I think you can resolve this as FIXED, Steven, and we can spin-off any issues found during/after the beta period.

Comment 25

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED