Closed
Bug 831013
Opened 12 years ago
Closed 12 years ago
STK GET_INPUT and GET_INKEY shows min and max length in display text
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.0 fixed)
RESOLVED
FIXED
| blocking-b2g | tef+ |
People
(Reporter: cyang, Assigned: frsela)
Details
(Whiteboard: [EU_TPE_TRIAGED], QARegressExclude)
Attachments
(1 file)
For GET_INPUT and GET_INKEY proactive commands, the text is displayed followed by the min and max length in brackets. For example:
- TC 27.22.4.2.1.3 displays: <GO-BACKWARDS> [1-1]
- TC 27.22.4.3.3.1 displays: ЗДРАВСТВУЙТЕ [5-5]
Daniel, thoughts on the display containing the min and max length? Can GCF tests like these be passed/waived?
Flags: needinfo?(dcoloma)
Comment 1•12 years ago
|
||
Carol, what is current problem? Are not we showing the [1-1] or [5-5] bits or is the problem related with the size of the input text field?
Flags: needinfo?(dcoloma) → needinfo?(cyang)
| Reporter | ||
Comment 2•12 years ago
|
||
Daniel, the GCF test asks if a certain display is shown, without the values in brackets. For example TC 27.22.4.2.1.3, step 4 in the TS 51.010 says:
Display "<GO-BACKWARDS>"
However, given that the current display is "<GO-BACKWARDS> [1-1]", can this test be considered passing?
Flags: needinfo?(cyang)
Comment 3•12 years ago
|
||
So, the point is that we are showing "<GO-BACKWARDS> [1-1]" but we should show "<GO-BACKWARDS>", right?
Flags: needinfo?(cyang)
| Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Daniel Coloma:dcoloma from comment #3)
> So, the point is that we are showing "<GO-BACKWARDS> [1-1]" but we should
> show "<GO-BACKWARDS>", right?
Yes, correct
Flags: needinfo?(cyang)
Updated•12 years ago
|
Assignee: nobody → pwang
Comment 5•12 years ago
|
||
Looks like a UI issue. Gaia people may able to get this fixed much sooner than I can. :)
Assignee: pwang → nobody
Updated•12 years ago
|
blocking-b2g: tef? → tef+
Comment 6•12 years ago
|
||
:frsela, it seems like STK gaia falls in your plate for most times, can you take a look? or re-assign if needed? thanks
Assignee: nobody → frsela
Updated•12 years ago
|
Whiteboard: [EU_TPE_TRIAGED]
| Assignee | ||
Comment 7•12 years ago
|
||
Attachment #702762 -
Flags: review?(21)
Comment 8•12 years ago
|
||
Comment on attachment 702762 [details]
Removed the min-max lenght help string
https://github.com/mozilla-b2g/gaia/commit/686b872f81dbeaa12f8515a784caa49b5f857e4c
Attachment #702762 -
Flags: review?(21) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
status-b2g18:
--- → fixed
Comment 9•12 years ago
|
||
Landed on mozilla-b2g18/gaia master prior to the 1/25 branching to mozilla-b2g18_v1_0_0/v1.0.0, updating status-b2g-v1.0.0 to fixed.
status-b2g18-v1.0.0:
--- → fixed
Updated•12 years ago
|
Whiteboard: [EU_TPE_TRIAGED] → [EU_TPE_TRIAGED], QARegressExclude
Comment 10•12 years ago
|
||
No Test case creation is needed in moztrap for this issue.
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•