Closed
Bug 420931
Opened 17 years ago
Closed 17 years ago
please QA the First Run page on the new Mozilla.com
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
VERIFIED
FIXED
3.0
People
(Reporter: jslater, Assigned: stephend)
References
()
Details
Hi Stephen. Please QA this page as discussed.
Thanks!
John
Reporter | ||
Updated•17 years ago
|
Comment 1•17 years ago
|
||
A couple things I happened to notice:
- I think the Firefox 3 versioning scheme is 3.0.0, not 3.0.0.0
- The title of the page says "This is not really Firefox 3 Beta 2"
- "Start" probably shouldn't be capitalized in the intro paragraph.
Comment 2•17 years ago
|
||
(In reply to comment #1)
> - I think the Firefox 3 versioning scheme is 3.0.0, not 3.0.0.0
Most definitely correct! 3.0.0 all the way. :)
Assignee | ||
Comment 3•17 years ago
|
||
What fligtar and reed said, above, plus:
The page validates at XHTML 1.0 Strict, which is good.
However,
1) "Visit Getting Started" link should point to https://www-firefox3.stage.mozilla.com/en-US/firefox/central/
2) "Visit Support" should probably point to http://support.mozilla.com
(If I'm wrong, Reed will correct me!) :-P
Comment 4•17 years ago
|
||
(In reply to comment #1)
> - I think the Firefox 3 versioning scheme is 3.0.0, not 3.0.0.0
Fixed in r10973
> - The title of the page says "This is not really Firefox 3 Beta 2"
Fixed in r10977
> - "Start" probably shouldn't be capitalized in the intro paragraph.
Fixed in r10982
> 1) "Visit Getting Started" link should point to...
> 2) "Visit Support" should probably point to ...
Fixed in r10977
Assignee | ||
Comment 5•17 years ago
|
||
Steven: looks good; if you mark this FIXED, I'll verify.
John: the links aren't changing here, right? We're still linking to /central?
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•17 years ago
|
Reporter | ||
Comment 6•17 years ago
|
||
The content/intent of the Getting Started page is changing quite a bit, but I don't see any reason to change the link. In general, I'd like to avoid changing links from the "old" site as much as possible.
Assignee | ||
Comment 7•17 years ago
|
||
Ditto on that (comment 6); verified FIXED.
Status: RESOLVED → VERIFIED
Comment 9•17 years ago
|
||
<h2>Welcome to Firefox3</h2>
nitpick, there should be a space between Firefox and 3
Comment 10•17 years ago
|
||
(In reply to comment #9)
> nitpick, there should be a space between Firefox and 3
Fixed in r11128. Thanks.
Assignee | ||
Updated•17 years ago
|
Reporter | ||
Comment 11•17 years ago
|
||
I'm reopening this bug b/c there have been some changes to this page as a result of Rolnitzky's partner program (bug 427649).
Basically we've added a third promo paragraph at the bottom of the page - the default version talks about add-ons in general, but there are also seven alternate versions that promote specific add-ons. Those will only be visible if you downloaded Firefox 3 from a direct referral by that add-on.
Anyway, this page needs a final round of QA...thanks!
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 12•17 years ago
|
||
[1] Any way we can get the logos to not jump on page reload? (I guess they won't when bug 427651 is fixed, since that should only show a single promo image/paragraph.)
[2] Page renders fine with JavaScript disabled, but doesn't have the promo content--this is the first run page, and it's not expected with default configs that JS is disabled, but perhaps upgrading users might have it, in which case not sure we care (or do we?)
Can't yet verify the intended functionality due to the above-mentioned bug 427651.
Comment 13•17 years ago
|
||
Sounds like we are in a holding pattern until the cookie functionality is setup -- is that right?
In terms of #2 -- do we have any idea what proportion of users disable JS? I have to believe it's very small.
Assignee | ||
Comment 14•17 years ago
|
||
(In reply to comment #13)
> Sounds like we are in a holding pattern until the cookie functionality is setup
> -- is that right?
>
> In terms of #2 -- do we have any idea what proportion of users disable JS? I
> have to believe it's very small.
Probably close to infinitesimal--I just wanted to be sure I tested that case, but I don't expect it'll be very common at all, especially not on the First Run page...
Comment 15•17 years ago
|
||
The new behaviour is all setup now. This can be QA'ed.
Assignee | ||
Comment 16•17 years ago
|
||
How do I QA the second paragraph of comment 11? Where are those entry points?
Assignee | ||
Comment 17•17 years ago
|
||
(In reply to comment #16)
> How do I QA the second paragraph of comment 11? Where are those entry points?
Verified that over in something like four other bugs last week and early this week.
John, please mark this fixed?
Reporter | ||
Updated•17 years ago
|
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Updated•13 years ago
|
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.
Description
•