Closed
Bug 813871
Opened 12 years ago
Closed 9 years ago
[music] alphabetization of albums and artists should be case-insensitive
Categories
(Firefox OS Graveyard :: Gaia::Music, defect)
Tracking
(blocking-b2g:-, b2g-v1.3T affected, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)
RESOLVED
DUPLICATE
of bug 1209135
blocking-b2g | - |
People
(Reporter: dkuo, Unassigned)
References
Details
(Keywords: polish, Whiteboard: permafail)
Attachments
(1 file)
50.23 KB,
image/png
|
Details |
In Music album and artist lists, alphabetization is case-sensitive now, should be case-insensitive.
This issue is still reproducing on Unagi Build ID: 20130322070203 Environmental Variables: Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/4931ec89ebbe Gaia: 85fd164691bb852f1cfaf82405df4380629ced6e
Reporter | ||
Updated•11 years ago
|
Comment 3•11 years ago
|
||
Comment 4•11 years ago
|
||
Nominating since this will likely be an issue for people with their music collections. See attached screenshot for an example.
blocking-b2g: --- → leo?
Comment 6•11 years ago
|
||
Dominic, Does IndexedDB all you to do a case-insensitive search? If not, I suppose you might need to store a lowercase version of the album and artist names in the metadata to use as a sort key. When you change your MediaDB schema like this, you should be able to increment the version number passed to the MediaDB() constructor and that should automatically trigger a complete re-scan of everyone's music collections. (The alternative is to make everyone do make reset-gaia.) I'm not sure that I've ever done that myself, but that was the intent of the version number option to the constructor.
Reporter | ||
Comment 7•11 years ago
|
||
David, Yes, to save a lowercase version of the album and artist names in the metadata as a sort key should be a suitable solution and that's why I filed this bug as you already suggested me while I was implementing the alphabetization in Music app. I haven't try to change the version of MediaDB but that might be a better way to update the MediaDB for users because people probably will forget to make reset-gaia to verify this bug.
We can't require a reset-gaia since that won't happen when end users update from v1.0 to v1.1
Comment 9•11 years ago
|
||
Reviewed in leo+ mega-triage. There's no solid criteria by which we can block on this: no crash, no dataloss, no critical functionality broken, etc. Would love a patch, but not holding a release on getting this fixed.
blocking-b2g: leo+ → -
Updated•10 years ago
|
status-b2g-v1.4:
--- → affected
Whiteboard: burirun1.4-2
Updated•10 years ago
|
status-b2g-v1.3T:
--- → affected
Whiteboard: burirun1.4-2 → burirun1.4-2, 1.3tarakorun2
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → affected
Flags: needinfo?(dharris)
Whiteboard: burirun1.4-2, 1.3tarakorun2 → permafail
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Reporter | ||
Updated•9 years ago
|
Assignee: dkuo → nobody
Comment 13•9 years ago
|
||
Hubert - please remember to move over affected flags and information when duping a bug. ------------------------------------------------------------------------------------------ This issue occurs on Flame in 3.0, 2.2 (v18d-1), 2.2 (v18d), 2.1 (v18d-1), and 2.0 (v18d-1) Environmental Variables: Device: Flame 3.0 Build ID: 20150204010225 Gaia: dfebaaa8aab43470f482d09d71137bab840c3ae9 Gecko: 0c2f7434c325 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 38.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0 Device: Flame 2.2 (KK - Nightly - Full Flash) Build ID: 20150202002507 Gaia: d6141fa3208f224393269e17c39d1fe53b7e6a05 Gecko: be206fa2fb60 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 37.0a2 (2.2) Firmware Version: v18d-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Device: Flame 2.2 (KK - Nightly - Full-Flashed) Build ID: 20150202002507 Gaia: d6141fa3208f224393269e17c39d1fe53b7e6a05 Gecko: be206fa2fb60 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 37.0a2 (2.2) Firmware Version: v18d User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Device: Flame 2.1 (KK - Nightly - Full-Flashed) Build ID: 20150202001432 Gaia: 63f291df9b9ad8498fb8fc7fb8bf070524406a5c Gecko: 70b8982a523d Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.0 (KK - Nightly - Full-Flashed) Build ID: 20150202000205 Gaia: 2989f2b2bd12fcc0e9c017d2db766e76a55873b8 Gecko: b961877cacba Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 32.0 (2.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•