Anshul Reporter
	Description • 10 years ago

STR
1. Insert a GSM SIM card
2. Go to Settings->Call Settings->Fixed dialing numbers
3. Enable FDN
4. Enter PIN2
5. Go back to Call Settings screen

Expected:
Fixed dialing numbers should say its disabled and other voice call settings should stay untouched.

Observed: The setting UI seems to be messed up. Please see the attachment.

	bhavana bajaj [:bajaj]
	Comment 1 • 10 years ago

I am adding qawanted here to test on branches and confirm  if its a regression.

	Jayme Mercado [:JMercado] (Inactive 3/4/2016)
	Comment 2 • 10 years ago

This issue does occur in 2.0 Flame, 2.1 Flame, Flame 1.4, and Buri 2.1.

Environmental Variables:
Device: Flame Master
BuildID: 20140718120125
Gaia: Unknown
Gecko: ecdb409898a6
Version: 33.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Environmental Variables:
Device: Flame 2.0
BuildID: 20140718135645
Gaia: 2f4b11611c9b37ccf33a76dbbe85cac912594253
Gecko: 12e11c8ecc0f
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Flame 1.4
BuildID: 20140718081451
Gaia: 621d152f89347c79619aa909ad62cc2ac9d3ab5b
Gecko: 989db90b4457
Version: 30.0 (1.4) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Environmental Variables:
Device: Buri Master
BuildID: 20140718061630
Gaia: Unknown
Gecko: 330ba968ed61
Version: 33.0a1 (Master) 
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Many options from the call settings screen are unavaialble when FDN is turned on.

	bhavana bajaj [:bajaj]
	Comment 3 • 10 years ago

Can you please help test this on 1.3 as well? Thanks

	Joshua Mitchell (Inactive)
	Comment 4 • 10 years ago

QA-Wanted to test 1.3 Flame

	Jayme Mercado [:JMercado] (Inactive 3/4/2016)
	Comment 5 • 10 years ago

This issue does occur on the 1.3 Flame Base V122 and Buri 1.3.

Environmental Variables:
Device: Buri 1.3
BuildID: 20140718005150
Gaia: 23f55be856cef53c6604a6fe4aeb09061afbc897
Gecko: 9d5426c98678
Version: 28.0 (1.3) 
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

Many options from the call settings screen are unavaialble when FDN is turned on.

	Preeti Raghunath(:Preeti)
	Comment 6 • 10 years ago

Blocking for CAF priority and regression issue.

	Sergi Mansilla [:sergi] (Telenor) [PTO]
	Comment 7 • 10 years ago

> Fixed dialing numbers should say its disabled and other voice call settings should stay untouched.

You mean that FDN should say it's enabled, right? Otherwise, why would it say it's disabled if we just enabled it?

> Observed: The setting UI seems to be messed up. Please see the attachment.

By "messed up" do you mean that the "Call waiting" item menu is empty and with an alert sign? Is there anything else that you consider it's messed up? Also, what call settings options are you expecting to be enabled when FDN is enabled?

Thanks.

	Anshul Reporter
	Comment 8 • 10 years ago

(In reply to Sergi Mansilla (Telenor) from comment #7)
> > Fixed dialing numbers should say its disabled and other voice call settings should stay untouched.
> 
> You mean that FDN should say it's enabled, right? Otherwise, why would it
> say it's disabled if we just enabled it?
Sorry, yes I meant enabled and not disabled.
> 
> > Observed: The setting UI seems to be messed up. Please see the attachment.
> 
> By "messed up" do you mean that the "Call waiting" item menu is empty and
> with an alert sign?
Yes
 Is there anything else that you consider it's messed up?
Call forwarding setting shows error "FDN blocked".
> Also, what call settings options are you expecting to be enabled when FDN is
> enabled?
> 
> Thanks.

	Sergi Mansilla [:sergi] (Telenor) [PTO]
	Comment 9 • 10 years ago

After thoroughly checking the code I am starting to think that this behavior is by design. The empty 'Call Waiting' row is empty on purpose and the alert icon indicates that something is wrong. when tapped, it offers to try to start the 'Call waiting' to the user.

The lack of options is probably because FDN limits that (and it kind of makes sense). I'd like to get somebody to look at this issue that is either from UX or that knows what activating FDN implies, or both. I think that even if this is default behavior it should be better signaled to the user.

Francisco, who could confirm that this is default behavior?

	Francisco Jordano [:arcturus] [:francisco]
	Comment 10 • 10 years ago

Unfortunately I'm not really into FDN feature, I think Michal did it with Kaze.

Michal, are you able to answer Sergin in comment above, or do you point him to the product owner for this feature?

	Anshul Reporter
	Comment 11 • 10 years ago

(In reply to Sergi Mansilla (Telenor) from comment #9)
> After thoroughly checking the code I am starting to think that this behavior
> is by design. The empty 'Call Waiting' row is empty on purpose and the alert
> icon indicates that something is wrong. when tapped, it offers to try to
> start the 'Call waiting' to the user.
> 
> The lack of options is probably because FDN limits that (and it kind of
> makes sense). I'd like to get somebody to look at this issue that is either
> from UX or that knows what activating FDN implies, or both. I think that
> even if this is default behavior it should be better signaled to the user.
> 
> Francisco, who could confirm that this is default behavior?
Sergi, on further investigation I see that the behavior of call forwarding is as expected. So the only issue is the empty Call Waiting row as you said.

	Sergi Mansilla [:sergi] (Telenor) [PTO]
	Comment 12 • 10 years ago

Hi Anshul,

What are you expecting to see in that row? Michal?

	Michał Budzyński (:michalbe)
	Comment 13 • 10 years ago

Sorry for the delay, I have no idea what's going on in this part of the app, it's probably Kaze's.

	Lawrence Mandel [:lmandel] (use needinfo)
	Comment 14 • 10 years ago

(In reply to Michał Budzyński (:michalbe) from comment #13)
> Sorry for the delay, I have no idea what's going on in this part of the app,
> it's probably Kaze's.

ni on Kaze - but he looks to be on PTO. 

Michal - Is there anyone else who you think can help answer Sergi's question in comment 12?

	Inder
	Comment 15 • 10 years ago

After discussing with Anshul removing it from our blocker list. Anshul pointed out that the main issue here is the lack of clarity on the error message.

	Michał Budzyński (:michalbe)
	Comment 16 • 10 years ago

Lawrence, Kaze is not working at Mozilla anymore. I don't know who is in charge of this feature now.

	Lawrence Mandel [:lmandel] (use needinfo)
	Comment 17 • 10 years ago

Given that CAF has dropped this from their blocker list (comment 15), setting back to 2.0? so that we can reevaluate the need for this fix in 2.0 during triage.

	Lawrence Mandel [:lmandel] (use needinfo)
	Comment 18 • 10 years ago

Review in triage confirms that this no longer needs to block 2.0.

	BMO Automation
	Comment 19 • 7 years ago

Firefox OS is not being worked on