Closed
Bug 1173596
Opened 9 years ago
Closed 9 years ago
[B2GDroid] Unable to set dates for Contacts
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(b2g-master unaffected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
b2g-master | --- | unaffected |
People
(Reporter: jthomas, Unassigned)
References
()
Details
(Whiteboard: [3.0-Daily-Testing])
Attachments
(1 file)
598.14 KB,
text/plain
|
Details |
Description: If the user attempts to set a date for Contact such Birthday or Anniversary they will be unable to set the date for the occasion. Repro Steps: 1) Update to B2GDroid 20150608071805 20150604202816 2) Select Contacts 3) Create a new contact. 4) Scroll down to Birthday. 5) Select Date 6) Attempt to enter and edit date. Actual: Keyboard pops up, but entering numbers and pressing enter on the Droid keyboard has no results. Expected: It is expected that the dates for contacts will be editable so that the occasion can be set to a precise date. Repro frequency: 100%. See attached: Logcat & Video
Reporter | ||
Comment 1•9 years ago
|
||
This issues does NOT occur on the Flame 3.0. Result: Dates are editable. Environmental Variables: Device: Flame 3.0 Kitkat Full Flash (319mb) BuildID: 20150609160220 Gaia: 31ef8deec7a04a988eb92309178b87cc0bde8220 Gecko: 8be8deb10e4f Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Blocks: b2gdroid
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → unaffected
Flags: needinfo?(ktucker)
Whiteboard: [3.0-Daily-Testing]
Reporter | ||
Comment 2•9 years ago
|
||
The build used was 20150608071805.
Reporter | ||
Comment 3•9 years ago
|
||
Correction: The build used was 20150608071805.
Comment 4•9 years ago
|
||
This might be related to bug 1172698. The keyboard pops up here when the date dropdown is tapped though in contacts.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 5•9 years ago
|
||
Can we reproduce this issue?
You need to log in
before you can comment on or make changes to this bug.
Description
•