Closed
Bug 1116059
Opened 9 years ago
Closed 6 years ago
[Call Log] The call log entry will move up after user deletes the associated contact
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)
Firefox OS Graveyard
Gaia::Dialer
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WONTFIX
People
(Reporter: sync-1, Unassigned)
Details
Attachments
(2 files)
FFOS2.0 baseline BuildID: 20140916000205 DEFECT DESCRIPTION: The call logs will move up after user block this caller. REPRODUCING PROCEDURES: Precondition: There is a record in call log which number not be saved in contacts. 1. Enter call log 2. Long press the record to create new contact 3. Then long press the record to delete contact 4. In call log, the record which number isnot saved in contacts will move up EXPECTED BEHAVIOUR: The call logs which number not be saved in contacts should not move up. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: 100%
Comment 3•9 years ago
|
||
Reproduced on 2.0: Build ID 20141229000235 Gaia Revision 01c32dcdc08b3c8fc8b3082870439fa2c1089f4f Gaia Date 2014-12-25 01:47:24 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/b41c344ed82d Gecko Version 32.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) 40 Firmware Date Tue Oct 21 15:59:42 CST 2014 Bootloader L1TC10011880 This might be fixed since 2.1 though. We changed the behavior of the call log there. QA wanted to check 2.1 and master.
status-b2g-v2.0:
--- → affected
Keywords: qawanted
Summary: [Midori 2.0][Call Log] The call logs will move up after user block this caller. → [Call Log] The call log entry will move up after user deletes the associated contact
Comment 4•9 years ago
|
||
This bug was a little wierd to check because of bug 1112242. But performing the steps twice works as a workaround for that issue. The number does not shift up in 2.2 and 2.1 Flame builds. However the Device type ("Unknown" for a contactless number) is lost in this process and will not reappear until the dialer app is closed and reopened. Not sure if that should be it's own issue or is related in some way to either this or bug 1112242. Environmental Variables: Device: Flame 2.1 BuildID: 20150105144122 Gaia: b04a8cb7b2482e0a44e6702b48c42283a00b5b1e Gecko: 99cea2c818f6 Version: 34.0 (2.1) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Environmental Variables: Device: Flame 2.2 BuildID: 20150107051358 Gaia: cd5c88c77debee57c87da79a3995bb34521fb14b Gecko: 206205dd8bd1 Version: 37.0a1 (2.2) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Updated•9 years ago
|
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → affected
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 5•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•