899020 - [Buri][fugu][Call]In dialer interface,input some numbers then cannot move the cursor

Status: RESOLVED DUPLICATE of bug 1092427

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

Description

[sync-1]

AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.164
 Firefox os  v1.1
 Mozilla build ID:20130715070218
 
 DEFECT DESCRIPTION:
 In dialer interface,input some numbers then cannot move the cursor.
 
 REPRODUCING PROCEDURES:
 English
 Steps:
 1. In the IDLE,click dial shortcut key;
 2. In dial interface,input some numbers,then want to move the cursor,you'll find it cannot successful.->KO
 China
 步骤：
 1.进入拨号器;
 2.在输入区域输入一些数字;
 3.点击输入区域,尝试移动光标,不能移动光标->KO
 
 EXPECTED BEHAVIOUR:
 In dialer interface,input some numbers then should can move the cursor.
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 Middle
 
 REPRODUCING RATE:
 5/5
 
 For FT PR, Please list reference mobile's behavior:

Comment 1

[(Inactive after June) George Duan [:gduan] [:喬智]]

Attachment: PR to master

This patch allow user move cursor and delete/add key on cursor's location before dialing and oncall.

Please kindly review.

Comment 2

[Anthony Ricaud (:rik)]

Comment on attachment 783521 [details]
PR to master

This doesn't look like a regression but rather a feature request. I'll remove the review flag while we determine if we want this behaviour or not.

Comment 3

[Anthony Ricaud (:rik)]

Wilfred: Do we want this feature?

IMHO, there's no need to allow for this feature unless we have strong user demand. Phone numbers are so short that I believe it's easier to delete a couple of digits and re-type them. This complexifies the code base (like every new feature), it will maybe make it harder to had copy-paste in the future.

Comment 4

[Joe Cheng [:jcheng] (please needinfo)]

adding to backlog

Comment 5

[Anthony Ricaud (:rik)]

Why are we adding this to the backlog? It already has a patch, the only thing needed here is "do we want this feature?".

Comment 6

[Wilfred Mathanaraj [:WDM]]

if this already has a patch and UX is happy with it I think we can pick it up for v1.2. I will koi? is again so we can cover this in our weekly discussion.

The main question is the usability of this implementation.

Comment 7

[Stephany Wilkes]

Ayman can provide a usability review, but feature inclusion is not up to UX. Since code freeze for 1.2 is in less than a month, I am not sure about a new feature (which neither users nor partners have necessarily requested) being included at this juncture. Might we review this for possible inclusion in 1.3 vs. 1.2?

Comment 8

[ayman maat :maat]

(In reply to Stephany Wilkes from comment #7)
> Ayman can provide a usability review, but feature inclusion is not up to UX.
> Since code freeze for 1.2 is in less than a month, I am not sure about a new
> feature (which neither users nor partners have necessarily requested) being
> included at this juncture. Might we review this for possible inclusion in
> 1.3 vs. 1.2?

This 'bug' is a feature request not a regression as the dialer app was never specified to behave this way and there has never been a demand from users, product or partners to include it.

Nevertheless I have reviewed the patch and think it works fine from a UX perspective.

What i am concerned about though is feature creep and the resultant risk it brings to the product. Though such 'unsolicited' features are welcome, we need to manage their integration tightly as we had 'undulations' both in terms of UX (features being coded that either didn't align or simply contradicted the UX we specified) and dev (bugs, increased code complexity) due to the inclusion of unsolicited and therefore unexpected features from developers during V1.0 in the comms apps. 

I am absolutely not against such features, all i am saying is that we need to be tight and disciplined in how we review and, if appropriate, integrate them in order to manage risk.

from a UX perspective there is no urgency for this patch, I would be happy for it to be part of v1.3

Comment 9

[Joe Cheng [:jcheng] (please needinfo)]

it's a feature request. 
not for v1.2 - back to backlog

Comment 10

[Mingming ZHAO]

Dears,

What about this issue for v1.3?

Comment 12

[Anthony Ricaud (:rik)]

It is too late for 1.3 because it has been feature complete for a while. And 1.4 is almost done.

We need a product decision to know if we want such a feature. Wilfred? I think comment 8 and bug 959041 gives you the information needed to decide.

Comment 13

[Wilfred Mathanaraj [:WDM]]

lets review this as part of v1.5

Comment 14

[(Inactive after June) George Duan [:gduan] [:喬智]]

Deassign myself for now. Please let me know if it need to move on.

Comment 15

[promise09th]

Attachment: Bug_899020.html

Comment 16

[promise09th]

I upload patch and change some codes because we need this patch in v2.0

And, I found below issue
: When user move cursor and delete or select number, cursor disappears.

Do you have any idea for this issue?

Thanks

Comment 17

[(Inactive after June) George Duan [:gduan] [:喬智]]

Sorry, I have no idea on that.