1077567 - Callscreen + software home button is really messed up

Status: RESOLVED DUPLICATE of bug 1068470

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

Description

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Attachment: Screenshot

The callscreen interacts very badly with the software home button.  In particular, try receiving a call while already on a call.

Tako has a software home button, so nomming for 2.1.

Comment 1

[Kevin Grandon :kgrandon]

Let's use bug 1068470 to track the software home button work. In this screenshot I see several asset issues, but this could be because we're missing assets for the higher resolution nexus5. Not sure if you want to keep this open to track the callscreen asset work, or mark it as a duplicate of bug 1068470.

Comment 2

[Gregor Wagner [:gwagner]]

Broken feature.

Kyle, have you tested on 2.1?

Comment 3

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

No, I haven't tested on 2.1.

Comment 4

[Gregor Wagner [:gwagner]]

Can QA check if this is happening on 2.1?

Comment 5

[Cody Roesch [:croesch]]

Kyle, It looks like you were testing with a Tako device correct? I've checked this on Flame device with the branches below and did not see any problems.

I enabled software home button and tested on the homescreen and on the lockscreen with no luck repro'ing. If you find that this happens for you on the Flame and can provide any additional information then QA will take another look at this. 

This bug does NOT repro on Flame kk build: Flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK

Actual Result: Incoming call when already on a call with Software Home button enabled, does not cause any issues.

Repro Rate: 0/4

Environmental Variables:
Device: Flame Master KK
BuildID: 20141006064312
Gaia: 470826d13ae130a5c3d572d1029e595105485fb0
Gecko: e0d9ad4be606
Version: 35.0a1 (Master) 
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141006062615
Gaia: 778ebac47554e1c4b7e9a952d73e850f58123914
Gecko: bc87917b3b95
Version: 34.0a2
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141006044157
Gaia: 26670a3193b57ead978ef2faefc2a679ea57f8d4
Gecko: c06b369ccda7
Version: 32.0 (2.0) 
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 6

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

This is on a Nexus 5.  I don't have a Tako.

I guess if it doesn't happen on the flame that gives more credence to kgrandon's theory that this is an issue with not having assets at the right resolution.

Comment 7

[Kevin Grandon :kgrandon]

There are two bugs here, one is for high DPI assets which we don't ship currently (though should do a better job at falling back to not break high-res devices).

The other bug is definitely a SHB bug, which is reproducible only on devices without a physical home button, using the -moz-physical-home-button pseudo selector. It's highly likely that this bug currently does not reproduce on a flame. I'm trying to fix this by removing usage of the -moz-physical-home-button selector so we can verify these bugs on a flame.