please QA the Homepage on the new Mozilla.com

VERIFIED FIXED in 3.0

Status

VERIFIED FIXED
11 years ago
6 years ago

People

(Reporter: jslater, Assigned: stephend)

Tracking

unspecified

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
Hi Stephen. Please QA as discussed.

A few notes:
- this page has two alternate background illustrations that aren't available yet. Stephanie, can you let us know when to expect them?
- I believe the intent is to have pull-down menus on ALL the top nav links.
- we'll want to update the "what's new" links before the site launch, but this is fine for now.

Thanks!
(Assignee)

Comment 1

11 years ago
1) The JavaScript-disabled view needs some CSS lovin' to get the platform-specific bullets inset

(Page validates, displays much the same in IE 6/7/Opera/Safari, even with JS disabled, except for the above-mentioned issue.)

Marco, any accessibility issues?
Style for js-disabled view fixed up a bit (it's pretty minimalist, but I think that's ok) - in r11473.

Can we mark this as FIXED and track the other background illustrations in Bug 423990?
(Assignee)

Comment 3

11 years ago
(In reply to comment #2)
> Style for js-disabled view fixed up a bit (it's pretty minimalist, but I think
> that's ok) - in r11473.
> 
> Can we mark this as FIXED and track the other background illustrations in Bug
> 423990?

Fine with me; John, or Pascal?  Marco will take a look at it for accessibility, too.

Comment 4

11 years ago
All's well on this end!
the firefox logo is stained by the background image :
https://www-firefox3.stage.mozilla.com/img/tignish/home/sidebar-thunderbird.png

I would also put a   between "learn" and "more" here, it is on two lines for me:
 <a href="/en-US/firefox/">Learn more.</a>
(In reply to comment #5)
> the firefox logo is stained by the background image :
> https://www-firefox3.stage.mozilla.com/img/tignish/home/sidebar-thunderbird.png

I'm not sure what you mean by this - can you explain further?

> I would also put a &nbsp; between "learn" and "more" here, it is on two lines
> for me:
>  <a href="/en-US/firefox/">Learn more.</a>

Good idea. Done in r11693.
(Assignee)

Comment 7

11 years ago
2) Step 3 and Step 4 images aren't found (maybe I should spin that off since it's from /products/?)
3) The "Mozilla Messaging Starts Up Operations" link (https://www-firefox3.stage.mozilla.com/en-US/press/mozilla-2008-02-19.html) is a 404.
4) Wil and/or Pascal: can you look over the download code here?  I've been testing with JavaScript disabled and our matrix (Opera 9.26, IE 6/7, Safari 2.1, etc...), but wouldn't mind some more eyes :-P

The three background images are in and looking good; in fact, they honestly make me hungry for Fruit Loops, but I digress.

Page is still validating, so that's awesome.  I don't see Pascal's issue, but maybe he can clarify.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Assignee)

Comment 9

11 years ago
Reopening; I still see the broken link I pointed out in #3 of comment 7.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #9)
> Reopening; I still see the broken link I pointed out in #3 of comment 7.

Fixed in rr12006.

Stephen - please let me know if I'm being too quick to mark these bugs as FIXED. I'm counting on you to mark them as VERIFIED or reopen them.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago11 years ago
Resolution: --- → FIXED
(Assignee)

Comment 11

11 years ago
Verified FIXED.

Steven - sorry about not consistently reopening; John and I talked about that briefly (since he's been doing a better job than I at that), and I'll be doing it going forward, since it's getting harder to track changes.

I'm also leaning towards spinoff bugs for issues brought up after a few iterations of these Verified FIXED bugs, for the same reason (also something I'll work on).
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.