Closed
Bug 1369013
Opened 9 years ago
Closed 9 years ago
[LeanPlum] - Keyboard not displayed when going back from the Search Engine trigger
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(firefox55 affected)
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | affected |
People
(Reporter: bsurd, Unassigned)
References
Details
(Whiteboard: [LP_M1])
Attachments
(1 file)
|
234.38 KB,
image/png
|
Details |
Devices:
- Nexus 5 (Android 6.0.1);
- Nexus 7 (Android 7.0);
Steps to reproduce:
1. Open Fennec and tap on the URL bar.
2. Tap on "Yes" in the Promote Search Engine trigger.
3. Tap on back.
Expected result:
The user is taken back to the previous page with the search bar highlighted and the keyboard displayed.
Actual result:
The keyboard is not displayed.
Comment 1•9 years ago
|
||
Hi Joe
This is expected and also the reason why we need UX review about deep link / trigger combination.
Maybe we should discuss about the UX here.
Flags: needinfo?(jcheng)
Comment 2•9 years ago
|
||
I've seen it in Fennec somewhere but I can't reproduce it now. As long as the keyboard can be displayed by clicking the search field again while search field is highlighted, I am fine with it. I would see it as a minor bug that we can fix it later.
Flags: needinfo?(cnevinchen)
Comment 3•9 years ago
|
||
given how the in app message is displayed in the initial implementation (unless we can make the HTML5 message work), we should not promote this use case. making this is P2
Flags: needinfo?(jcheng)
Priority: -- → P2
Comment 4•9 years ago
|
||
we should not interrupt user's current flow of typing and search. if we were to do this use case, i suggest we defer this message to the next app launch and say something like "you've been searching with Firefox quite a bit, do you know that you can change your default search provider?"
Comment 5•9 years ago
|
||
Disabled this message on leanplum server side per product manager's decision.
Flags: needinfo?(cnevinchen)
Comment 6•9 years ago
|
||
We have disabled this message so we can close the bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•9 years ago
|
Whiteboard: [LP_M2]
Updated•9 years ago
|
Whiteboard: [LP_M2] → [LP_M1]
| Assignee | ||
Updated•5 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
•