Created attachment 8604342 [details] logcat-dialer-asterisk.txt Description: If there is already content in the dial field, long pressing the Asterisk key will type an asterisk, that will then switch to a comma (,). If the field is already blank, the asterisk will be typed, and then deleted. Repro Steps: 1) Update a Flame to 20150511010202 2) Open the Dialer app 3) Press and hold the Asterisk (*) key. Actual: The asterisk will be typed, then deleted in the dial field. Expected: The asterisk is typed, then changes to a comma (,) Environmental Variables: Device: Flame 3.0 (319MB)(Full Flash) Build ID: 20150511010202 Gaia: 6089234ace8b294a8feef064387604bae16254e3 Gecko: d8420a541d1c Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: 10/10 See attached: Video (URL), Logcat.
This issue DOES occur on Flame 2.2 builds. The asterisk will be typed, then deleted in the dial field. Environmental Variables: Device: Flame 2.2 Build ID: 20150511002500 Gaia: 528ef60e7cda09ad43478065f5d33bda398fbeb7 Gecko: 8d04cc085cf5 Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
I don't think the comma should be displayed here, as it represent a pause in the dialing sequence and a pause at the beginning is not allowed. I think the asterisk should remain displayed in that case. What do you think, Carrie?  http://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-d00.zip Chapter 8.7.
If the field is blank, long-tapping the asterisk key will only display the asterisk symbol, not a comma. So we still need to fix the current behavior (the asterisk will just disappear). Thanks!
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Based on comms triage.
Priority: -- → P2
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.