User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.1 (KHTML, like Gecko) Maxthon/126.96.36.1990 Chrome/22.0.1229.79 Safari/537.1 Steps to reproduce: 1. Enter the phone lock password lock interface 2. view and enter build infomation: gecko: revision="3cbade1974968bb1e0fbb0c3386239715244a7a7" gaia: revision="aab72f365d73f624ede32b522f27d072c409e42e" gonk-misc: revision="654358494ba601a46ef9838debc95417ae464cc6" dalvik: revision="ca1f327d5acc198bb4be62fa51db2c039032c9ce" librecovery: revision="e1bd90051c9e937221eb1f91c94e3cde747311a7" moztt: revision="6ee1f8987ef36d688f97064c003ad57849dfadf2" external/jsmin: revision="cec896f0affaa0226c02605ad28d42df1bc0e393" external/opensans: revision="b5b4c226ca1d71e936153cf679dda6d3d60e2354" device/qcom/b2g_common/mozilla-b2g: revision="41c17a6abfd5f488ec99d9aa246f5b07583403c7" Actual results: No cursor in the code lock and can still continue to enter the input box is full, real has not entered within the space, without any prompting; Expected results: Position the cursor, enter the correct password hints may no longer be entered correctly;
Whiteboard: burirun4 → burirun4, OpenCrun1.4-3
should be already resolved, ping qa to double check
This issue is still reproducing Buri 2.1. Observed behavior: There is no active cursor on the passcode lock screen indicating where the input will be put to. But user could still tell where they are by looking at the previous field. Tested on: Device: Buri BuildID: 20140813085958 Gaia: 2864a8d4413746a5359bbcc5042ef776ed06009a Gecko: 6a7be7376caa Version: 34.0a1 (2.1 Master) Firmware v1.2device.cfg User Agent Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
QA Whiteboard: [QAnalyst-Triage?]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
thansk Pi Wei for clarify. ni jenny for UX decision if we should add any visual feedback
Let's do this: when user finish entering the codes and the codes match, hide keyboard. Thank you!
howie could we put it in our backlog? @jenny so we don't have to dim(disable) the `change` button until pin code matched?
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
(In reply to Fred Lin [:gasolin] from comment #5) > howie could we put it in our backlog? > > @jenny so we don't have to dim(disable) the `change` button until pin code > matched? Hi Fred, sorry for the late reply! I think either way is fine, but for consistency, let's dim the button. Thanks!
blocking-b2g: backlog → ---
tracking-b2g: --- → backlog
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Last Resolved: 20 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.