Closed
Bug 1105593
Opened 10 years ago
Closed 10 years ago
[FFOS2.0][Woodduck][Contacts]MS can't enter the next interface and the blue background will still shown after long press contact.
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect, P2)
Firefox OS Graveyard
Gaia::Contacts
Tracking
(b2g-v2.0 affected, b2g-v2.1 unaffected, b2g-v2.2 unaffected)
RESOLVED
DUPLICATE
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
b2g-v2.1 | --- | unaffected |
b2g-v2.2 | --- | unaffected |
People
(Reporter: sync-1, Unassigned)
References
Details
Attachments
(4 files)
DEFECT DESCRIPTION:
MS can't enter the next interface and the blue background will still shown.
>The issue exists on all interface.
REPRODUCING PROCEDURES:
1.Enter Contacts
2.Long press a contact then move your finger to right or left for a while,then remove your finger from the screen,you will see the interface is unchanged.
EXPECTED BEHAVIOUR:
MS should enter the next interface.
Comment 1•10 years ago
|
||
Hi Norry,
qawanted for Woodduck 2.0M and Flame 2.0/2.1/2.2. Thanks!
Comment 2•10 years ago
|
||
Hi Reporter,
Could you confirm the actual result according to my updated verify video?
On Flame 2.0 and woodduck 2.0M, long tapping contact will invoke the highlighted background. After finger leaves the screen, the blue background will not disappear.
On Flame 2.1 and Flame 2.2, after finger leaves the screen, the blue background will disappear, but MS will leave in the current page, will not enter next page.
Could you also help to confirm the expected result?
Thank you.
Flags: needinfo?(sync-1)
Comment 3•10 years ago
|
||
(In reply to comment #2)
> Comment from Mozilla:Hi Reporter,
>
> Could you confirm the actual result according to my updated verify video?
> On Flame 2.0 and woodduck 2.0M, long tapping contact will invoke the
> highlighted background. After finger leaves the screen, the blue background
> will not disappear.
>
> On Flame 2.1 and Flame 2.2, after finger leaves the screen, the blue background
> will disappear, but MS will leave in the current page, will not enter next
> page.
>
> Could you also help to confirm the expected result?
>
> Thank you.
>
Hi ,
I don't know why I can't watch your updated verify video,but according to your description,what you said is same as mine.
The situation of the bug below :
When we select and press one of the contacts,then move your finger to right or left around , you will see that the blue background will not disappear and the MS still stays in the current page.(see the video for detail)
The expected result we want is that the blue background will disappear and the MS can enter the next page .
Thanks you.
Comment 8•10 years ago
|
||
Hi Peipei,
According to comment 4, this bug can be reproed on Woodduck 2.0 and Flame 2.0/2.1/2.2
On Woodduck2.0&Flame 2.0, after remove finger from screen, the blue background will not disappear and it will not enter the next page;
On Flame 2.1/2.2, after remove finger from screen, the blue background will disappear, but it will not enter the next page. (Please see video: Verify-2.1&2.2.mp4)
Both The behavior are different from what reporter said on comment 4.
I think the behavior on Flame 2.1/2.2 is reasonable, could you help with this bug?
Thank you.
Flags: needinfo?(fan.luo)
Updated•10 years ago
|
QA Contact: ckreinbring
Comment 9•10 years ago
|
||
The bug repros on Flame 2.0 engineering with shallow flash.
Actual result: After long tapping a contact and swiping horizontally, the highlight on the contact will remain when the user removes their finger.
BuildID: 20141202035701
Gaia: 8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko: 29222e215db8
Platform Version: 32.0
Firmware Version: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
--------------------------------------------------------------------------------------------------------
The bug does not repro on Flame 2.2 or 2.1 engineering with shallow flash.
Actual result: After long tapping a contact and swiping horizontally, the highlight on the contact will disappear when the user removes their finger.
Flame 2.2
BuildID: 20141201032744
Gaia: 39214fb22c203e8849aaa1c27b773eeb73212921
Gecko: 08be3008650f
Platform Version: 37.0a1
Firmware Version: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Flame 2.1
BuildID: 20141202061559
Gaia: a684b82a19dd1939ca6e75e60a6203327b333c2a
Gecko: a7f6a3cc59bc
Platform Version: 34.0
Firmware Version: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → unaffected
status-b2g-v2.2:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ckreinbring
Comment 10•10 years ago
|
||
Gary, could you please take a look? Theproblem complained in this bug is: Long Tap and then release on a contact entry will only highlight the contact without steping to next page. Do you think this is expected?
Flags: needinfo?(gchen)
Updated•10 years ago
|
Blocks: Woodduck_P2
Comment 11•10 years ago
|
||
Same issue with bug 1104618. Fix in 2.1
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(sync-1)
Flags: needinfo?(gchen)
Resolution: --- → DUPLICATE
Reporter | ||
Comment 12•10 years ago
|
||
(In reply to comment #12)
> Comment from Mozilla:Same issue with bug 1104618. Fix in 2.1
>
HI,
I have not authorized to access bug #1104618, pls help me obtain permission.My Bugzilla@Mozilla account is "zhenhua.zhang@t2mobile.com",thank you.
Reporter | ||
Comment 13•10 years ago
|
||
Mozilla在2.1上fixed,拿回2.0用risk太高,建议keep
Reporter | ||
Comment 14•10 years ago
|
||
dear vpm,
this pr is same with PR 852634
Reporter | ||
Comment 15•10 years ago
|
||
Hi feiyan,
此PR同852634(Mozilla在2.1上fixed,拿回2.0用risk太高,建议keep),麻烦您一并帮我改一下状态哦,谢谢啦!
Reporter | ||
Comment 16•10 years ago
|
||
Dear Zhenhua,
这个不是内部PR,VPM处理不了,请联系SPM。
Reporter | ||
Comment 17•10 years ago
|
||
Hi DengWei,
此PR同852634,Mozilla回复--在2.1上fixed,拿回2.0用risk太高,建议keep。麻烦您帮我改一下状态哦,谢谢啦!
You need to log in
before you can comment on or make changes to this bug.
Description
•