1514586 - Opened tabs cannot navigate to a different location

Status: RESOLVED DUPLICATE of bug 1494748

(Firefox for Android Graveyard :: General, defect)

Description

[Gurenko Alex]

Attachment: Screenshot_20181216-161138.png

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

1) Open a tab or several tabs
2) Put phone to sleep for some time (not sure how long exactly, does not work immediately, takes some time)
3) Wake up phone
4) Open Firefox
5) Try to navigate to a different page in one of the tabs that been opened before (including Firefox home page)

I'm using Android 9 with latest security patches on Pixel 2 phone.


Actual results:

Nothing happens if new address or search text is typed and Go button is pressed. No load animation is shown, however address bar changes to the typed address.


Expected results:

You should be able to navigate to a desired page or get a search results for typed query without closing tabs or playing around with refresh and other tabs.

Comment 1

[Stefan Deiac]

Hi, thanks for your report.
I tried to reproduce your issue following your information from the description using Google Pixel (Android 9) and OnePlus 5T (Android 8.1.0) on the latest version of Nightly 66.0a1 (2018-12-17) and Release 64.0.1 and I wasn't able(I was let the phones more than two hours in sleep mode). Do you have some specific option or add-ons installed? Also, if you can send us a video with the problem it will be very helpful. I'll wait for your update, thanks.

Comment 2

[Jan Henning [:JanH]]

Likely bug 1494748.

Comment 3

[Gurenko Alex]

Attachment: videoshot

Hello Stefan, I've attached a video recording of what's happening. I only have 1 addon - uBlock.

Comment 4

[Mihovil Stanic [:Mikeyy - L10n HR]]

Good job Alex on video, I have exact same issue. It was introduced in FF for Android 63.
You can get around it by closing affected tab. Hopefully they will find fix for it since it's annoying.

Samsung S9
Android 8.0.0.
FF 63 and 64

Comment 5

[Gurenko Alex]

(In reply to Mihovil Stanic [:Mikeyy - L10n HR] from comment #4)
> Good job Alex on video, I have exact same issue. It was introduced in FF for
> Android 63.
> You can get around it by closing affected tab. Hopefully they will find fix
> for it since it's annoying.
> 
> Samsung S9
> Android 8.0.0.
> FF 63 and 64

Yes, I saw the corresponding bug and it's so annoying, I know that force closing works or closing the affected tab, but overall, experience right now is very unpleasant, because I have to do it dozens of times per day. What bothers me is that BZ1494748 was opened 3 months ago and wasn't fixed for FF64, meaning it won't be fixed until 65 (if we're lucky) or even 66, e.g. we have to live with this for next half a year.