Closed
Bug 1028691
Opened 10 years ago
Closed 10 years ago
[Collection app] Background images sometimes in poor quality
Categories
(Firefox OS Graveyard :: Gaia::Everything.me, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 verified, b2g-v2.1 verified)
People
(Reporter: ranbena, Assigned: ranbena)
References
Details
(Whiteboard: [systemsfe])
Attachments
(5 files)
Often newly added Smart Collections have a poor quality background image. When reopening the SC, it updates to a good quality image.
Assignee | ||
Updated•10 years ago
|
Comment 1•10 years ago
|
||
Need a screenshot of the poor quality wallpaper.
Assignee | ||
Comment 2•10 years ago
|
||
Right sorry. Having trouble with getting screenshots on the device for some reason..
Comment 3•10 years ago
|
||
(In reply to Ran Ben Aharon (Everything.me) from comment #2) > Created attachment 8444108 [details] > Screenshot.png > > Right sorry. Having trouble with getting screenshots on the device for some > reason.. Ok - we'll probably want to get a screenshot of the good quality image too as a point of comparison.
Assignee | ||
Comment 4•10 years ago
|
||
Since the collection.background can be updated by two processes - a) Collection create b) Collection view, the former requests a 170x170 image which is then displayed as the Collection content bg. Then gets overwritten with the full size bg. The fix simply keeps a record if the current bg image is full sized or not and displays only if it is.
Attachment #8444430 -
Flags: review?(kgrandon)
Assignee | ||
Comment 5•10 years ago
|
||
Kevin, I'd like to add a unit test with this patch though I think it'll require stubbing the api call. Not sure how to do that.
Comment 6•10 years ago
|
||
Comment on attachment 8444430 [details] [review] Pull Request James - mind if I pass this off to you? Totally swamped, thanks!
Attachment #8444430 -
Flags: review?(kgrandon) → review?(jlal)
Comment 7•10 years ago
|
||
Comment on attachment 8444430 [details] [review] Pull Request The code itself looks okay and seems to work but I think an integration test like https://github.com/mozilla-b2g/gaia/blob/master/apps/verticalhome/test/marionette/collection_test.js is a better bet then a unit test and should be fairly easy to implement (though I would start splitting up those tests)
Attachment #8444430 -
Flags: review?(jlal) → review+
Comment 8•10 years ago
|
||
Comment 9•10 years ago
|
||
The difference is slightly notable. This looks like a blocker to me. Do you confirm Jason?
Keywords: qawanted
Comment 11•10 years ago
|
||
(In reply to Johan Lorenzo [:jlorenzo] from comment #9) > The difference is slightly notable. This looks like a blocker to me. Do you > confirm Jason? I'll wait for Patryk to comment, but given the VD refresh priority needed for 2.0 I'm leaning towards yes.
Assignee | ||
Comment 12•10 years ago
|
||
Attaching a screenshot comparison. It's very noticeable imo.
Updated•10 years ago
|
blocking-b2g: --- → 2.0?
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking+]
Assignee | ||
Comment 14•10 years ago
|
||
Comment on attachment 8444430 [details] [review] Pull Request Updated the PR. No change to code, only added tests. James, I went for unit tests eventually because it seems more suitable to me in this specific case. Lmk if you have any questions about the tests implementation.
Attachment #8444430 -
Attachment description: WIP → Pull Request
Attachment #8444430 -
Flags: review+ → review?(jlal)
Comment 15•10 years ago
|
||
Comment on attachment 8444430 [details] [review] Pull Request LGTM - can you rebase/land this patch?
Attachment #8444430 -
Flags: review?(jlal) → review+
Assignee | ||
Comment 16•10 years ago
|
||
Landed on master: https://github.com/mozilla-b2g/gaia/commit/0486f10834bb0a582b0551f31981759f114d9e72
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 18•10 years ago
|
||
Please do, it needs rebasing anyway.
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → fixed
Flags: needinfo?(kgrandon)
Target Milestone: --- → 2.0 S5 (4july)
Assignee | ||
Comment 19•10 years ago
|
||
Landed on v2.0: https://github.com/mozilla-b2g/gaia/commit/34f4b94233a0e03ffbb3b84dc0ed1cc52df1df1a
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(padamczyk)
Updated•10 years ago
|
Comment 20•10 years ago
|
||
This issue has been successfully verified on Flame 2.0: Gaia-Rev 8d1e868864c8a8f1e037685f0656d1da70d08c06 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c756bd8bf3c3 Build-ID 20141201000201 Version 32.0 Device-Name flame FW-Release 4.4.2 This issue has been successfully verified on Flame 2.1: Gaia-Rev ccb49abe412c978a4045f0c75abff534372716c4 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22 Build-ID 20141201001201 Version 34.0 Device-Name flame FW-Release 4.4.2
You need to log in
before you can comment on or make changes to this bug.
Description
•