This bug executes the development for /whatsnew 42.
Copy bug 1196520 Design bug 1196527 Both final. Please note we'd like to test two headlines on /whatsnew, so the request is to expose both to localizers.
Initial template is now up on demo2 for localizers (currently showing variation A only). https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/ Note: Clicking the "Try the new Private Browsing" CTA is not yet functional. I will update when this is ready.
UITour functionality should now be working on demo2 when a user clicks the blue CTA button to highlight privateWindow. To enable UITour on demo2, please maker sure to add "https://www-demo2.allizom.org" to the comma-delimited preference `browser.uitour.testingOrigins` in about:config. It won't exist by default, so you may need to create a new preference.
Graphic finalized in bug 1196527 comment 6
As noted, we would like to test version A against version B. Open to suggestions here, but I was thinking we'd do a /whatsnew/a /whatsnew/b Then fork traffic to /whatsnew/ via Optimizely. I believe we've tested whatsnew like this before. NI agibson - will this implementation be possible?
I suggest we do: /whatsnew/ /whatsnew/b/ It doesn't really make sense to do whatsnew/a/ as /whatsnew would be redundant. This is how we've done it in the past.
Ok the template is now serving two separate URLs: https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/ https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/b/ I decided /whatsnew/b/ should show the design with the white CTA lockup, since it was mentioned in the meeting yesterday that this will receive the smaller proportion of traffic. Hope this make sense.
Hi Cory, 2 things I'm missing: 1.) Fallback URL (SUMO link?) for when someone doesn't have the privateWindow icon in their pallet. 2.) "Learn how to find it" link for the second variation of /whatsnew. I imagine these will probably both be the same URL. Thanks
(In reply to Alex Gibson [:agibson] from comment #9) > https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/ The "Introducing Private Browsing with Tracking Protection" subhead should not appear in this version.
(In reply to Cory Price [:ckprice] from comment #11) > (In reply to Alex Gibson [:agibson] from comment #9) > > https://www-demo2.allizom.org/en-US/firefox/42.0/whatsnew/ > The "Introducing Private Browsing with Tracking Protection" subhead should > not appear in this version. Good catch, thanks!
(In reply to Alex Gibson [:agibson] from comment #10) > Hi Cory, 2 things I'm missing: > > 1.) Fallback URL (SUMO link?) for when someone doesn't have the > privateWindow icon in their pallet. https://www.mozilla.org/firefox/private-browsing/ > 2.) "Learn how to find it" link for the second variation of /whatsnew. https://support.mozilla.org/kb/private-browsing-use-firefox-without-history
Awesome work Alex - thanks! Here are things I heard today. 1. fade the poof out quicker. 2. expand poofs a bit as they fade out. 3. eye shutter, maybe blink a bit quicker. 4. leg blends into the shield, matt to separate out the layer. 5. move content up on the page a bit more for smaller screens. 6. move the poof to behind the shield - DONE 7. need a high res mask graphic (version B) NI Matt for (4) and (7)
Created attachment 8674952 [details] mask-plus-shield_2x.png Thanks Matt! #4 on Cory's list - Updated Critters: https://www.dropbox.com/s/ka6epks622perb3/shield-with-critters.psd?dl=0 #7 on Cory's list - Attached is a 2x version of the 'mask + shield'
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/189f81177959169b83bcbabdd57d673677508ee9 [fix bug 1196532] Firefox 42 /whatsnew https://github.com/mozilla/bedrock/commit/6723ef1cabb414d2c29398cd9ab3457f8275cb87 Merge pull request #3357 from alexgibson/bug-1196532-whatsnew-42 [fix bug 1196532] Firefox 42 /whatsnew & /firstrun/learnmore
On demo2 both /whatsnew and /whatsnew/b have the "try the new PB" button links to https://support.mozilla.org/kb/private-browsing-use-firefox-without-history if private browsing isn't in their pallet - in which case should it link to https://www.mozilla.org/firefox/private-browsing/ per Comment 13?
(In reply to Rebecca Billings [:rbillings] from comment #17) > On demo2 both /whatsnew and /whatsnew/b have the "try the new PB" button > links to > https://support.mozilla.org/kb/private-browsing-use-firefox-without-history > if private browsing isn't in their pallet - in which case should it link to > https://www.mozilla.org/firefox/private-browsing/ per Comment 13? Please see Bug 1219188 :) These links cannot be updated until the private browsing product page is in master.