Closed Bug 809076 Opened 13 years ago Closed 13 years ago

[UX VD] Drawer. Contact icon should not be there, is not a valid button.

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect, P3)

x86
macOS

Tracking

(blocking-b2g:-, b2g18+ fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)

RESOLVED FIXED
blocking-b2g -
Tracking Status
b2g18 + fixed
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- fixed

People

(Reporter: vicky, Assigned: steveck)

References

Details

(Whiteboard: interaction, UX-P1, [TEF_REQ], PRODUCT-CONSISTENCY, [TEF UX Critical])

Attachments

(1 file)

The "contact" icon next to the Email users name is not correct, is not ment to have an icon there, and if needed is not that one. Please specify why is it placed there.
Assignee: nobody → schung
Severity: normal → major
Hi Peter, Based on the https://www.dropbox.com/sh/ygwfxk6chpshxdj/ct4nwRk2r3/Apps/Email/mail-settings.pdf We will need an account button for account selection. Is there any icon for the account button? Thanks.
Flags: needinfo?(pla)
Keywords: polish
Priority: -- → P3
Keywords: polish
Whiteboard: interaction, UX-P1, [TEF_REQ]
Whiteboard: interaction, UX-P1, [TEF_REQ] → interaction, UX-P1, [TEF_REQ], PRODUCT-CONSISTENCY
Hi Steve, Yes, as Casey said, this should be the back arrow we use in the other headers. I do find it still feels odd in that you tap "<" to go to accounts, which makes the screen pan right (this is fine), but then when you tap "<" again, the screen pans to the left to go back... Steve, can you make the arrow swap? Please use a common component if you can.
Flags: needinfo?(pla)
Whiteboard: interaction, UX-P1, [TEF_REQ], PRODUCT-CONSISTENCY → interaction, UX-P1, [TEF_REQ], PRODUCT-CONSISTENCY, [TEF UX Critical]
blocking-b2g: --- → tef?
NOTE: If blocking-basecamp+ is set, just land it for now. [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: User will see the button with misleading icon. Testing completed: Risk to taking this patch (and alternatives if risky): None
Attachment #711233 - Flags: review?(bugmail)
Attachment #711233 - Flags: approval-gaia-v1?
blocking-b2g: tef? → tef+
Comment on attachment 711233 [details] Patch for applying the correct button image Go ahead with uplift once this is reviewed +
Attachment #711233 - Flags: approval-gaia-v1?
It has been decided that the UX bugs will track, not block for v1.0.1 and we'll consider uplift (please nominate when review is given) but we'll have to discuss targeting v1.1 depending on risk/reward.
blocking-b2g: tef+ → -
tracking-b2g18: --- → +
(In reply to Peter La from comment #3) > Steve, can you make the arrow swap? Please use a common component if you > can. There's no explicit building block style for this. There is a back-rtl.png, but that's only referenced by an rtl selector, so I don't think we want to hard-code that hack in and then get regressed if building blocks changes internally. We can do "transform: scaleX(-1)" but I'm a little worried about such a hack having a performance impact on us. Can you get the building blocks updated to have an explicit icon-forward or something like that? I'll r+ this as-is since Casey is in charge of this call.
Attachment #711233 - Flags: review?(bugmail)
Attachment #711233 - Flags: review+
Attachment #711233 - Flags: approval-gaia-v1?
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment on attachment 711233 [details] Patch for applying the correct button image Critical & low risk TEF UX change, approving for v1.0.1.
Attachment #711233 - Flags: approval-gaia-v1? → approval-gaia-v1+
This commit does not apply cleanly to v1-train. If this patch depends on another bug, please comment here and I will retry when that bug is approved to land on all branches that this bug needs to land on. If the merge conflict needs to be resolved by hand, the following commands could be a useful starting point: cd gaia git checkout v1-train git cherry-pick -x -m1 8024254338e230e8635602ce0015beb4e9bb28ef <resolve merge conflict>
Wow, was not easy to find out dependencies here, but finally I got it: It seems that you need to apply Bug 798258, that needs Bug 798292 to apply, in v1-train for cleanly apply this one. So after applying in v1: git cherry-pick d6cae68b2b7396b4708eab765b5c8164b5a75091 git cherry-pick 11c850e81064996147704aeef94c3043a3f9240a your STR will cleanly apply. I wouldn't say that is dependency, cause the whole problem comes when cleaning a trailing space at the end of a line that was inserted by the Commits of the previous bugs. I don't know what's the better way of fixing this... Ideas?
Alberto and I discussed this on IRC. Alberto merged the patch by hand, thanks! v1-train: b31a0fa9fa27638c8eb14c7c4d8abfd5511cb310
So, it looks like we didn't want one of those images to be removed yet since we haven't uplifted the fix for bug 808576 that changes us to use the built-in spinners.
(In reply to Andrew Sutherland (:asuth) from comment #14) > So, it looks like we didn't want one of those images to be removed yet since > we haven't uplifted the fix for bug 808576 that changes us to use the > built-in spinners. Problem solved by way of uplifting bug 808576.
Batch edit: bugs fixed on b2g18 since 1/25 branch of v1.0 are fixed on v1.0.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: