1119867 - Recently added Track shows at bottom of the recently added music list

Status: RESOLVED DUPLICATE of bug 1134229

(Firefox OS Graveyard :: Gaia::Music, defect)

Description

[Mahir Labib Chowdhury]

User Agent: Mozilla/5.0 (Windows NT 6.3; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20141231004008

Steps to reproduce:

1. Open Music App
2. Click "Playlist" button
3. Select Recently Added


Actual results:

The most recently added track is on the bottom of the list


Expected results:

The recently added track should be on the top of the list. The list should show reversed.

Comment 1

[Mahir Labib Chowdhury]

Can you check this?

Comment 2

[GoodMike]

N? the UX owner, Jacqueline to verify the isuue.
Hi Jacqueline, please help to check. Thank you.

Comment 3

[Dominic Kuo [:dkuo]]

(In reply to Mahir Labib Chowdhury from comment #1)
> Can you check this?

Hi Mahir, would you please describe how you add your new track and probably attach your test file here? it will be very helpful if you could add more information about this issue, which should help us to narrow down the problem quickly, thanks.

Comment 4

[GoodMike]

Dominic is working on solving the issue with Mahir based on UX spec.

Comment 5

[Mahir Labib Chowdhury]

(In reply to Dominic Kuo [:dkuo] from comment #3)

> Hi Mahir, would you please describe how you add your new track and probably
> attach your test file here? it will be very helpful if you could add more
> information about this issue, which should help us to narrow down the
> problem quickly, thanks.

Actually I downloaded some files and transferred with Bluetooth, the same result each time.

Comment 6

[Mahir Labib Chowdhury]

any update on this? I'm still having this issue on v3.0

Comment 7

[Dominic Kuo [:dkuo]]

(In reply to Mahir Labib Chowdhury from comment #6)
> any update on this? I'm still having this issue on v3.0

I can reproduce this issue with master build, should be a regression, taking this.

Comment 8

[Safwan Rahman (:safwan)]

Confirming this! :)

Comment 9

[Safwan Rahman (:safwan)]

Mahir, can you please let know Which build you have used to reproduce the issue? It will be help to get the Regression!
As you have filled this Bug at 9th January, so you have used any build made before 9th January. I am trying to find out the regression

Comment 10

[Safwan Rahman (:safwan)]

It seems that this problem is happened for a commit landed between 6th November 2014 to 7th November 2014.

I have tested with Gaia build of 6th November but could not get reproduce it.
But, with Gaia build of 7th November, I could reproduce the issue.
so it seems that this issue is caused by any commit landed between this time frame

Comment 11

[Safwan Rahman (:safwan)]

Oh! Got it. Only one commit landed between the Time frame. (2014-11-06 to 2014-11-07).

So I think this commit is responsible for the issue

https://github.com/mozilla-b2g/gaia/commit/ba627cf2f2fbcbb5e47be207e6411e79b2348b01

Dominic, As you have made the commit, Can you please re check why that commit is raising this issue?

Comment 12

[Mahir Labib Chowdhury]

I think you've already found it :)

Comment 13

[Safwan Rahman (:safwan)]

Bahaj, it seems to be affect 2.1. is it possible to block 2.1?

Comment 14

[Dominic Kuo [:dkuo]]

(In reply to Safwan Rahman from comment #11)
> Dominic, As you have made the commit, Can you please re check why that
> commit is raising this issue?

It's a refactoring commit so caused regressions, sorry about that but thanks to Hub, he has a patch in bug 1134229 which also fixes this, I am going dup it.

Comment 16

[bhavana bajaj [:bajaj]]

(In reply to Safwan Rahman from comment #13)
> Bahaj, it seems to be affect 2.1. is it possible to block 2.1?

Hmm, given its a regression we could consider depending on risk...

:hub/hema, thoughts on getting patch in https://bugzilla.mozilla.org/show_bug.cgi?id=1134229 uplifted to 2.1 given its busted since then?

Comment 17

[Hema Koka [:hema]]

(In reply to bhavana bajaj [:bajaj] from comment #16)
> (In reply to Safwan Rahman from comment #13)
> > Bahaj, it seems to be affect 2.1. is it possible to block 2.1?
> 
> Hmm, given its a regression we could consider depending on risk...
> 
> :hub/hema, thoughts on getting patch in
> https://bugzilla.mozilla.org/show_bug.cgi?id=1134229 uplifted to 2.1 given
> its busted since then?

Bajaj: Are we still landing patches to 2.1? 

Also can you get QA to verify if Hub's fix addresses this issue on master/2.2 first?

Thanks
Hema

Comment 18

[bhavana bajaj [:bajaj]]

(In reply to Hema Koka [:hema] from comment #17)
> (In reply to bhavana bajaj [:bajaj] from comment #16)
> > (In reply to Safwan Rahman from comment #13)
> > > Bahaj, it seems to be affect 2.1. is it possible to block 2.1?
> > 
> > Hmm, given its a regression we could consider depending on risk...
> > 
> > :hub/hema, thoughts on getting patch in
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1134229 uplifted to 2.1 given
> > its busted since then?
> 
> Bajaj: Are we still landing patches to 2.1? 
Serious blocking regressions with low risk are getting landed, hence wanted to check with you if you think this is one of those cases. I am on the fence but given this was requested from a dogfooder hitting this regression in 2.1, i assume this could be a common case and wanted to follow-up with you.
> 
> Also can you get QA to verify if Hub's fix addresses this issue on
> master/2.2 first?
Sure, I've requested verification.
> 
> Thanks
> Hema

Comment 19

[Hubert Figuiere [:hub]]

We should discuss whether we want this in 2.1 on bug 1134229 since this is were the fix lives.