New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fix bug 1325198] Test /all links on /new, part 2. #4550
[fix bug 1325198] Test /all links on /new, part 2. #4550
Conversation
9576a60
to
1409dfe
Compare
I definitely get the refresh button in production in my current version. If you have trouble triggering it locally you can just manually add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few layout issues but looking good to me otherwise. Maybe worth getting a second opinion from @alexgibson on the JavaScript bits.
@@ -61,6 +69,12 @@ | |||
<div class="mobile download-button-wrapper" id="download-button-wrapper-mobile" data-upgrade-subtitle="{{_('Get it free on Google Play')}}"> | |||
{{ download_firefox(dom_id='download-button-mobile') }} | |||
</div> | |||
|
|||
{% if version == '2' %} | |||
<div id="test-inpage-wrapper"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this probably needs to move down after #refresh-firefox-wrapper
so it can clear the floats when both buttons are shown.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yeah, tested in Beta and Dev Edition. 😞 Moving this block to the last element in main-content
seems to do the trick.
li { | ||
.border-box(); | ||
margin-bottom: 10px; | ||
width: 50%; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on conversation below, the XP/Vista link will be merged with the Windows 32-bit link, which will skirt us around this issue for now.
You need to enable UITour in order to see the refresh button, and then view the page using the current release version of Firefox (may also need to update product details locally) |
case 'Linux 64-bit': | ||
$li.attr('data-sort', 4); | ||
break; | ||
case 'OS X': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not related to this change, but I guess we should really file a bug to rename OS X
to macOS
sometime soon?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably a good idea. Hopefully Mac users don't get confused. 😒
var $html = $('html'); | ||
|
||
// make sure desktop download button exists, user is not on Android or iOS, and user is on a recognized platform | ||
if (!$html.hasClass('ios') && !$html.hasClass('android') && $dlButton.length && $dlButton.find('.unrecognized-download:visible').length === 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any reason why we don't want to show this for iOS and Android users? At the very least, iOS users would also see there is an Android version available, and vice-versa?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this maybe be simplified to say "as long as there is a download button visible, show the extra content"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the reason we went desktop only here was to make sure the links are actionable. Clicking on the Google Play button while on iOS would probably be more frustrating than helpful.
I agree we may want to promote/display information about Android on iOS (and vice versa), but I think that's a different task than we're performing here.
(FWIW, my preference/hope is for a single link to a freshened up /firefox/all/
instead of the handful of links we're testing here.)
// make sure desktop download button exists, user is not on Android or iOS, and user is on a recognized platform | ||
if (!$html.hasClass('ios') && !$html.hasClass('android') && $dlButton.length && $dlButton.find('.unrecognized-download:visible').length === 0) { | ||
// pull the nojs links out of the primary CTA | ||
var $directLis = $dlButton.find('.nojs-download li').remove(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I totally get that this is for a test and is quick and dirty, but a lot of this DOM-fu could probably be avoided if we wrote a macro specifically for this use-case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, but I'm holding off on that until we have a final direction. I really hope we go with a single link to an improved /firefox/all/
rather than injecting direct links here.
} | ||
} | ||
|
||
#test-mobile-downloads { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like these mobile links need to be block-level and have a set height/width to show up on IE < 9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Will fix.
@@ -1278,6 +1285,20 @@ | |||
), | |||
'output_filename': 'js/firefox_new_scene2-bundle.js', | |||
}, | |||
'experiment_firefox_new_scene1_all_links-pt2': { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be an underscore before pt2
? e.g. experiment_firefox_new_scene1_all_links_pt2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
$dlButton.append($newLink); | ||
// move forest up on the page a bit (original value = -254px) | ||
} else if (version === 2) { | ||
$('.forest-container').css('margin-top', '-310px'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving this content up is fine as long as the download buttons are shown, but if you set the HTML classes linux arm
for example, then the install link can no longer be clicked because the horizon assets cover the content.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. There are too many display variations to be this cute about spacing. Will remove the special casing here.
$li.attr('data-sort', 5); | ||
break; | ||
default: | ||
$li.attr('data-sort', 99); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently Windows (XP/Vista)
is falling through to this ordering. Do we need to special case it? Ideally, Windows users should only see the link that is appropriate to them providing we have JS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before the special XP/Vista link was added, Verdi requested the specific ordering (I believe) based on popularity. That being the case, I think XP/Vista being last is probably correct.
I think keeping the XP/Vista link visible for all users stays true to the original intent of the test, but am open to discussion if there's a potential for harm having all 3 Windows downloads displayed. Are you thinking we should do some detection and show either both Windows 32 and Windows 64 OR only XP/Vista?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit of a special edge case, as it's not really like a specific platform link like the others - it just points to a specific bouncer end-point that supports sha-1. For Windows XP users they still want "Windows 32 bit" for example, but the main link won't work at all as it points to the sha-256 bouncer URL. When they click "Windows XP/Vista", they still get the 32 bit Windows installer. It's a little confusing with 2 buttons pointing to the same product imho, but will defer to what you think is most appropriate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it might be of any help, I seem to remember adding special casing for the original experiment in the sha-1 PR: #4413
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see the difference now. Thanks for the link to the previous PR - will pilfer.
Pushed an update that I believe addresses all the comments. @craigcook + @alexgibson - one more look? |
cbe9d27
to
a4bcdc9
Compare
Other than the one layout issue, the changes all look good to me. r+wc 👍 |
Fixed the ?v=1 link UI and the IE 7 display bug (float container just needed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r+ to merge once squashed 👍
4ab6c3d
to
01296a1
Compare
Description
2nd round of testing for alternate download links on
/firefox/new/
.en-US
only.Version 1: - Link added underneath Firefox Privacy link that opens up a modal (winner from last test).
Version 2: - Majority of content from modal in v1, displayed directly on the page (underneath primary CTA).
I believe we want to run this test ASAP, but should confirm with other teams that no other upcoming experiments (i.e. Optimizely/funnelcake) would conflict.
Bugzilla link
https://bugzilla.mozilla.org/show_bug.cgi?id=1325198
Testing
Ensure UI works across browsers (SVGs wont be displayed on old IE). Make sure direct download links work, and that experiment works as intended.
Checklist