When dial pad opened during 2 other calls in call waiting status, user cannot do call switch at the time until close dial pad. * Build Number The bug is found on v1.1, v1.2(CDMA), unable to verify with v1.3 due to(bug 897100) but probably this is a bug existed along the way. Gaia: 085876be10150c8ca837c0616be215e943d72ec0 Gecko: 773730823bf0c897928aa541ae1dbed7f3d9497b BuildID 20131101101259 Version 26.0 * Reproduce Steps 1. MO 2 calls to DUT, DUT answers them all. 2. Press dial pad on dialer of DUT. 3. Try to do call switching(press each incoming call number on dialer for GSM, press switch button for CDMA) * Expected Result Call still be able to be switched. * Actual Result Unable to switch call until close the dial pad. * Occurrence rate 100%

I'm not sure this is a real bug. There are a lot of actions we can't do when the dial pad is open (mute, enable speaker). Etienne: Carrie: Anyone has opinions on this?

Don't have a strong opinion. Before working on this we should probably make sure we have a spec covering all the edge cases.

Hi everyone, I just reproduced this with Enpei and it looks like bad UX not a bug. I'll check the call waiting spec (CDMA and GSM) and if it is not defined inside, I'll discuss with the related ppl to see if we want to change it or not. Thanks!

I am working in this bug (patch attached). I don't know if there is a strong decision for how it should be. I think this patch is the faster solution, but it can be only a halfway solution, for what I'm reading in comment 3 and comment 1.

Personally, I don't think "switch" should be functionable (not necessary) when the keypad is opened. However, due to the layout design on that page, users can still see these two calls when the keypad is there and it will be really confusing if it's untapable. Hence, I'd vote for changing it. Thanks!

I think this issue will be taken care of when we land bug 977588. The switch button is moving from the calls themselves to a UI that will not be displayed when the keypad is opened. Carrie: Would that remove the confusion?

Hi Anthony, No it's irrelevant. We move the position of the merge and hold button in bug 977588, but we still need users to tap the two calls to switch the active status. Hence, the problem still need to be solved. Thanks!

Ah right, my bad.

Unassigning as Paco isn't working on this as far as I know.

Firefox OS is not being worked on