Closed Bug 808660 Opened 8 years ago Closed 2 years ago

[Contacts] Apply BB to the value selectors


(Firefox OS Graveyard :: Gaia::Contacts, defect, P1)

Gonk (Firefox OS)


(Not tracked)



(Reporter: pabloUX, Unassigned)



(Keywords: polish, Whiteboard: visual design, UX-P2, ux-tracking, 2.6UXnom)


(5 files, 2 obsolete files)

VAlue selectors should be as it is specified in tbe BB.
Severity: major → normal
Component: Gaia → Gaia::Contacts
Priority: -- → P1
Whiteboard: Visual design
yes they should. including Steve P on this as i feel it is more a visual design touchpoint.
Keywords: polish
Whiteboard: Visual design → visual design
Whiteboard: visual design → visual design UX-P1
Just FYI: There's a relevant bug on this, here:

Rafa and Sergi were also cc'd on the parallel email thread, subject: "The behavior of value selector has been changed". We had to shift how value selectors work in v1 for technical reasons.
Whiteboard: visual design UX-P1 → visual design, UX-P1
Whiteboard: visual design, UX-P1 → visual design, UX-P2
Assignee: nobody → pacorampas
Depends on: 1080458
Attached file patch in github
Attached image object-menu-contacts.png (obsolete) —
Comment on attachment 8515817 [details] [review]
patch in github


We are working for applying the value selector for contacts. We have attached a screenshot with the after and before. With this patch is all working fine but there is a error: "mozL10n: A non-existing entity requested: #type_l10n_id#" when the edit mode is opened. We couldn't find the issue, could you help us?
Also, could you give us your feedback about the patch in general?

Attachment #8515817 - Flags: feedback?(francisco)
Comment on attachment 8515817 [details] [review]
patch in github

Jose I'm a bit overloaded, could you take a look?

Specially to the critical path, I think we will be loading more resources at startup and that can penalize our cold start time.
Attachment #8515817 - Flags: feedback?(francisco) → feedback?(jmcf)
Comment on attachment 8515817 [details] [review]
patch in github

This patch news much more work on various aspects:

A/ Carrie and Fang to give us the ok to the interaction and visual proposal you are making here. 

B/ If they give us the ok, then you should file a new bug to modify building blocks.

C/ The concerned CSS files to implement that design should be lazy loaded

D/ I left other substantive comments on GH, concerning the code organization

thanks Paco. needinfo-ing Carrie and Fang to know their opinions
Flags: needinfo?(fshih)
Flags: needinfo?(cawang)
Attachment #8515817 - Flags: feedback?(jmcf)

I wonder what's the difference between the attached pic and the current implementation on my device (master build)? It's using the correct bb on my flame already (looks exactly the same as your "After"). Thanks!
Flags: needinfo?(cawang)
Excuse me carrie, you are right in comment 8. The after was before and before was after hehehe. I have updated the screenshot with correct after/before label.
Attachment #8515828 - Attachment is obsolete: true
Attachment #8518824 - Flags: ui-review?(cawang)
ni? Harly for building block issue. Thanks!
Flags: needinfo?(fshih) → needinfo?(hhsu)
Comment on attachment 8518824 [details]

The input field is not following the building block. We need Harly's input on this one. Thanks!
Attachment #8518824 - Flags: ui-review?(cawang) → ui-review-
After discussion with the Framework team, since currently we don't have "value selector with input field as an item" in our standard Building Blocks. Therefore, it is not suggested to make a hack version of value selector. The team proposed to use a standard value selector, and when user taps "Custom", it will trigger an input dialog for user to input custom tag name.
Flags: needinfo?(hhsu)
Blocks: 994991
Whiteboard: visual design, UX-P2 → visual design, UX-P2, ux-most-wanted-nov2014
Depends on: 1102134
Hey Harly, could you please review that again with the framework team?
Please check: (3rd example: inputs)

As we discussed in the past value selectors and action menus are to strict, so we created object menu as a way to implement more flexible modal structures.
Flags: needinfo?(hhsu)
Attached image 2014-11-23-08-36-07.png
Hi Arnau, 
Thanks for bringing this up. Currently in our Building Blocks, it is defined that Object menus are accessed using a "press-and-hold" gesture on a selectable object ( Which in this case, doesn't fit this scenario. Also, due to the fact that in the edit contact page, the "Home", "Personal" and "Birthday" fields all use a triangle at the bottom right corner to indicate that it should trigger a value selector when pressed(please refer to the attach screenshot). Therefore, the Framework team suggested that it should trigger a value selector first, and then when user selects "Custom", it then opens an input dialog for user to input custom tag. Hope this answer your question.
Flags: needinfo?(hhsu)
Paco, you should create a new patch following Harly's comment, please.
Attached image alertCustom.png (obsolete) —
Comment on attachment 8529032 [details]

Hi Harly,

Regarding your comment 12, could you check if you want this?

Attachment #8529032 - Flags: feedback?(hhsu)
Hi Paco,
Thank you for making the modification, I just have 2 comments here:
1. Are you using a standard value selector like the one defined here ( Because, typically a single select value selector will only have a cancel button at the bottom, but the screenshot you've provided have cancel and done button. 

2. Another thing is that could you remove the chevron (>) on the right side of create custom? We don't really a pattern of a chevron within value selector now.

Attachment #8529032 - Flags: feedback?(hhsu) → feedback-
Attached image tag-select-contacts.png
Attachment #8529032 - Attachment is obsolete: true
Comment on attachment 8529698 [details]

Hi, could you recheck this?
Attachment #8529698 - Flags: feedback?(hhsu)
Paco, all looks good to me, I just have one question. After tapping the done button in "edit custom" page, does it go back to the edit contact page? or the "custom selected" page?
(In reply to Harly Hsu from comment #21)
> Paco, all looks good to me, I just have one question. After tapping the done
> button in "edit custom" page, does it go back to the edit contact page? or
> the "custom selected" page?
You go back to "edit contact page". Is it ok?
Comment on attachment 8529698 [details]

Yes, that's just what I wanted. Thanks.
Attachment #8529698 - Flags: feedback?(hhsu) → feedback+
Comment on attachment 8532518 [details] [review]
patch in github v2

Hi Cantera, could you review this?
Attachment #8532518 - Flags: review?(jmcf)
Whiteboard: visual design, UX-P2, ux-most-wanted-nov2014 → visual design, UX-P2, ux-most-wanted-nov2014, 2x-uxnom
Attachment #8532518 - Flags: review?(jmcf)
Assignee: pacorampas → nobody
Harly - do you know if this is still an issue? Thanks!
Flags: needinfo?(hhsu)
Whiteboard: visual design, UX-P2, ux-most-wanted-nov2014, 2x-uxnom → visual design, UX-P2, ux-tracking
Hi Tiff, the issue still exists in the current contact app.
Flags: needinfo?(hhsu)
Whiteboard: visual design, UX-P2, ux-tracking → visual design, UX-P2, ux-tracking, 2.6UXnom
Firefox OS is not being worked on
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.