Closed Bug 1345480 Opened 8 years ago Closed 5 years ago

After sharing multiple times the last sharing options is not displayed near share icon

Categories

(Firefox for Android Graveyard :: General, defect, P3)

ARM
Android
defect

Tracking

(firefox53 affected, firefox54 affected, firefox55 affected, firefox63 affected, firefox64 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox53 --- affected
firefox54 --- affected
firefox55 --- affected
firefox63 --- affected
firefox64 --- affected

People

(Reporter: sflorean, Unassigned)

Details

Environment: Device: - Samsung Galaxy Note 4 - Android 5.0.1 - HTC 10 - Android 6.0.1 Build: Nightly 55.0a1 (2017-03-08); Steps to reproduce: 1. Open Fennec and load mozilla.org; 2. Open the Custom Menu and choose "Share"; 3. Share page several times (more than 8) with different options (e.g. Gmail, twitter) that are available on device; 4. Open the Custom Menu and observe the behavior of share options (shortcuts). Expected result: After sharing to gmail once, the gmail shortcut appears on the right of the share icon in the Custom Menu and the same with next one. Actual result: After sharing multiple times, the last sharing options is not displayed near share icon. Notes: Check the video: https://www.youtube.com/watch?v=KW_nlOLxJc8
Priority: -- → P3
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.