Closed
Bug 1359673
Opened 8 years ago
Closed 8 years ago
Latest update (Ver. 54 April 24, 2017 release date per google play) has disabled settings and help tab in Firefox Beta, as well as disabled both hardware and arrow tab back buttons
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: AnthonyRich2005, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
User Agent: Mozilla/5.0 (Android 5.0; Mobile; rv:54.0) Gecko/54.0 Firefox/54.0
Build ID: 20170420095842
Steps to reproduce:
I have noticed several problems with this latest update with Version 54 Firefox Beta. Firefox Ver. 53 (Official Release) works as it should (I have both installed.).
The Settings and Help tab have both been disabled (greyed out) and cannot be used/selected.
The back/previous page function has also been disabled. You cannot go back using the android back function on the phone nor the in browser previous page/back arrow button. The back arrow is not greyed out, however selecting it does nothing.
I have also noticed that a ghost window (blank screen area the size of the keyboard) appears above the actual keyboard on certian webpages, and in doing so takes up roughly 90% to 95% of the screen, so that you cannot see what you are looking at, and/or typing. However, exiting out of the QWERTY/keyboard and reopening by selecting the open field/text box sometimes fixes this issue. I am using a Samsung Galaxy Note 3 N900v, fully rooted, however the OS is pretty stock Lollipop 5.0. More details to follow when I get time. Please email me with questions, and I will do what I can to answer them.
Comment 1•8 years ago
|
||
I think this was accidental fall-out from the fix for bug 1356563. Should be fixed in 54b2 (https://hg.mozilla.org/releases/mozilla-beta/rev/8dbf9446a944).
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•4 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
•