Closed Bug 1028789 Opened 10 years ago Closed 10 years ago

[Sora]There is no character counter inside STK submenus

Categories

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

defect

Tracking

(blocking-b2g:2.0+, b2g-v2.0 fixed, b2g-v2.1 fixed)

VERIFIED FIXED
2.0 S6 (18july)
blocking-b2g 2.0+
Tracking Status
b2g-v2.0 --- fixed
b2g-v2.1 --- fixed

People

(Reporter: sync-1, Assigned: frsela)

Details

(Keywords: cert-waiver)

Attachments

(2 files)

DEFECT DESCRIPTION:
 When accessing some STK menu that offers a field to enter some characters, none character counter is presented in order to let user know about how much characters can be used or to help user to know how many characters still left to enter.
 
  REPRODUCING PROCEDURES:
 1. Access phone settings then select STK menu (VIVO chip - at the end of list);
 2. Notice a lot of sub menus are presented;
 3. Select any submenu (e.g.: Mensagens);
 4. Notice a field to enter some text is presented;
 5. Starting inserting some text;
 6. Notice there is no character counter in order to let user know about how many characters has been inserted and how many characters user still can insert.
 
 *This feature (character counter) is important because in some submenus user is able to insert a limited qty of charatcers and a counter is needed in order to let user know about how many characters still can use.
 **There is another situation, when inserting some DATE, STK menu allow the format DDMMYY in some submenus and DDMMYYYY in other submenus, user needs to know if the submenu is about to allow DDMMYY or DDMMYYYY, in this case, only a character counter can help user.
 
  EXPECTED BEHAVIOUR:
 Phone must show a character counter everytime that phone presents a STK screen that user should insert some characters
 
  ASSOCIATE SPECIFICATION:
 None
 
  TEST PLAN REFERENCE:
 Pre homo vivo
 
  TOOLS AND PLATFORMS USED:
 STK menu
 
  USER IMPACT:
 Will see
 
  REPRODUCING RATE:
 100%
 
  For FT PR, Please list reference mobile's behavior:
Dear Fernando,
Block VIVO again...Can you provide a proposed patch for this? Thanks a lot!
blocking-b2g: --- → 1.3?
Flags: needinfo?(frsela)
Dear Fernando,
Any update about this? Vivo is pushing us.
Flags: needinfo?(frsela)
Flags: needinfo?(brg)
This is a new feature request out of 1.1. and very late for 1.3. IMHO we should introduce it in 2.0 and try a certification waiver for it. Do you think it is possible?
Flags: needinfo?(brg) → needinfo?(chenxk)
Cert-waiver from 1.1 so please check if its possible to fix in 2.0
blocking-b2g: 1.3? → 2.0?
Keywords: cert-waiver
blocking-b2g: 2.0? → 2.0+
Setting ni to Rafa as we need UX feedback about how implement this feature
Flags: needinfo?(hello)
We're very constrained in terms of space in these sort of screens. I don't think it's always necessary two explicitly show a character counter, but let me know if that's a certification request. Otherwise, other means might cover most use cases.

I see the following as possible enhancements:

* Use the text field placeholder to display input requirements, e.g.: "DDMMYYYY", "6 characters", etc.
* Bouncing animation left/right on the textfield when the user tries to enter more chars than allowed (the [send] button is disabled when not enough chars have been entered)
* Use the [ok]/[send] button to convey some info by changing its state from disabled to, for example, red.
* In addition to changing states, the [send] button could hold the counter.
* Reduce the text field's width and display a counter on its side (I'd really like to avoid this one)


Hope those help!
Flags: needinfo?(hello)
Yes, this is a must for certification, lets include it asap.
Assignee: nobody → frsela
Attached file Proposed patch
Proposed patch.

As Rafa suggested me, now the keyboard is not hidden when the input box is plenty.

Also an animation and mobile vibration is applied as a feedback when no more characters allowed.

The Ok buttons shows the pending number of characteres.
Attachment #8447945 - Flags: review?(21)
Target Milestone: --- → 2.0 S6 (18july)
Comment on attachment 8447945 [details] [review]
Proposed patch

r+ with nits.
Attachment #8447945 - Flags: review?(21) → review+
https://github.com/mozilla-b2g/gaia/commit/f00fdf04461d7f30a6c1be95be11bb656da7fa6f
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Needs rebasing for v2.0 uplift.
Flags: needinfo?(frsela)
rebasing for v2.0 uplift:
https://github.com/mozilla-b2g/gaia/pull/21616 

waiting for travis merge
Flags: needinfo?(frsela)
Tested and working (see attached image)
Hamachi
2.1
Gecko-329b2e4
Gaia-d688d4f

2.0
Gecko-d7d9838
Gaia-1144cdc
Status: RESOLVED → VERIFIED
Flags: needinfo?(chenxk)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: