Closed
Bug 1305283
Opened 8 years ago
Closed 8 years ago
Iframe scroll position restart
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1305579
People
(Reporter: regnetcc, Unassigned)
References
Details
(Keywords: regressionwindow-wanted, testcase-wanted)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20160924030427 Steps to reproduce: Can't provide the website as they are company internal portal, but I have create a edit screenshot for an idea http://screencast.com/t/XUzdDldFg: 1. Scroll down to any where of the page in iframe web 2. click to other tax section 3. back to original tab section Actual results: Firefox scoll back the web to the top of web in iframe Expected results: In Firefox 48.0.2 32 bit / Windows 10 64 bit, page scroll position should be still in the position where we left.
Summary: Iframe scroll position restart everytime → Iframe scroll position restart
It would be nice if you could attach a minimal testcase to reproduce the issue.
Flags: needinfo?(regnetcc)
Keywords: testcase-wanted
Screen record with Firefox Nightly 52, Firefox 49 and above should have the same result - scroll position reset to top of the page. http://screencast.com/t/ci5njCN9zl Expected result from Firefox 48.0.2 - scroll position unchanged http://screencast.com/t/A8LsQQc7mIf This is the best I can help, I can't find any website have similar design to reproduce.
As you can't provide a public testcase, you need to run the tool mozregression to narrow down a regression range. See http://mozilla.github.io/mozregression/ for details.
Keywords: regressionwindow-wanted
app_name: firefox build_date: 2016-05-27 22:55:29.721000 build_file: C:\Users\#######\.mozilla\mozregression\persist\33c4562b47ce--mozilla-central--firefox-49.0a1.en-US.win32.zip build_type: inbound build_url: https://queue.taskcluster.net/v1/task/Euwy--w3Rxemm5DGwkE8TQ/runs/0/artifacts/public%2Fbuild%2Ffirefox-49.0a1.en-US.win32.zip changeset: 33c4562b47ce2cc5e2988d756c76fa79a36c469a pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4d63dde701b47b8661ab7990f197b6b60e543839&tochange=33c4562b47ce2cc5e2988d756c76fa79a36c469a repo_name: mozilla-central repo_url: https://hg.mozilla.org/mozilla-central task_id: Euwy--w3Rxemm5DGwkE8TQ
Hopefully that is the information you are looking for, otherwise I have a copy of log. Let me know if you need more information. Thank you.
Maybe bug 881832. Anyway, it's hard to tell without a testcase. :/
Can you make a simple web has iframe and similar design to the clip I upload? This is the best I can do, I saved the portal website but there is so many private information and I don't know how to delete all the text on the web. The issue still can be duplicate on the offline file. If you can show me how to remove all the web content, I maybe send you and portal without content and you can duplicate the error.
I think you can remove all the page content to replace it with a random long page (to have scrolling available) and keep only the menu bar to switch between pages.
Comment 9•8 years ago
|
||
Looks like Bug 1117640
Updated•8 years ago
|
Reporter | ||
Comment 10•8 years ago
|
||
The test case in https://bug1117640.bmoattachments.org/attachment.cgi?id=8549602 different with what I report, my company portal site only have scroll issue with Firefox 49 uppon, Firefox 48.0.2 working nicely.
Comment 11•8 years ago
|
||
(In reply to Nokizilla from comment #10) > The test case in > https://bug1117640.bmoattachments.org/attachment.cgi?id=8549602 different > with what I report, my company portal site only have scroll issue with > Firefox 49 uppon, Firefox 48.0.2 working nicely. Okay. Please provide a testcase or public URL to reproduce the problem.
Comment 12•8 years ago
|
||
try running this on Mozregression Command |mozregression --launch 759d94861665| (this build should be bad) |mozregression --launch 85f5fe4d8e30| (this build should be good). This will check if bug 881832 is the culprit.
Reporter | ||
Comment 13•8 years ago
|
||
mozregression --launch 759d94861665 - bad mozregression --launch 85f5fe4d8e30 - good Thanks Justin.
Comment 14•8 years ago
|
||
Hey Mats, it looks like bug 881832 caused this regression. Can you take a look at this?
Depends on: 881832
Flags: needinfo?(mats)
Comment 15•8 years ago
|
||
Sorry I did that backwards.
Comment 16•8 years ago
|
||
I think we need a testcase or URL here to be able to investigate what the problem is.
Flags: needinfo?(mats)
Reporter | ||
Comment 17•8 years ago
|
||
Seem like the issue has been fixed in Nighly build 20160929030426. I tested on two pc. Did you fix it?
Comment 18•8 years ago
|
||
Bug 1305579 landed, which might have fixed this. You can verify by running mozregression to check the builds immediately before and after that bug landed. mozregression --launch=f52d02de70b2 --repo=autoland mozregression --launch=d2cce59a6d01 --repo=autoland f52d02de70b2 has the fix for bug 1305579. d2cce59a6d01 does not have the fix for bug 1305579.
Reporter | ||
Comment 19•8 years ago
|
||
I'm not developer so I got this error when copy your code: C:\WINDOWS\System32>mozregression —launch=f52d02de70b2 —repo=autoland usage: mozregression-script.py [OPTIONS] [--bad DATE|BUILDID|RELEASE|CHANGESET] [--good DATE|BUILDID|RELEASE|CHANGESET] mozregression-script.py [OPTIONS] --launch DATE|BUILDID|RELEASE|CHANGESET mozregression-script.py --list-build-types mozregression-script.py --list-releases mozregression-script.py --write-conf mozregression-script.py: error: unrecognized arguments: ùlaunch=f52d02de70b2 ùrepo=autoland
Reporter | ||
Comment 20•8 years ago
|
||
mozregression --launch d2cce59a6d01 ----- BAD mozregression --launch f52d02de70b2 ----- GOOOOOD
Reporter | ||
Comment 21•8 years ago
|
||
mozregression --launch d2cce59a6d01 —repo=autoland ----- BAD however, mozregression --launch d2cce59a6d01 without repo auto land is good. Unsure if I test properly, please let me know if you need more info
Comment 22•8 years ago
|
||
You need the repo part to test properly. There needs to be two dashes before repo, not just one.
Reporter | ||
Comment 23•8 years ago
|
||
Doing the samething copy and paste, now the PyPM work, result bellow: mozregression --launch=f52d02de70b2 --repo=autoland | GOOD mozregression --launch=d2cce59a6d01 --repo=autoland | BAD
Comment 24•8 years ago
|
||
Perfect thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(regnetcc)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•