Activity stream - An incomplete preview context menu is displayed when the keyboard is triggered

NEW
Unassigned

Status

()

Firefox for Android
Activity Stream
P3
normal
Rank:
2
a year ago
5 months ago

People

(Reporter: carmenf, Unassigned)

Tracking

54 Branch
ARM
Android
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox54 affected)

Details

(Whiteboard: [MobileAS])

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8836089 [details]
One option preview menu.jpg

Environment: 
Device: Huawei Honor 8 (Android 6.0);
Build: Nightly 54.0a1 (2017-02-09);

Prerequisites: Activity stream is enabled.

Steps to reproduce:
1. Open Firefox;
2. Go to Activity stream Panel;
3. Tap once on the URL bar to focus it and to trigger the keyboard;
4. Tap on the 3 dots icon to open the context menu (either from Top sites or Highlights area websites).

Expected result:
URL bar is not focused anymore;
Keyboard is dismissed;
Preview context menu is triggered - depending the screen size first 5 or 6 options (Open in New Tab; Open in Private Tab; Delete from History; Bookmark; Share, Copy Address).

Actual result:
Only one option is displayed when context menu is triggered.
Also, sometimes, the context menu wasn't even triggered after first trying.

Notes:
Please see the screenshot attached.
Also tested using Oneplus Two (Android 6.0.1) and Motorola Razr xt910 (Android 4.4.4) and the difference is that on these 2 devices, there are 2 options when the context menu is triggered.
(Reporter)

Updated

a year ago
Whiteboard: [MobileAS]
Blocks: 1311099
Blocks: 1377248

Updated

8 months ago
Rank: 2
Priority: -- → P3
All open Activity Stream bugs are moving from the whiteboard tag, "[mobileAS]", to the Firefox for Android component, "Activity Stream", so that I can keep better track of these bugs as the new triage owner; I will send out an email shortly with additional details, caveats, etc.
Component: General → Activity Stream
I verified that this is still an issue in the current build. It's likely we're calculating how high the context menu needs to be based on the visible screen size, which is smaller when the keyboard is expanded.
You need to log in before you can comment on or make changes to this bug.