Closed
Bug 1368970
Opened 7 years ago
Closed 6 years ago
[LeanPlum] - Tapping on device back button doesn't dismiss the prompt
Categories
(Firefox for Android Graveyard :: General, defect, P1)
Tracking
(firefox55 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: sflorean, Assigned: vlad.baicu)
References
Details
(Whiteboard: [Leanplum] [61])
Environment: Device: Huawei Honor (Android 5.1.1); Build: Nightly 55.0a1 (2017-05-30); Prerequisite: Enable LeanPlum from Switchboard Experiments. Steps to reproduce: 1. Launch Fennec and go to a page; 2. Fennec is launched succesfully. A message: "This page could be a reader mode page" is displayed. With options: No, Newsletter! 3. Tap on device back button. Expected result: The prompt is dismiss. Actual result: Nothing. The button is not responding. Notes: -The prompt is not dismiss if the user taps on screen. -Reproducible with all the prompts.
Comment 1•7 years ago
|
||
Yes.. this is the expected behavior for "Confirm" type dialog. We need some UX decision here.
Flags: needinfo?(tchen)
Comment 2•7 years ago
|
||
Current Fennec in-app messages allow users to close and go back to previous page by pressing back button. From UX perspective it's better to make it consistent.
Flags: needinfo?(tchen) → needinfo?(cnevinchen)
Comment 3•7 years ago
|
||
per triage with Nevin, let's make it a P2 given it is the current 3rd party behavior and we should use this in app message with caution. In the mean time we should ask for a fix from our partner
Priority: -- → P2
[triage] Bulk edit: product thinks leanplum is high priority: P1 rank 1.
Rank: 1
Priority: P2 → P1
Blocks: leanplum-priority
Updated•6 years ago
|
Whiteboard: [Leanplum]
Comment 6•6 years ago
|
||
This can wait until 61, considering we will be replacing dialogs with banners (https://bugzilla.mozilla.org/show_bug.cgi?id=1438680)
Updated•6 years ago
|
Whiteboard: [Leanplum] → [Leanplum] [61]
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → vlad.baicu
Reporter | ||
Comment 7•6 years ago
|
||
Tested again on latest Nightly build (2018-04-02) with affected device Huawei Honor (Android 5.1.1) and Google Pixel (Android 8.1.0) and this issue is not reproducing. I will close this bug as WORKSFORME.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•