Closed
Bug 1024623
Opened 10 years ago
Closed 10 years ago
[Vertical] Add collections to customization of vertical homescreen
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(b2g-v2.0 fixed, b2g-v2.1 verified)
VERIFIED
FIXED
2.0 S4 (20june)
People
(Reporter: sonmarce, Assigned: macajc)
References
Details
(Whiteboard: [systemsfe])
Attachments
(2 files)
52 bytes,
text/plain
|
kgrandon
:
review+
bajaj
:
approval-gaia-v2.0+
|
Details |
317.05 KB,
image/png
|
Details |
Follow up of bug 1006172 for adding collections to customization of vertical homescreen
Reporter | ||
Updated•10 years ago
|
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8440354 -
Flags: review?(kgrandon)
Comment 2•10 years ago
|
||
Comment on attachment 8440354 [details]
V1 Proposed patch
I did not test this, but I assume you tested it. I left a few nits on github.
One thing I'm not very clear on - what pieces are there to hook this up to the collections app? Is there some IAC message we need to send?
Attachment #8440354 -
Flags: review?(kgrandon) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Collection app listens for a 'setup' msg before populating the collection database with the predefined collections. I believe bug 1020158 was filed to implement that (send msg). If nobody from e.me takes it, I'll take it myself. In fact, I have a version of that implemented already since I needed data on the collection database to test the collection customization and launching the setup process was the easiest way to fill the database since the rest of the code (in collection app) was already in place
Assignee | ||
Comment 4•10 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/dfc4703bb81d1fa4f2087a1a6124b47a80a5d1de
Assignee | ||
Comment 5•10 years ago
|
||
Comment on attachment 8440354 [details] V1 Proposed patch 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 #):Implementation of the vertical homescreen [User impact] if declined: Collections on the homescreen will not be placed on the correct place according to the configuration file. This will difficult (or make impossible) to pass the certification process (since that's a requisite). [Testing completed]: yes [Risk to taking this patch] (and alternatives if risky): low [String changes made]: none
Attachment #8440354 -
Flags: approval-gaia-v2.0?(bbajaj)
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Updated•10 years ago
|
Attachment #8440354 -
Flags: approval-gaia-v2.0?(bbajaj) → approval-gaia-v2.0+
Comment 6•10 years ago
|
||
v2.0: https://github.com/mozilla-b2g/gaia/commit/97c21d64d47c4c27d332841173c61f273c46f0d4
Target Milestone: --- → 2.0 S4 (20june)
Verified the issue is fixed on 2.2, 2.1 Customization of collection that is placed to the home vertical screen Device: Flame 2.2 Master BuildID: 20141027040237 Gaia: e91d99e4d96954f06383c00bb9d79598a697e310 Gecko: 8230834302c9 Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89 Version: 36.0a1 (2.2 Master) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Device: Flame 2.1 BuildID: 20141027001201 Gaia: c97463d61f45513a2123b19610386ddbfc916819 Gecko: 4f8c0c021128 Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89 Version: 34.0 (2.1) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
This issue still reproduces on Flame 2.0. A new added collection is placed below divider of smart collection and placed to the another collection Leaving verifyme keyword for 2.0 verification. Flame 2.0 KK Flame 2.0Device: BuildID: 20141027000202 Gaia: 2183b4f3ec0eb47ab1f133c31732ec53b08ad253 Gecko: 43bee45176c4 Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89 Version: 32.0 (2.0) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Follow-up bug is opened bug 1083297 as result of failed verification on 2.0
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage?] [failed-verification]
Flags: needinfo?(ktucker)
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•