please QA the Release Notes page on the new Mozilla.com

VERIFIED FIXED in 3.0

Status

www.mozilla.org
General
VERIFIED FIXED
11 years ago
6 years ago

People

(Reporter: John Slater, Assigned: stephend)

Tracking

unspecified

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
Hi Stephen. Please QA as discussed.

Thanks,
John
(Assignee)

Comment 1

11 years ago
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).
(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.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Assignee)

Comment 3

11 years ago
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!
(Reporter)

Comment 4

11 years ago
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.
(Assignee)

Comment 5

11 years ago
Make it so.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(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.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago11 years ago
Resolution: --- → FIXED
(Assignee)

Comment 7

11 years ago
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?
(Reporter)

Comment 8

11 years ago
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

11 years ago
Looks good from an a11y standpoint.
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
FWIW, I expect to be making many updates to the Release Notes page when we get to the RC1 milestone.
Changed at my request, as the version number for Firefox 3 gold will be "3.0" instead of "3.0.0".
(Assignee)

Comment 14

10 years ago
Links in comment 8 still need to be populated.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Links from comment 8 updated in r12009.

Should the "SafeBrowsing Service Privacy Policy" stay or go?
(Reporter)

Comment 16

10 years ago
(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.

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.
I'm going to close this for now. We re-open or create a new bug when the final release notes get underway.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago10 years ago
Resolution: --- → FIXED
(Assignee)

Comment 19

10 years ago
(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).
(Assignee)

Updated

10 years ago
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
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.