Closed
Bug 1232584
Opened 9 years ago
Closed 9 years ago
[TV] FTE for usage metrics specs update for the new legal approved terms
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect, P2)
Firefox OS Graveyard
Gaia::First Time Experience
ARM
Gonk (Firefox OS)
Tracking
(blocking-b2g:2.5+, b2g-v2.5 fixed, b2g-master fixed)
RESOLVED
FIXED
blocking-b2g | 2.5+ |
People
(Reporter: Fischer, Assigned: Fischer)
References
Details
(Keywords: verifyme, Whiteboard: [ft:conndevices][partner-cherry-pick][partner-blocker])
Attachments
(4 files, 2 obsolete files)
The FTU for usage metrics specs has been updated according to http://is.gd/bTOxTc
Assignee | ||
Comment 1•9 years ago
|
||
[Blocking Requested - why for this release]:
Assignee: nobody → fliu
blocking-b2g: --- → 2.5?
Assignee | ||
Updated•9 years ago
|
Summary: [TV] FTE for usage metrics specs update → [TV] FTE for usage metrics specs update for the new legal approved terms
Assignee | ||
Comment 2•9 years ago
|
||
@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
Flags: needinfo?(pchen)
Comment 3•9 years ago
|
||
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
Flags: needinfo?(pchen)
Comment 4•9 years ago
|
||
Assignee | ||
Comment 5•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[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
Attachment #8707378 -
Flags: review?(rexboy)
Comment 6•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[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.
Attachment #8707378 -
Flags: review?(rexboy)
Updated•9 years ago
|
blocking-b2g: 2.5? → 2.5+
Updated•9 years ago
|
Blocks: TV_Testing_2.6
QA Whiteboard: [COM=TV Seamless Experience]
Updated•9 years ago
|
QA Whiteboard: [COM=TV Seamless Experience] → [COM=TV FTE]
Assignee | ||
Comment 7•9 years ago
|
||
Update status: Waiting for the final specs & terms confirmation.
Comment 10•9 years ago
|
||
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
Flags: needinfo?(jalin)
Assignee | ||
Comment 11•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[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
Attachment #8707378 -
Flags: review?(rexboy)
Comment 12•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master
I think you're making things too complex. See my comments.
Attachment #8707378 -
Flags: review?(rexboy)
Updated•9 years ago
|
Flags: needinfo?(fliu)
Assignee | ||
Comment 13•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master
@Rex,
Not use FTEwizard to make the script simple, thanks.
Flags: needinfo?(fliu)
Attachment #8707378 -
Flags: review?(rexboy)
Comment 14•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[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.
Attachment #8707378 -
Flags: review?(rexboy)
Comment 15•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[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.
Attachment #8707378 -
Flags: review+
Assignee | ||
Comment 16•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 17•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[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
Attachment #8707378 -
Flags: approval-gaia-v2.5?(jocheng)
Comment 18•9 years ago
|
||
Comment on attachment 8707378 [details] [review]
[gaia] Fischer-L:bug_1232584-update-FTE-for-usage-metrics > mozilla-b2g:master
Approve for TV 2.5
Attachment #8707378 -
Flags: approval-gaia-v2.5?(jocheng) → approval-gaia-v2.5+
Comment 19•9 years ago
|
||
Assignee | ||
Comment 20•9 years ago
|
||
Updated•9 years ago
|
status-b2g-v2.5:
--- → fixed
status-b2g-master:
--- → fixed
Comment 21•9 years ago
|
||
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.
Assignee | ||
Comment 22•9 years ago
|
||
Assignee | ||
Comment 23•9 years ago
|
||
Attachment #8733226 -
Attachment is obsolete: true
Assignee | ||
Comment 24•9 years ago
|
||
Attachment #8733229 -
Attachment is obsolete: true
Assignee | ||
Comment 25•9 years ago
|
||
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.
You need to log in
before you can comment on or make changes to this bug.
Description
•