Closed Bug 494843 Opened 11 years ago Closed 11 years ago
please QA the Under the Hood page for 3
Hi guys. Please QA the new Under the Hood page for 3.5. As discussed, this is the final new page to support the release and we're in a slight bit of a time crunch. I'm hoping it's fairly straightforward! Known issues: - Faster Page Loading blurb will be replaced with a video demo hosted by Chris Blizzard (should be ready soon) - missing site ID screenshot in User Experience section Thanks!
First: where are all the links? None of the "View Documentation" or "Learn more about this feature." links are implemented! And now, the first batch of the more minor nits:  I think the prevailing style (at least in trade publications), is to refer to Ethernet and its ilk (e.g., Gigabit Ethernet, here), as a proper noun (xref: http://www.networkworld.com/news/2009/042009-terabit-ethernet.html)  Page validates to its doctype (a note to myself)  "Numerous alignment fixes" doesn't mean much to me; I'm guessing it's related to page layout, no? (I didn't check much of the content, admittedly.)
Severity: normal → major
I've added in the links with my best guesses for the appropriate destinations on MDC. Blizzard, can you confirm? I've also updated the capitalization of Gigabit Ethernet (r26266).
I'm pretty sure that we're going to get rid of that entire paragraph on faster page loading and will replace it with something else.
(In reply to comment #2) > I've added in the links with my best guesses for the appropriate destinations > on MDC. Blizzard, can you confirm? Thanks Steven. Sorry for not giving you this info earlier. Chris, please double check all this when you have a chance. (In reply to comment #3) > I'm pretty sure that we're going to get rid of that entire paragraph on faster > page loading and will replace it with something else. That's true - details in comment #0. Thanks all!
The geolocation link is missing docs. Use this: https://developer.mozilla.org/En/Using_geolocation The rest of the links look good. The JSON article needs some fleshing out, but that's not your responsibility.
Geolocation link added in r26270.
Just an FYI: I'm having the client QA team take a look at this (and a few other) pages -- it's looking good.
Minor anchor link problem under "Web Developer Features" - the Return to top links to https://www-trunk.stage.mozilla.com/en-US/firefox/performance/#top-performances where it should be https://www-trunk.stage.mozilla.com/en-US/firefox/performance/#top-performance
Grammar More UE Goodness "Plus, we've given your browsing history an easier-to-use timeline so you can quickly find a pages you’ve been to before."
Under "Vista", "themeing" should be "theming". I guess we should leave this open to track the missing screenshot? The rest seems good to me, unless anyone else finds something; Pascal? :-)
I don't know what's left to do here, from my side -- mostly content that should be/has been already vetted. Pascal, do you see anything?
Whiteboard: [waiting on Site Identity screenshot]
Steven, now that https://bugzilla.mozilla.org/show_bug.cgi?id=499309 and https://bugzilla.mozilla.org/show_bug.cgi?id=499310 have been resolved, can you add the Blizzard performance demo to this page? Let me know if you need any copy or additional info...thanks.
The Blizzard video has been added in r28372.
Can someone please add the missing Site Identity screenshot? I'm assuming we need both Mac/Windows versions; thanks!
(In reply to comment #18) > Can someone please add the missing Site Identity screenshot? I'm assuming we > need both Mac/Windows versions; thanks! I believe Steven is working on this today...please correct me if I'm wrong, of course.
Yeah, the screenshots are all updated here.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
More UE Goodness -> More UX Goodness
verified fixed on https://www.mozilla.com/en-US/firefox/performance/
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
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.