Closed
Bug 1341610
Opened 7 years ago
Closed 3 years ago
An extra arrow is displayed in googles account creation drop down menu
Categories
(Firefox for Android Graveyard :: Awesomescreen, defect)
Tracking
(platform-rel ?, firefox51 affected, firefox52 wontfix, firefox53 affected, firefox54 affected)
People
(Reporter: bsurd, Unassigned)
Details
(Whiteboard: [platform-rel-Google])
Attachments
(1 file)
107.51 KB,
image/png
|
Details |
Device: - Huawei Honor 8 (Android 6.0); - Motorola Nexus 6 (Android 7.0); - Huawei Honor 5X (Android 5.1.1); Steps to reproduce: 1. Go to google.com; 2. Tap on Sign in and then select Create account 3. Scroll down (if necessary) until the Birthday field is visible; 4. Observe the drop down menu arrows. Expected result: The menu is displayed without any issue. Actual result: There is an extra down facing arrow for each of the menus in the google account creation page. Notes: The only site I've noticed this happen was in the google account creation page, other sites that have drop down menus don't seem to have this problem.
Comment 1•7 years ago
|
||
Too late for firefox 52, mass-wontfix.
Comment 2•6 years ago
|
||
This is likely a duplicate of bug #1368555
platform-rel: --- → ?
Whiteboard: [platform-rel-Google]
Comment 3•3 years ago
|
||
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: 3 years ago
Resolution: --- → INCOMPLETE
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
•