Closed
Bug 813097
Opened 12 years ago
Closed 12 years ago
Evme - Shortcuts removal mode searchbar
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: evyatar, Assigned: evyatar)
Details
Attachments
(1 file)
3.87 KB,
patch
|
crdlc
:
review+
vingtetun
:
approval-gaia-v1+
|
Details | Diff | Splinter Review |
When entering "remove mode" in shortcuts (Tap and Hold a shortcut)- the Searchbar is still active, and focusing on it breaks the UI.
Assignee | ||
Comment 1•12 years ago
|
||
Pull Request: https://github.com/mozilla-b2g/gaia/pull/6496
Attachment #683103 -
Flags: review?(crdlc)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → evyatar
Comment 2•12 years ago
|
||
How can I enter in "remove mode"
Assignee | ||
Comment 3•12 years ago
|
||
Tap and Hold a shortcut icon- the view should change, and all shortcuts should have X icons on top of them.
Comment 4•12 years ago
|
||
Comment on attachment 683103 [details] [diff] [review] Fade out the searchbar and make it inactive during removal mode NOTE: If blocking-basecamp+ is set, just land it for now. [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: Testing completed: Risk to taking this patch (and alternatives if risky):
Attachment #683103 -
Flags: review?(crdlc)
Attachment #683103 -
Flags: review+
Attachment #683103 -
Flags: approval-gaia-master?(21)
Updated•12 years ago
|
Component: Gaia → Gaia::Homescreen
Comment 5•12 years ago
|
||
Comment on attachment 683103 [details] [diff] [review] Fade out the searchbar and make it inactive during removal mode Review of attachment 683103 [details] [diff] [review]: ----------------------------------------------------------------- Late feature work.
Attachment #683103 -
Flags: approval-gaia-master?(21) → approval-gaia-master+
Comment 6•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/43e0fb8d372e4889f8d2b04d45d4137de3018925
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•