990493 - [Sora][Contacts] MS flashed a white screen when user import contacts

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect, P2)

Description

[sync-1]

the latest id: Mozilla build ID: 20140312164001 FFOS: 1.3
 
 DEFECT DESCRIPTION:
  MS flashed a white screen when user import contacts.
 
  REPRODUCING PROCEDURES:
  Precondition: Disable screen lock.
  1. Idle -> Contacts -> Tap "Settings" icon -> Import contacts -> Memory card/ SIM card -> Press power key to unlight screen -> Press power key again to light screen ->  MS flashed a white screen(K.O)
 
 1.1 also have this problem.
 
  EXPECTED BEHAVIOUR:
  MS should not flashed a white screen
  
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE: 100%

Comment 1

[sync-1]

Attachment: Video for this PR

Comment 3

[Jack Liu]

Dears, 

991453 has 100% reproduce rate, it's IOT blocker.

Comment 4

[Jason Smith [:jsmith]]

Not a regression, so this isn't a blocker.

Comment 6

[Jack Liu]

Hi Jason,

Actually bug#991453 you duplicated on this is regression, it's ok in Buri 1.1, please check.

Shall I reopen bug#991453 or set blocking flag on this?

And I also don't agree with you on blocker definition, carrier blocks TA on it even it's not regression bug.

Mozilla say new features in 1.3 aren't mature and ask to waive related bugs, but when OEM/Carrier accept it, in next version you say it's not blocker because OEM/Carrier already accept it in last shipment. It's confusion to us.

I'm not mean to offend anybody, please correct me if what I said is not truth.
 
Thanks.

Comment 7

[Jason Smith [:jsmith]]

(In reply to Jack Liu from comment #6)
> Hi Jason,
> 
> Actually bug#991453 you duplicated on this is regression, it's ok in Buri
> 1.1, please check.
> 
> Shall I reopen bug#991453 or set blocking flag on this?

I strongly doubt that. The white screen issue showing up with the lockscreen disabled to my understanding was present in 1.1.

> 
> And I also don't agree with you on blocker definition, carrier blocks TA on
> it even it's not regression bug.

In cases where the issue isn't a regression, we really need a compelling reason why this is needed. Were there support complaints? Is this issue more common now in 1.3 vs. 1.1? Those type of questions need to be answered to help determine the blocking need.

Do note that every patch we take poses regression risk. If we aggressively argue for too many patches, then we'll risk ending up in a never ending cycle in product development to never actually ship the product. We push for the triage guidelines (https://wiki.mozilla.org/B2G/Triage#Blocker_Triage_Guidelines) to help guide us on balancing the need for certain issues to be fixed vs. taking into the regression risk of each patch that is included.

> 
> Mozilla say new features in 1.3 aren't mature and ask to waive related bugs,
> but when OEM/Carrier accept it, in next version you say it's not blocker
> because OEM/Carrier already accept it in last shipment. It's confusion to us.

I agree there's a problem with waiver tracking. This problem is being looked into.

Comment 8

[Jack Liu]

Hi Jason,

Thanks for your reply.

We have found bug#991453 is 100% reproduce rate on Sora but not on Buri 1.1, please confirm.

I understand that every patch may introduce new regression issues, but issue like this will make bad impression on end user. We must give confidence to user, although FirefoxOS is new and with limited features but it's stable and friendly.

Comment 9

[Jason Smith [:jsmith]]

(In reply to Jack Liu from comment #8)
> Hi Jason,
> 
> Thanks for your reply.
> 
> We have found bug#991453 is 100% reproduce rate on Sora but not on Buri 1.1,
> please confirm.
> 
> I understand that every patch may introduce new regression issues, but issue
> like this will make bad impression on end user. We must give confidence to
> user, although FirefoxOS is new and with limited features but it's stable
> and friendly.

Okay - I reopened bug 991453 to track it separately.

Comment 10

[Tim Guan-tin Chien [:timdream] (please needinfo)]

I highly suspect the root cause is the same even if these two bug have different reproducible range.

It's likely the bug is only visible when the platform/layout is stressed to a certain point. "SIM Card Import" which requires a lot of disk write make it a good candidate.

We should see if fixing bug 991453 will make this bug disappear.

Comment 11

[Warren WU]

(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #10)
> I highly suspect the root cause is the same even if these two bug have
> different reproducible range.
> 
> It's likely the bug is only visible when the platform/layout is stressed to
> a certain point. "SIM Card Import" which requires a lot of disk write make
> it a good candidate.
> 
> We should see if fixing bug 991453 will make this bug disappear.

bug 991453 do the CSS modification to solve,this problem still exists.

Comment 12

[Wesly Huang (EPM)]

link all Fire C (codename: Sora) bugs to a meta one.

Comment 13

[BMO Automation]

Firefox OS is not being worked on