Closed
Bug 870646
Opened 12 years ago
Closed 8 years ago
[Buri][IOT][PUK layout] Setting PIN after insert PUK, fields are covered by keyboard.
Categories
(Firefox OS Graveyard :: General, defect, P2)
Tracking
(tracking-b2g:backlog, b2g18+)
People
(Reporter: sync-1, Unassigned)
References
Details
(Whiteboard: Chile, IOT, buri)
Attachments
(4 files)
+++ This bug was initially created as a clone of Bug #451756 +++
AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.094
Firefox os v1.0.1
Mozilla build ID:20130502070201
Created an attachment (id=406450)
VideoLogsPart01
DEFECT DESCRIPTION:
When you fail inserting up to 5 times the PIN code in the DUT, and the PUK is requested, PIN fields are covered for the keyboard. Please refer to attach video.
REPRODUCING PROCEDURES:
1. Set a PIN code to SIM.
2. Turn on DUT.
3. Fail 5 times PIN code.
4. When the PUK code is requested, notice how the other 2 fields of PIN (new, confirm) are covered for the keyboard. KO
Refer to attach video.
EXPECTED BEHAVIOUR:
When the keyboard appears, the screen should scroll to the top and allow the other 2 fields to be visibles.
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:
For FT PR, Please list reference mobile's behavior:
++++++++++ end of initial bug #451756 description ++++++++++
CONTACT INFO (Name,Phone number):
DEFECT DESCRIPTION:
REPRODUCING PROCEDURES:
EXPECTED BEHAVIOUR:
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:
For FT PR, Please list reference mobile's behavior:
![]() |
||
Updated•12 years ago
|
blocking-b2g: --- → tef?
![]() |
||
Updated•12 years ago
|
Whiteboard: Chile, IOT, buri
![]() |
||
Comment 9•12 years ago
|
||
thanks David. per comment 8. tef-, set tracking-b2g18+
blocking-b2g: tef? → -
tracking-b2g18:
--- → +
Comment 10•12 years ago
|
||
Recheck on version:
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.171
Firefox os v1.1
Mozilla build ID:20130722070207
stilll not OK.
Mark leo?
Updated•12 years ago
|
blocking-b2g: - → leo?
Comment 11•12 years ago
|
||
Amelie given this is not a regression and a known issue in 1.0.1 and based on where we are in the 1.1 cycle this is not a blocker.Passing this onto koi? to address in future release.
blocking-b2g: leo? → koi?
Comment 12•12 years ago
|
||
Keyboard API & focus issue. Not addressable during v1.2 cycle. Pass to 1.3? to address in future release.
blocking-b2g: koi? → 1.3?
Component: Gaia::Settings → General
![]() |
||
Comment 13•12 years ago
|
||
(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) from comment #12)
> Keyboard API & focus issue. Not addressable during v1.2 cycle. Pass to 1.3?
> to address in future release.
Dear Mozilla,
Which version is the end? I think this is a terrible user experience problem and we should fix it ASAP.
Flags: needinfo?(timdream)
Updated•12 years ago
|
Flags: needinfo?(timdream) → needinfo?(jcheng)
![]() |
||
Comment 15•12 years ago
|
||
Dears,
If I long press input-box, the screen has scroll to the top and display OK. please help check why?
Flags: needinfo?(timdream)
Updated•12 years ago
|
Flags: needinfo?(timdream) → needinfo?(jcheng)
![]() |
||
Comment 16•12 years ago
|
||
hi Ivan, does it fall under your team's scope to discuss whether this is to be fixed in any particular release? Thanks
Flags: needinfo?(jcheng) → needinfo?(itsay)
Comment 17•12 years ago
|
||
Sorry, I was a little bit confused.
Rudy, this is yet another forms.js work I believe. Would you be able to do it? Do you need external help?
Flags: needinfo?(itsay) → needinfo?(rlu)
Comment 18•12 years ago
|
||
Right now, I am more focused on 3rd party keyboard related follow-up to get it into v1.3, so may not be able to look into this issue recently.
Would be great if someone can pick this up.
Thanks.
Flags: needinfo?(rlu)
![]() |
||
Comment 19•12 years ago
|
||
Tim
Per recent discussion 3rd party keyboard was moving to 1.4.
Do you concur that this bug will also need to move to 1.4?
Moved to keyboard.
Component: General → Gaia::Keyboard
Flags: needinfo?(timdream)
Comment 21•12 years ago
|
||
Please disregard previous comment.
(In reply to Preeti Raghunath(:Preeti) from comment #19)
> Tim
>
> Per recent discussion 3rd party keyboard was moving to 1.4.
>
This bug has nothing to do with 3rd-party keyboard. Please read the bug comments carefully.
> Do you concur that this bug will also need to move to 1.4?
For this bug along, if I am present in the triage, I will minus it. I personally think this is a easily recoverable usability issue, not a serious bug.
> Moved to keyboard.
This is a input method API focusing/scrolling issue, not a keyboard component bug (the component is only about built-in keyboard app).
![]() |
||
Comment 22•12 years ago
|
||
minus per Tim's comment 21.
blocking-b2g: 1.3? → ---
Flags: needinfo?(praghunath)
Updated•11 years ago
|
blocking-b2g: --- → backlog
Assignee | ||
Updated•11 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Comment 23•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•