[Buri][Call]The incoming call number will disappear

RESOLVED WORKSFORME

Status

Firefox OS
Gaia::Dialer
P3
normal
RESOLVED WORKSFORME
5 years ago
3 years ago

People

(Reporter: sync-1, Unassigned)

Tracking

unspecified

Firefox Tracking Flags

(blocking-b2g:-)

Details

Attachments

(2 attachments)

log
20.35 KB, application/octet-stream
Details
247.73 KB, image/x-png
Details
(Reporter)

Description

5 years ago
Created an attachment (id=464820)
 PIC
 
 DEFECT DESCRIPTION:
 The incoming call number will disappear
 
 REPRODUCING PROCEDURES:
 Lock the screen first,
 Make a MT call to the test phone(receive a call)
 click the home key  
 then unlock screen  
 The incoming call number will diaappear
 
 KO
 
 EXPECTED BEHAVIOUR:
 The incoming call number should diaplay normal
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:mid
 
 REPRODUCING RATE:5/5
 
 For FT PR, Please list reference mobile's behavior:
(Reporter)

Comment 1

5 years ago
Clone from brother
(Reporter)

Comment 2

5 years ago
Created attachment 779070 [details]
log
(Reporter)

Comment 3

5 years ago
Clone from brother
(Reporter)

Comment 4

5 years ago
Created attachment 779071 [details]
PIC

Comment 5

5 years ago
Someone take a look at this bug?

Updated

5 years ago
blocking-b2g: --- → leo?

Comment 6

5 years ago
(In reply to sync-1 from comment #0)
>  click the home key  
>  then unlock screen  

This is a minor issue and there's no indication this is a regression from v1.0.1.
blocking-b2g: leo? → -

Comment 7

5 years ago
 Call is the basic function,and it is bad if the end user can not see the caller immediately?

And it is very easy to touch the home key by careless when you get the mobile out of pocket or bag.

I also met the strange incoming call screen in v1.0.1, but I just don't know how it become this.
Now , we found the step to reproduce it.In my opinion, it is critical, and it should also be easy to fix, just ignore the home key press in this case, as in fact the mobile is still in lock status.  The home key should not work.

Can you reconsider it?

Comment 8

5 years ago
I reproduced it on v1.0.1 version.
Anyway, I think it is a blocking PR. It will really give the end use bad experience if he saw this screen.

I mark it as leo?, please reconsider.
blocking-b2g: - → leo?
(In reply to Amelie Kong from comment #8)
> I reproduced it on v1.0.1 version.

This is the point Alex was making in comment 6, it's too late to block on issues that have been present this whole time unless they are cert blockers, critical security issues, or championed by a partner.
blocking-b2g: leo? → -

Comment 10

5 years ago
Dears,

I investigated this issue.It is caused by the code "https://github.com/mozilla-b2g/gaia/blob/v1.1.0hd/apps/communications/dialer/style/oncall.css#L695".

If remove this CSS code, on lockscreen the incoming call number/contact is displayed on the top.In this case, do not answer the call, then press the home key, the number/contact is displayed normal.

I think if the DOM element "#calls" is on the top, when press home key it is still there, so it is display normal. But if move "#calls" to "top:14rem", there is no DOM element on the top, so when press home key, the number/contact disappeared.

Hope the investigation can help you to solve it.Thanks!
This has been fixed.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.