Closed
Bug 1097772
Opened 10 years ago
Closed 6 years ago
[System][Call Screen] Callscreen notification does not go away if tapped once the call is hung up
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gtorodelvalle, Unassigned)
Details
I found this issue using the following build: flame-KK.eng.master.184based.B-63.Gecko-f8ad1d8.Gaia-757eef6. STR: 1. Establish a call to or from the DuT. 2. Minimise the call screen tapping on the "Home" button. Wait until the call screen completely disappears from the screen. 3. Hang up the call from the other side. 4. Expand the notification overlay and tap on the entry for the call screen which may be still there. There are "strict" timing requirements to reproduce the issue related to this step. EXPECTED: 5. In case the call screen is expanded, once the call is completely hung up: 1) the call screen should be closed and 2) the entry for the call screen in the notification overlay should also go away. OBSERVED: 5. The call screen is shown with no call information on it. 6. Tap on the "Home" button. The call screen minimises showing a white area at the top of the screen. 7. Expand the notification overlay. The call screen entry is still there and 5-6-7 can be repeated over and over again until a new call is established and "properly" dealt with (this is not going from 2 to 4 :) ). I'll try to record a video about the issue and upload it.
Reporter | ||
Comment 1•10 years ago
|
||
BTW, for the time being I'll keep the component as Gaia::Dialer until the issue is further investigated.
Comment 2•10 years ago
|
||
I can't reproduce on v188 + shallow flash gecko and gaia. Gaia-Rev 5ae28ff11b982e2bd7d1aa097cda131536952bdc Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/688f821edcd4 Build-ID 20141112040208 Version 36.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental 39 FW-Date Thu Oct 16 18:19:14 CST 2014 Bootloader L1TC00011880 Can you shoot a video, Germán?
Comment 3•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•