421347 - please QA the Release Notes 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

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

1) Placeholder fact aside, we should lower-case the "/Features" link to be consistent with the rest
2) Need links for the following:

<li><a href="#">Firefox 3 Project Page</a></li>
<li><a href="#">MozillaZine’s Knowledge Base</a></li>
<li><a href="#">Developer Information</a></li>

3) Same comment as from https://bugzilla.mozilla.org/show_bug.cgi?id=421348#c1:

When JavaScript is disabled, the expand/collapse widgets disappear, and the
heading doesn't shift left, so there's an empty space (minor UI nit)

4) Both "/organic" and "/security" links should have their trailing directory slashes, to avoid a quick-but-uneccessary redirects (HTTP 301 status).

Comment 2

[Steven Garrity [:sgarrity]]

(In reply to comment #1)
> 1) Placeholder fact aside, we should lower-case the "/Features" link to be
> consistent with the rest
fixed r11066.

> 2) Need links for the following:
> <li><a href="#">Firefox 3 Project Page</a></li>
> <li><a href="#">MozillaZine’s Knowledge Base</a></li>
> <li><a href="#">Developer Information</a></li>

John, can you let me know where these links should go?

> 3) Same comment as from https://bugzilla.mozilla.org/show_bug.cgi?id=421348#c1:
> When JavaScript is disabled, the expand/collapse widgets disappear, and the
> heading doesn't shift left, so there's an empty space (minor UI nit)

Fixed in r11067.

> 4) Both "/organic" and "/security" links should have their trailing directory
> slashes, to avoid a quick-but-uneccessary redirects (HTTP 301 status).

Fixed.

Comment 3

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

Sorry, Steven, I should've caught this before: the +/- widget images don't collapse/expand in either IE 6 or 7.  Should we reopen this to address:

1) The above
2) The three links John can supply in comment 1?

Thanks!

Comment 4

[John Slater]

1. We should definitely address this, yes.
2. I'm copying Beltzner on this bug...the final content for this page is really in his domain, so he's better qualified to determine what should go here than I am.

But yeah, this one should be reopened.

Comment 5

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

Make it so.

Comment 6

[Steven Garrity [:sgarrity]]

(In reply to comment #3)
> Sorry, Steven, I should've caught this before: the +/- widget images don't
> collapse/expand in either IE 6 or 7.  Should we reopen this to address:

Good catch. Fixed in r11175.

I'll keep in touch with beltzner about updating the content for the release notes.

Comment 7

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

1) I guess Beltzner can fix this too with Kubla later (in addition to the three missing links in comment 2 / comment 4), but the side navigation links should be MultiViews-agnostic, and thus end in .html, as we've been fixing in the other pages.
2) Likewise, I'm not sure whose fix this is, but:
* "performance" (#performance) is an empty anchor
* "more personal" (#personal) is an empty anchor
* "under the hood" (#engine) is also an empty anchor

Marco, you know the drill: are there accessibility issues?

Comment 8

[John Slater]

For the side navigation links, let's do this (I'm basing these on the FF2 release notes):
* Firefox 3 Project Page = http://wiki.mozilla.org/Firefox3
* [text change here] Firefox Support = http://support.mozilla.com
* Developer Information = http://www.mozilla.org/projects/firefox/

Beltzner, let us know what you think the best plan should be for filling in the content (including the empty anchors) later.

Comment 9

[Marco Zehe (:MarcoZ)]

Looks good from an a11y standpoint.

Comment 10

[Pascal Chevrel:pascalc (PTO until April 26)]

I would be tempted to propose the "Firefox 3 developer page" on Devmo instead of the Developer Information page on w.m.o. It is/will be localized in several languages, has more practical information for web developers and gets more love from the documentation team I think:

http://developer.mozilla.org/en/docs/Firefox_3_for_developers

Comment 11

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

FWIW, I expect to be making many updates to the Release Notes page when we get to the RC1 milestone.

Comment 12

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

Page URL seems to have moved from https://www-firefox3.stage.mozilla.com/en-US/firefox/3.0.0/releasenotes/ to https://www-firefox3.stage.mozilla.com/en-US/firefox/3.0/releasenotes/ surreptitiously (perhaps the first wasn't the correct scheme).

Comment 13

[Reed Loden [:reed]]

Changed at my request, as the version number for Firefox 3 gold will be "3.0" instead of "3.0.0".

Comment 14

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

Links in comment 8 still need to be populated.

Comment 15

[Steven Garrity [:sgarrity]]

Links from comment 8 updated in r12009.

Should the "SafeBrowsing Service Privacy Policy" stay or go?

Comment 16

[John Slater]

(In reply to comment #15)
> Should the "SafeBrowsing Service Privacy Policy" stay or go?
Beltzner, can you weigh in on this when you have a chance? I'm not really up to speed on the content needs for this page.

Comment 17

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

It can go, we'll have updated the privacy policy of Firefox to include the appropriate link.

Just so you guys know, the release notes will likely change for RC1, and those should be the ones that we base the content of the final release notes on.

Comment 18

[Steven Garrity [:sgarrity]]

I'm going to close this for now. We re-open or create a new bug when the final release notes get underway.

Comment 19

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

(In reply to comment #18)
> I'm going to close this for now. We re-open or create a new bug when the final
> release notes get underway.

Yeah; the template's there, and we'll have to revisit this before we ship anyway (checked validation again, and we're fine).