Closed Bug 979833 Opened 10 years ago Closed 10 years ago

inconsistent presentation of message that number is not in FDN list.

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED FIXED
1.4 S4 (28mar)
tracking-b2g backlog

People

(Reporter: maat, Assigned: rik)

References

Details

(Keywords: late-l10n)

Attachments

(3 files)

The dialogues for informing the user that FDN is active are very different both in information delivery, language and visual treatment between the Dialler app (refer to attachment ’01 Dialler’) and the Messages app (refer to ‘attachment 02 [details] [diff] [review] msg app 1 number’).  For consistency and continuity of UX across the platform we should ensure that the dialogue in the dialler app has the same visual treatment, language and information as that in the message app. 

Therefore the dialogue in the dialler app should read as follows:

      FDN Active
      FDN is activated and the following number is not in your FDN list:
      <phone number>
Attached image 01 Dialler.png
Attached image 02 msg app 1 number.png
blocking-b2g: --- → 1.4?
Blocking for string consistency, fix should be a more generic message like dependent bug 978130
blocking-b2g: 1.4? → 1.4+
Depends on: 978130
Anthony this is in your area ;)
Assignee: nobody → anthony
set target milestone to 1.4 S4 for now
Target Milestone: --- → 1.4 S4 (28mar)
Keywords: late-l10n
Given that we're way past strong string freeze, I'm moving this back into the triage bucket. This might have been a good idea a month ago, but do we really really need this now? David?
blocking-b2g: 1.4+ → 1.4?
Flags: needinfo?(dscravaglieri)
Moving to backlog.
blocking-b2g: 1.4? → backlog
Bug 978130 - [FDN] Misleading message when trying to send an SMS in FDN mode, is 1.4+ and it's almost ready to land...so we should maintain the string consistency in both applications and fix this bug for 1.4 version.
clear n?
Flags: needinfo?(dscravaglieri)
Per comment 8 re-nominating this bug accordingly
blocking-b2g: backlog → 1.4?
I've moved bug 978130 into the triage queue, too. "close" isn't a good measure right now. What we need is "really really blocking"
I'm working on this and I don't like the string used. Do we expect users to understand "FDN"? We use Fixed dialing numbers in settings.
Flags: needinfo?(ofeng)
Flags: needinfo?(cawang)
Summary: [Dialler] inconsistent presentation of message that number is not in FDN list. → inconsistent presentation of message that number is not in FDN list.
We might change the string message but that's not a blocker to review.
Attachment #8404037 - Flags: review?(etienne)
backlog since this breaks string freeze
blocking-b2g: 1.4? → backlog
Agree with Anthony. Users won't get the meaning of "FDN".
My suggestion:

FDN Active
FDN (Fixed Dialing Numbers) is activated and the following number is not in your FDN list:
<phone number>

I've discussed with Omega and we suggest using this string in both Message and Dialer APP. Thanks!
Flags: needinfo?(ofeng)
Flags: needinfo?(cawang)
Committed with new message: https://github.com/mozilla-b2g/gaia/commit/2cee2e60b4b1659f6a7bfc8a8bcadcc2e6d37e23
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Of course I forgot to commit the message update…

So new commit: https://github.com/mozilla-b2g/gaia/commit/07b30ab53994a9da86d40eee5fb74154bf8c5c10
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: