Closed Bug 970874 Opened 10 years ago Closed 10 years ago

[Contacts] When import contacts appear wrong screen

Categories

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

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lolimartinezcr, Unassigned)

Details

(Keywords: regression)

Attachments

(4 files)

Tested (02/11/2014)
1.3
Gecko 06f88fa
Gaia 00cd1ae

Steps:
1. Press contacts aplication.
2. Press "settings"
3. Press "Import" contacts
4. Press "Gmail" option
5. Insert Login and password and press "OK" button (appear a screen "Please hold on..."
6. Select  contacts and import it

Actual result:
You can see attached screen.

Expected result:
You can see list of contacts directly.

This screen also can see when i import contacto to Facebook (but it shows very quickly)
blocking-b2g: --- → 1.3?
Keywords: regression
Summary: [Contacts] [Contacts] When import contacts appear wrong screen → [Contacts] When import contacts appear wrong screen
What exactly is the behavior on 1.2?
Keywords: qawanted
Tested again 02/12/2014
1.3
Gecko 3820ecd
Gaia 01e9da4

Steps:
1. Press contacts aplication.
2. Press "settings"
3. Press "Import" contacts
4. Press "Gmail" option (with 300 contacts in gmail server)
5. Insert Login and password and press "OK" button (appear a screen "Please hold on..."
6. Select  contacts and import it


1.2
Gecko 7375ace
Gaia 724d367
Behabior on 1.2: When import is finished you can see "Import Contact" screen directly you can't see attached image screen.
I need more information than that - what screen is seen on 1.2? What's the user impact of this bug?
(In reply to Jason Smith [:jsmith] from comment #3)
> I need more information than that - what screen is seen on 1.2? What's the
> user impact of this bug?

Once the import process is completed, we can see different behavior in v1.2 and v1.3:
v1.3: "device-2014-02-11-122653.png" screen appears during a few seconds before appearing the expected one "2014-02-12-11-06-43.png"

v1.2: Appear expected screen "2014-02-12-11-06-43.png"
Attached image 2014-02-12-11-06-43.png
Can we get a video here on the bug? Sorry, I'm still having trouble nailing down the severity of the impact of this bug.
Attached video VID_0005.3gp
(In reply to Loli from comment #7)
> Created attachment 8374881 [details]
> VID_0005.(In reply to Loli from comment #7)
> Created attachment 8374881 [details]
> VID_0005.3gp


Seconds: 1.19, once finish import process during an second you can see an intermediate screen
Minus for 1.3 the user impact is fairly low
blocking-b2g: 1.3? → -
Nominating for v1.4 as it's a regression
blocking-b2g: - → 1.4?
Looks like QA attention is no longer needed it has been answered in comment 2, removing "QA Wanted" for now
Keywords: qawanted
(In reply to Maria Angeles Oteo (:oteo) from comment #10)
> Nominating for v1.4 as it's a regression

I think we were clear in triage that this was a very minor regression, so I don't see why we would block 1.4 if we decided to not block this bug for 1.3.
We use to block on regressions, correct me if I wrong.

From my user point of view it's an ugly screen (attachment 8374881 [details]) that we should fix in v1.4 specially because it was working fine before. I understand that it's very late for v1.3 but for sure it's something we should fix in current v1.4 version.
(In reply to Maria Angeles Oteo (:oteo) from comment #13)
> We use to block on regressions, correct me if I wrong.

Not all regressions. We'll block on most regressions unless they are exceedingly minor.

> 
> From my user point of view it's an ugly screen (attachment 8374881 [details]
> [details]) that we should fix in v1.4 specially because it was working fine
> before. I understand that it's very late for v1.3 but for sure it's
> something we should fix in current v1.4 version.

See the video here - the screenshot here I think hides the truth of the severity of the bug. Triage thought this bug was minor because the image only appears for a second during a transition. From a user's point of view, they wouldn't even notice the weird UI, as they wouldn't be able to disect the UI within a second. It's certainly a papercut though.
I know the screen is shown very fast, perhaps I already have QA eyes which I should start worrying me ;)

Removing 1.4? Let's try to find a fix first and ask for approval later
blocking-b2g: 1.4? → ---
Hi,

I'm not able to reproduce this issue in master, environmental variables:
Device: hamachi
BuildId: 20140313064116
Gecko: 7312341
Gaia: b5d0f9b
Platform version: 30.0a1

asking qawanted to re-confirm. Thanks!
Keywords: qawanted
QA Contact: sarsenyev
I see the issue as described in comment 14 and the video attachment 1 [details] [diff] [review]min. 19sec. on the latest 1.4
I'm not sure why it's mentioned a different behavior in 1.2, but the same behavior can be seen on 1.2 
During a transition user can see the image for a second
 
1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140314040202
Gaia: ea9e23abea5933656555d849b922c8da7530c90b
Gecko: fe40387eba1a
Version: 30.0a1
Firmware Version: v1.2-device.cfg
Keywords: qawanted
QA Contact: sarsenyev
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: