Closed
Bug 947099
Opened 11 years ago
Closed 11 years ago
[Dialer] Update tab bar to new 1.3 visual designs
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(b2g-v1.3 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | affected |
People
(Reporter: epang, Assigned: pivanov)
References
Details
(Whiteboard: ux-tracking, visual design, visual-tracking, bokken)
Attachments
(4 files, 1 obsolete file)
There are a couple of updates needed for dialer
1. Update tab bars to new 1.3 visual designs.
2. Update layout to allow for a 45px tab bar (instead of 40px)
See attachments.
Reporter | ||
Comment 1•11 years ago
|
||
Layout update specs
Assignee | ||
Comment 2•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #8343603 -
Flags: review?(anthony)
Reporter | ||
Comment 4•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
Hi Fabrice, can you help review Pavel's patch? thanks in advance :)
Attachment #8343603 -
Flags: review?(anthony) → review?(fabrice)
Updated•11 years ago
|
Attachment #8343603 -
Flags: review?(fabrice) → review?(anthony)
Reporter | ||
Comment 5•11 years ago
|
||
Hey Antony, I just wanted to note that the patch from this bug needs is dependent with the patch from https://bugzilla.mozilla.org/show_bug.cgi?id=947093
They will land together along with all other toolbar updates to remain consistent. Thanks!
Flags: needinfo?(anthony)
Comment 6•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
When I apply this patch on top of the patch from bug 947093, I can't see the blue bar at the bottom of the selected tab.
Also, why are we losing 5 precious pixels of vertical space for that bar?
Attachment #8343603 -
Flags: review?(anthony) → review-
Updated•11 years ago
|
Flags: needinfo?(anthony)
Assignee | ||
Comment 7•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
Hey Anthony,
sorry for the mistake was I typo (merge the wrong branch) anyway ... I think now it's ready for review. Thanks :)
Attachment #8343603 -
Flags: review- → review?(anthony)
Comment 8•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
One of the two changes are breaking one thing:
1) Go to the contacts tab
2) Click the "add a contact" button
Expected:
The tab bar should disappear.
Actual:
The content of the tab disappears but we still have a black 45px bar in the bottom.
This is also changing the background of the Call log header background but I don't know if that's intended.
I'm on PTO for the next three weeks so you should ask a review to someone else.
Attachment #8343603 -
Flags: review?(anthony) → review-
Reporter | ||
Updated•11 years ago
|
Whiteboard: ux-tracking, visual design, visual-tracking, jian → ux-tracking, visual design, visual-tracking, bokken
Assignee | ||
Comment 9•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
Hey Fernando,
can you take a look if you have time :). If not I will ask Etienne because we try to land this soon
Thanks :)
Attachment #8343603 -
Flags: review- → review?(ferjmoreno)
Comment 10•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
Hi Pavel! I am afraid that I am still seeing the visual issues that Anthony mentioned in comment 6.
Attachment #8343603 -
Flags: review?(ferjmoreno)
Comment 11•11 years ago
|
||
This is what I am seeing after applying your changes from https://github.com/pivanov/gaia/commit/343ad70664c5d88dd309feceb92e343592ccd4e0
Assignee | ||
Comment 12•11 years ago
|
||
Hey Fernando,
this but depends on Bug 947093 did you apply both?
Comment 13•11 years ago
|
||
Oh, there you go! Now it looks better! :)
Unfortunately, the bottom bar does not entirely disappear (only the icons do) and I am also seeing this issue when trying to add a new contact. Check the current call log version, the bottom bar needs to disappear entirely when adding a contact.
I also added a comment to https://github.com/pivanov/gaia/commit/3b3c795925ce11e5ad25aa112775934536343e78
Thanks Pavel!
Attachment #8350001 -
Attachment is obsolete: true
Comment 14•11 years ago
|
||
And sorry for the delay replying to comment 12. I usually do a complete bugmail pass once a day (first thing in the morning) and I only look at review/feedback/needinfo requests for the rest of the day. So if you want me to get back to this before tomorrow, set any of this flags on me, please :).
Reporter | ||
Comment 15•11 years ago
|
||
(In reply to Fernando Jiménez Moreno [:ferjm] (use needinfo instead of CC, please) from comment #14)
> And sorry for the delay replying to comment 12. I usually do a complete
> bugmail pass once a day (first thing in the morning) and I only look at
> review/feedback/needinfo requests for the rest of the day. So if you want me
> to get back to this before tomorrow, set any of this flags on me, please :).
Thanks for reviewing Fernando. The bottom toolbar should stay when adding a new contacts but like Fernando noticed the icons should be show. Thanks!
Flags: needinfo?(pivanov)
Assignee | ||
Comment 16•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
ahhh ... I merge the wrong branch ... sorry guys ... now everything should work (I test it few times)
Attachment #8343603 -
Flags: review?(ferjmoreno)
Flags: needinfo?(pivanov)
Comment 17•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
Thanks Pavel!
Attachment #8343603 -
Flags: review?(ferjmoreno) → review+
Assignee | ||
Comment 18•11 years ago
|
||
Landed to master:
https://github.com/mozilla-b2g/gaia/commit/ac1f7b71eaf1858c5a3f7ef87b55257dc4f9310e
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Doesn't this need to land in v1.3 branch in order for it to be marked fixed? I'm not sure what the protocol is; I am reopening this bug unless, there's a different way to track the bug being fixed for v1.3 branch.
Status: RESOLVED → REOPENED
Flags: needinfo?(pivanov)
Resolution: FIXED → ---
Comment 20•11 years ago
|
||
This should have landed in 1.3.
Updated•11 years ago
|
blocking-b2g: --- → 1.3?
Comment 21•11 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #19)
> Doesn't this need to land in v1.3 branch in order for it to be marked fixed?
> I'm not sure what the protocol is; I am reopening this bug unless, there's a
> different way to track the bug being fixed for v1.3 branch.
No, RESOLVED/FIXED indicates that it has landed on master. The scripts that will eventually uplift this to the proper branch depend on that status.
The right way to get this into the 1.3 conversation is to nominate it as kaze just did. If it gets approved for inclusion in 1.3 (via blocking-b2g:1.3+), the uplift scripts will land it to the 1.3 branch and this bug will get marked with "status-b2g-v1.3:fixed".
Can you restore the FIXED status to this bug and the related issues under bug 947087?
Flags: needinfo?(pivanov) → needinfo?(nhirata.bugzilla)
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
status-b2g-v1.3:
--- → affected
Flags: needinfo?(nhirata.bugzilla)
Resolution: --- → FIXED
Comment on attachment 8343603 [details]
patch for Gaia/master
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
[User impact] if declined:
[Testing completed]:
[Risk to taking this patch] (and alternatives if risky):
[String changes made]:
Attachment #8343603 -
Flags: approval-gaia-v1.3?
Needs approval. Please approve?
Flags: needinfo?(praghunath)
Updated•11 years ago
|
blocking-b2g: 1.3? → ---
Comment 24•11 years ago
|
||
Comment on attachment 8343603 [details]
patch for Gaia/master
approved for 1.3 gaia per triage
Attachment #8343603 -
Flags: approval-gaia-v1.3? → approval-gaia-v1.3+
Flags: needinfo?(praghunath)
Comment on attachment 8343603 [details]
patch for Gaia/master
We are no longer taking the tab change in 1.3; we will have it in 1.4
Attachment #8343603 -
Flags: approval-gaia-v1.3+ → approval-gaia-v1.3-
You need to log in
before you can comment on or make changes to this bug.
Description
•