Closed
Bug 1300520
Opened 8 years ago
Closed 8 years ago
scrolling broken on http://reader.aol.com after installing firefox-49.0b9
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jack, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20160829102229 Steps to reproduce: Installed latest firefox-49.0b9 code on linux. SIgned into http://reader.aol.com and went to my subscriptions. Scrolled through list of articles with mouse. Actual results: The <nav class="nav pull-left"> part of the screen scrolled with the rest of the page and it should have been fixed. AND when it scrolled, it became corrupted and took a few seconds to refresh and correct it self. Seemed to be some sort of video issue. Expected results: I expected the <nav class="nav pull-left"> to NOT scroll as it does with all previous versions of firefox. I swiched back to firefox-49.0b8 and the problem was not there. It is JUST the firefox-49.0b9 version.
This is what you see when scrolling with firefox 49 b9. The fixed parts of the nav bars scroll with the page and get corrupted.
Comment 3•8 years ago
|
||
Firefox: 49.0b9, Build ID 20160901141622 User Agent Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Hi Jack, I have tested this issue on Firefox Beta 49.0b9 and I have managed to reproduce the issue with e10s disabled. Also, I have updated the Firefox beta 49.0b9 to Firefox beta 49.0 and the issue is no longer reproducible. It seems that this issue was fixed in the latest Firefox beta. Jack, can you please update your Firefox beta, retest this issue and report back the results?
Flags: needinfo?(jack)
I can confirm that the scrolling issue with aol reader has been fixed with the Firefox 49 b10 build. Thanks
Comment 5•8 years ago
|
||
Thanks for testing this so quickly. Considering this, I will close this issue as Resolved - Worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jack)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•