[Address book] After leaving Edit mode, the contacts cover the Header
Bug #1211710 reported by
Christina Li
on 2013-08-13
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Ubuntu UI Toolkit |
Fix Released
|
Undecided
|
Unassigned | |
| | Ubuntu UX |
Undecided
|
Olga Kemmet | ||
| | address-book-app |
Medium
|
Renato Araujo Oliveira Filho | ||
| | address-book-app (Ubuntu) |
Undecided
|
Unassigned | ||
| | Trusty |
Undecided
|
Unassigned | ||
| | ubuntu-ui-toolkit (Ubuntu) |
Undecided
|
Unassigned | ||
| | Trusty |
Undecided
|
Unassigned | ||
Bug Description
Current situation:
After leaving Edit mode to return to the normal view of the contact list- the top of the contact list covers the Header component. When you start scrolling the contact list the problem disappears.
Desired solution:
The contact list should never cover the Header.
Christina Li (christina-li)
on 2013-08-13
| Changed in ubuntu-ux: | |
| status: | New → Fix Committed |
| assignee: | nobody → Christina Li (christina-li) |
Rachel Liu (rachelliu)
on 2013-08-28
| tags: | added: addressbk-aug-2013 |
| Bill Filler (bfiller) wrote : | #1 |
| Changed in address-book-app: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Renato Araujo Oliveira Filho (renatofilho) |
I will add the ubuntu-ui-toolkit since the fix for this bug will need changes on SDK.
| Pat McGowan (pat-mcgowan) wrote : | #3 |
This is working correctly so closing the bugs.
| Changed in ubuntu-ui-toolkit: | |
| status: | New → Fix Released |
| Changed in address-book-app (Ubuntu Trusty): | |
| status: | New → Fix Released |
| Changed in ubuntu-ui-toolkit (Ubuntu Trusty): | |
| status: | New → Fix Released |
| Changed in address-book-app: | |
| status: | Confirmed → Fix Released |
Olga Kemmet (olga-kemmet)
on 2014-07-07
| Changed in ubuntu-ux: | |
| assignee: | Christina Li (christina-li) → Olga Kemmet (olga-kemmet) |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
most likely an sdk bug