1069827 - The index letter of contacts is inconsistent with the real contacts displayed.

Status: RESOLVED INVALID

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

Description

[Rachelle Yang [:ryang][[e-mail]]]

Reproduce steps:
If we have a list of contacts and try to quickly go to a letter, for example going from 'A' to 'Z' while scrolling the index list, or quickly tapping a single letter, inconsistency between the index letter of the contact and the real contacts displayed  is observed.

Comment 1

[Johan Lorenzo [:jlorenzo]]

I am not able to reproduce with today's 2.1 build on my Flame. Can you provide a video?

Comment 2

[Rachelle Yang [:ryang][[e-mail]]]

Attachment: incosistent contact display

Comment 3

[Rachelle Yang [:ryang][[e-mail]]]

Hi Johan, the issue happened on 2.0.
Could you please kindly try on 2.0 build again ? 
And I also attach the picture for your reference in comment 2.
In the attachment, you could see the index is "Q" while the contacts displayed are "M" category.

Comment 4

[Francisco Jordano [:arcturus] [:francisco]]

Rachelle, could you confirm if you have contacts on that letter.

The way it works is the following, the contacts shortcuts is always available, but if you don't have contacts in one specific letter while you are sliding, the contacts list won't jump to that letter (since it doesn't exist a contacts group for that)

Comment 5

[Johan Lorenzo [:jlorenzo]]

I can't repro on 2.0 either. Rachelle, can you check what Francisco mentioned in comment 4?

Comment 6

[Rachelle Yang [:ryang][[e-mail]]]

Hi Johan and Francisco, thank you so much for your feedback.

I have confirmed the comment4 from Francisco. 
There are no contacts available for that specific index letter. Thus, may I know if under this circumstance, what contacts ( which letter of contacts )will be displayed if that specific index letter doesn't have any corresponding contacts?

Will it be randomly selected or any rule to follow ?
Thank you very much.

Comment 7

[Johan Lorenzo [:jlorenzo]]

I didn't see the implementation, but from what I see with my data: it goes to the last letter with contacts (M in your case) depending on which way you scroll (from A to Z in your case). So if you scroll from Z to A, it should stay at your R, S or T contacts.

Comment 8

[Francisco Jordano [:arcturus] [:francisco]]

(In reply to Johan Lorenzo [:jlorenzo] from comment #7)
> I didn't see the implementation, but from what I see with my data: it goes
> to the last letter with contacts (M in your case) depending on which way you
> scroll (from A to Z in your case). So if you scroll from Z to A, it should
> stay at your R, S or T contacts.

Johan is right, it will jump when you have next available group of contacts (in contacts app, a group is a set of contacts under the same letter).

Also take into account that the loading of the list is happening at the same time that we are rendering, it takes a while until we get all the contacts, so sometimes if you are pretty fast trying to use the scroller wont have any results until all contacts have been loaded.

Comment 9

[Rachelle Yang [:ryang][[e-mail]]]

Thanks Francisco and Johan. Then May I conclude this bug should not be considered as an issue? 
Thank you very much.

Comment 10

[Johan Lorenzo [:jlorenzo]]

I think so. You can mark this issue as RESOLVED -> INVALID then.

Comment 11

[Rachelle Yang [:ryang][[e-mail]]]

Thank you very much, Johan.