Closed Bug 556571 Opened 15 years ago Closed 15 years ago

test alternate footers on /ie.html

Categories

(www.mozilla.org :: General, defect, P1)

Product:
www.mozilla.org
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jslater, Assigned: sgarrity)

References

(
URL
)

Details

One of the findings from Blake's recent multivariate tests on the download page for IE users is that the versions with smaller footers seemed to perform a little better. Since it's not clear if that's tied to page load speed or actual footer content, let's do a few more tests to see what really works. Steven and I have already discussed this on the phone, but here's what we're proposing: 1. keep the current footer content, but eliminate the two images (grey background & dino head). Replicate the grey background as closely as possible using CSS. 2. keep the current images and visual style, but reduce the # of links...just use the headers of each category and legal links, rather than the full site map. 3. combination of #1 and #2...eliminate images and reduce the # of links. 4. go super simple...remove grey background entirely and only include the most essential links (like privacy policy and legal notices). 5. slightly expanded version of #4...use only the most essential links, but keep the grey CSS background from version #1. Blake, if that sounds like a good testing plan to you then Steven will start building these with the goal of having them ready to start testing by sometime next week.
Sounds great!
Priority: -- → P1
These will have to be based on the main ie.html page, rather than ie-perf.html (from bug 555235) because the ie-perf.html doesn't actually use the real footer template. I assume that's ok?
Alternately, I could stuff a static version of the footer links into copies of ie-perf.html. If we go that route, though, I'll probably have to setup another variation - one that looks just like the original ie.html, but has the in-lining of CSS/JS of ie-perf.html to act as the control for this test (ie-perf.html can't be the control as is, because it has a simplified footer). Blake, please let me know your preference.
I'm fine with the idea from comment #2, but b/c this is a testing thing it's Blake's call. Blake, what do you think?
I'm also fine with the idea form comment #2.
First variation is in trunk in r65413 (/en-US/firefox/ie-test-footer-a). More to come.
Second variation in trunk in r65414 (/en-US/firefox/ie-test-footer-b).
Would you mind only attaching new footer HTML and inline CSS to this bug?
(In reply to comment #8) > Would you mind only attaching new footer HTML and inline CSS to this bug? Sure. Should I even be bothering to check-in the variation pages to SVN? Is that helpful for QA, or do they test the actual test variations anyhow?
Thanks! For a test as simple as this, we can just QA the SiteSpect variations.
For variation #1 (previously setup as /en-US/firefox/ie-test-footer-a), the only change is the following inline CSS - to be added in the document <head> somewhere after the other CSS includes: <style type="text/css"> #footer { background: #e3e2df; border-top: 1px solid #d5d4d1; } #footer #copyright { background: none; padding-left: 0; } </style>
For variation #2 (previously setup as /en-US/firefox/ie-test-footer-b), the only changes are: The following inline CSS - to be added in the document <head> somewhere after the other CSS includes: <style type="text/css"> #footer-menu li { width: auto; margin-right: 35px; } #footer { min-height: 0; } * html #footer { height: 0; } </style> and the unordered list in the footer with the ID of #footer-menu should be replaced with: <ul id="footer-menu"> <li><a href="/en-US/firefox/">Firefox</a></li> <li><a href="/en-US/mobile/">Mobile</a></li> <li><a href="https://addons.mozilla.org/" class="external">Add-ons</a></li> <li><a href="http://support.mozilla.com/">Support</a></li> <li><a href="/en-US/manyfaces/">Community</a></li> <li><a href="/en-US/about/">About</a></li> </ul>
For variation #3: The following inline CSS - to be added in the document <head> somewhere after the other CSS includes: <style type="text/css"> #footer { background: #e3e2df; border-top: 1px solid #d5d4d1; } #footer #copyright { background: none; padding-left: 0; } #footer-menu li { width: auto; margin-right: 35px; } #footer { min-height: 0; } * html #footer { height: 0; } </style> and the unordered list in the footer with the ID of #footer-menu should be replaced with: <ul id="footer-menu"> <li><a href="/en-US/firefox/">Firefox</a></li> <li><a href="/en-US/mobile/">Mobile</a></li> <li><a href="https://addons.mozilla.org/" class="external">Add-ons</a></li> <li><a href="http://support.mozilla.com/">Support</a></li> <li><a href="/en-US/manyfaces/">Community</a></li> <li><a href="/en-US/about/">About</a></li> </ul>
For variation #4: The following inline CSS - to be added in the document <head> somewhere after the other CSS includes: <style type="text/css"> body#firefox #footer { margin-top: 0; } #footer { background: none; color: #afaba3; } #footer a:link, #footer a:visited, #footer #lang_form label { color: #afaba3; } #footer #copyright { background: none; padding-left: 0; clear: left; } #footer { min-height: 0; } * html #footer { height: 0; } #footer #lang_form { width: auto; } </style> and the unordered list in the footer with the ID of #footer-menu should be removed.
For variation #5: The following inline CSS - to be added in the document <head> somewhere after the other CSS includes: <style type="text/css"> #footer #copyright { clear: left; } #footer { min-height: 0; } * html #footer { height: 0; } </style> and the unordered list in the footer with the ID of #footer-menu should be removed.
This is perfect. Thanks Steven!
Is this done? On hold?
done
closing per comment #18
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
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.