Closed
Bug 821616
Opened 12 years ago
Closed 12 years ago
[Settings] APN settings: Carrier name and carrier advanced settings value mismatch
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect, P3)
Tracking
(blocking-basecamp:+)
People
(Reporter: steveck, Assigned: timdream)
References
Details
Attachments
(1 file, 1 obsolete file)
1. Go to Cellular & Data, select Data settings/A-GPS settings
2. Check current(provider A) advanced settings value, then select another provider B.
3. Press back button.
4. Enter settings page again, check the provider name and advanced settings value.
Expected result:
Provider name and settings value should be provider A's name and value because we don't submit the changes.
Actual result:
Provider name is pointed to provider B but advanced setting value still belongs to Provider A.
The provider name was saved without clicking the submit button and the provider name still mismatched even restart the settings app or restart the phone. This behavior will make user confused so it should be a blocker.
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P3
Comment 1•12 years ago
|
||
What’s your mcc/mnc? I cannot reproduce with my SIM card because only one provider matches my mcc/mnc info.
Reporter | ||
Comment 2•12 years ago
|
||
If your SIM card only has one mcc info, you can:
1. Create a custom settings and submit
2. Enter the page, select the original provider and back without submit.
3. Enter the page again, you can see the the value in advanced settings is custom settings value but the checked radio input is original provider.
Updated•12 years ago
|
Target Milestone: --- → B2G C3 (12dec-1jan)
Comment 4•12 years ago
|
||
Hi,
Yes, I think it could be a blocker for certification. Issues related to APN settings should be very clear.
I add the dependency.
Thanks,
David
Blocks: b2g-v1-certification
Flags: needinfo?(dpv)
Assignee | ||
Comment 5•12 years ago
|
||
Stealing, Steve talk to me on Monday on details thanks.
Assignee: schung → timdream+bugs
Assignee | ||
Comment 6•12 years ago
|
||
Assignee | ||
Comment 7•12 years ago
|
||
I tried to make sure that Settings.init() doesn't touch controls in the dialogs and all controls in the dialogs comes with data-setting, so that they will be saved during "sumbmit" but not during onchange.
Attachment #695621 -
Attachment is obsolete: true
Attachment #695626 -
Flags: review?(ehung)
Attachment #695626 -
Flags: feedback?(schung)
Comment 8•12 years ago
|
||
Comment on attachment 695626 [details]
Github: https://github.com/mozilla-b2g/gaia/pull/7185
r=me, looks good. Thanks!
Attachment #695626 -
Flags: review?(ehung) → review+
Assignee | ||
Comment 9•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 10•12 years ago
|
||
Comment on attachment 695626 [details]
Github: https://github.com/mozilla-b2g/gaia/pull/7185
It look good and also fixed the same issue in wifi method page, but it might be a little bit confusing for people who is new to the settings app about the timing of saving the different type of input.
Attachment #695626 -
Flags: feedback?(schung) → feedback+
You need to log in
before you can comment on or make changes to this bug.
Description
•