Closed Bug 1668686 Opened 5 years ago Closed 5 years ago

Using the back button in Yahoo answers the displayed page is blank

Categories

(Core :: Panning and Zooming, defect)

Product:
Core
Component:
Panning and Zooming
Version:
Firefox 81
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox81 --- wontfix
firefox82 --- unaffected
firefox83 --- unaffected

People

(Reporter: dgaguine, Unassigned)

Details

Attachments

(1 file, 1 obsolete file)

Screenshot 2020-10-01 230237.png
94.99 KB, image/png
Details
Attached image Screenshot 2020-10-01 163352.png (obsolete) —

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

In Yahoo answers scroll down so you can see a question that is off the page and click on it to see any answers. Then press the back button

Actual results:

A blank page is displayed where the list of questions were, the titles and side screens are not present, the vertical shaded scrollbar box that you can grab to move up and down the page is also not present. If you roll the mouse wheel or click on the vertical scroll bar the questions/titles and other elements reappear.

Expected results:

The list of questions should reappear without having to roll the mousewheel or click on vertical scroll bar

This bug appears to be very similar to bug Bug 488701 which was had status
resolved incomplete
some years ago. This only affects Firefox 81

Attachment #9179135 - Attachment is obsolete: true

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Panning and Zooming
Product: Firefox → Core

(In reply to David Gaguine from comment #0)

This only affects Firefox 81

By this, do you mean it started happening in Firefox 81 and wasn't present in previous versions (80 and below)? Or do you mean you tested Firefox Beta 82 and Nightly 83 and it doesn't occur there? Assuming the former, can you please test the current Nightly and see if the problem still occurs? It would also be useful if you used mozregression to find the regression range where this started happening.

Flags: needinfo?(dgaguine)

It started happening with FF 81 about 2weeks ago. It wasn’t present before this. I have installed the nightly version 83.0a1 (2020-10-02) and on a brief test the problem is no longer present.
I tried to use mozregression but even after disabling my antivirus (flagged it as a infection) kept getting an installation error

Flags: needinfo?(dgaguine)

(In reply to David Gaguine from comment #4)

It started happening with FF 81 about 2weeks ago. It wasn’t present before this. I have installed the nightly version 83.0a1 (2020-10-02) and on a brief test the problem is no longer present.

That's good news, hopefully it means the issue has been fixed already.

I tried to use mozregression but even after disabling my antivirus (flagged it as a infection) kept getting an installation error

That's unfortunate - I was having the same problem not too long ago when I tried to install the GUI for mozregression. Apparently it's a known issue and somebody will hopefully fix it.

But in the meantime, it would be helpful if you went to about:support in both FF 81 and the nightly version and did a quick comparison of the first couple of lines in the "Graphics" section (specifically, the Compositing and the Asynchronous Pan/Zoom lines) to see if they're the same. If they're not then it's possible the Nightly version is running with a different configuration and the bug only appears in the release configuration.

Flags: needinfo?(dgaguine)

The only difference in the two versions is "smooth pinch-zoom enabled" is present in FF nightly in Asynchronous Pan/Zoom line and absent in FF81

Flags: needinfo?(dgaguine)

Ok. It's probably worth turning that off in the Nightly build to make sure that's not interfering. In the Nightly build, go to about:config, search for the apz.allow_zooming pref, and double-click on it to set it to false. Then restart Nightly and see if you can reproduce the issue. If you can, then we know it was likely fixed by the zooming code paths; if you can't reproduce it then it may have been fixed by something else, or might be due to some other configuration change.

Sadly, changing the settings in about:config did not reproduce the problem in Nightly

Hopefully that means the issue is resolved already. Since mozregression isn't working for you, perhaps we can spot-check a few builds manually. The 81 release branched from nightly on August 24, so unless the regression was introduced by an uplift to beta/release, the nightly build in this folder should show the problem. If it doesn't, then maybe try the last 81 beta build from this folder. If that doesn't show it either then most likely the problem is specific to your release Firefox profile or intermittent.

Sorry to be a pain, if I try to install FF81 from the link you provided http://archive.mozilla.org/pub/firefox/nightly/2020/08/2020-08-24-09-44-58-mozilla-central/ it immediately updates to FF 83.0a1 (2020-10-06). I have tried uninstalling nightly 83.0a1, I have deleted the contents of the nightly directory. I have disabled all network connections and then trying to run the installer (wouldn't install), How do I prevent it updating?

Ah yeah, sorry about that, I should have realized that would happen. You can disable the auto-updating by going to about:config and setting the app.update.auto preference to false.

Also FYI it might be easier if you download the .zip file (e.g. firefox-81.0a1.en-US.win64.zip) from that folder, instead of the installer. You can just unpack the .zip file and run the firefox.exe file instead, without going through the "installation" process.

Thank you unzipping the file worked and I can confirm that the build 81.0a1 (2020-08-24) does show the problem

Ah that's good news, it means that between August 24 and now a fix already landed. So the problem will definitely be fixed in Firefox 83, and depending on when it landed it may be fixed in Firefox 82 as well. If you have the time to spare you could try the September 21 nightly or one of the Firefox 82 beta builds to see if the fix made it in to Firefox 82. If it didn't we can bisect further and maybe uplift the fix to 82, but other than that there's not much to do here.

Thanks for your help in reporting the bug and verifying that the bug seems to be fixed! I'm going to mark this bug WORKSFORME as that's usually what we do in cases like this - if we do manage to figure out what fixed it we can mark this bug as a duplicate of that one instead.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
status-firefox81: --- → wontfix
status-firefox83: --- → unaffected
Resolution: --- → WORKSFORME

Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.

status-firefox82: --- → ?

FF82.0a1 2020-09-19 problem is fixed

Great, thanks again for checking!

status-firefox82: ? → unaffected
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: