The FTU for usage metrics specs has been updated according to http://is.gd/bTOxTc

[Blocking Requested - why for this release]:

@Peko, The new FTE Settings is having the 1st page which contains the whole Mozilla privacy policy. The Mozilla privacy policy has texts in different sizes, like big title, middle title and regular texts. Could you please help to define the font sizes for the Mozilla privacy policy ? Please refer to http://is.gd/bTOxTc for the new FTE Settings specs and the Mozilla privacy policy. Thank you

Hi Fischer, I think we should keep the same size,but you can change font type to fira sans italic. For example: Mozilla Privacy Policy:70 px (keep the same) What do we mean by "personal information? :38 px (fira sans italic) For us, "personal information" means...:38 px (keep the same) Thanks

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master @Rex, This patch does: (1) Update the TV FTU according to the new approved terms by legal - The 1st page is to present user the Mozilla Privacy policy - The 2nd page is to present user the Activation terms - The 3rd page is to ask user’s permission for collecting app usage (2) Update fteWizard to add 3 more events for TV FTU’s usage - oninit event: fired after fteWizard is done with init so we could do other follow-up init operations - ongoNext event: fired after going to next page - ongoPrev event: fired after going back to previous page (3) Use fteWizard to control the page transition in TV FTU Thank you

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master Per our discussion, please set r? to me once legal finishes their modification.

Update status: Waiting for the final specs & terms confirmation.

Jack, please update spec here. Thanks.

Dear Fischer, Please refer to the final FTE spec as the link below, https://drive.google.com/folderview?id=0B5RN80W56Ga9fjlncXJuZW5YbW0zX2tDX0sta3FsMXU3cmRYM0hTOEJXZFZ2ck5wSW1PZlU&usp=sharing There are 3 files you will use, 1. FTE Spec v2.5_20160303.pdf 2. Mozilla Privacy Policy.docx 3. Firefox OS Privacy Notice.docx Please let me know if you have any questions. Jack

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master @Rex, This patch does: * Update the TV FTU according to the new approved terms by legal - Add Firefox OS Privacy Notice and Mozilla Privacy Policy - Add links to open Firefox OS Privacy Notice and Mozilla Privacy Policy * Update fteWizard to add 3 more events for TV FTU’s usage - oninit event: fired after fteWizard is done with init so we could do other follow-up init operations - ongoNext event: fired after going to next page - ongoPrev event: fired after going back to previous page * Use fteWizard to control the page transition in TV FTU * Slightly update simple_key_navigation.js to avoid Null exception on accessing empty element list Thanks

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master I think you're making things too complex. See my comments.

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master @Rex, Not use FTEwizard to make the script simple, thanks.

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master There are two hyperlinks in the legal texts, and the patch assumes they appear in the same line when implementation. This may not be the case after localization. If there are line wraps between the links, the resulting spatial navigation would be weird (e.g. when focusing at first hyperlink, you need to press right for the next hyperlink that is wrapped and actually shown at left If we can make sure the problem above is not happening during l10n (or we can tolerate it), then we can make the commit. Or I would suggest to use spatialNavigator rather than SimpleNavigator for this case.

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master After discussion I realized the decision has been discussed with UX, so I'm ok with it. There are still some comments on Github, please consider them before landing.

Land to Master: https://github.com/mozilla-b2g/gaia/commit/19d23ce1bfb38eb6156d65fb550e98229b8b5072

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master [Approval Request Comment] [Bug caused by] (feature/regressing bug #): 1232584 [User impact] if declined: TV FTU is not the final version [Testing completed]: Yes [Risk to taking this patch] (and alternatives if risky): Low [String changes made]: Yes

Comment on attachment 8707378 [details] [gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master Approve for TV 2.5

Uplifted to v2.5: https://github.com/mozilla-b2g/gaia/commit/d90c7cd8df3ba9be8671f698cf1cf67db07b788c

tv-ftu on TV(stingray) 3/22 v2.5 + tv-ftu-Improve-for-scroll-down-hint.patch Arrow animation is OK Transition dignity is ... depends on you.

After the bug 1556613 and the bug 1257442 landed, the transition should be smooth. Please see the attached video: try_arrow_button_transition_video_link_20160322.