Closed
Bug 1375820
Opened 7 years ago
Closed 7 years ago
Layout glitches on image slider on Chrome Web Store
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1373479
People
(Reporter: gerd.neumann, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170622030208 Steps to reproduce: Go to an image slider on the Chrome Web Store, e.g. https://chrome.google.com/webstore/detail/web-design-pirate/pdplijceapgnjafgenmlijejmjgplbhm Actual results: During the image slide (happens automatically after a few seconds or by hovering the bullets on top of the slider with the mouse) then during the image transition, there are layout glitches. See screenshot. The bug is present on Windows and on Ubuntu with Firefox 56 Expected results: It did work in Firefox 54. There's the output of mozregression on windows: app_name: firefox build_date: 2017-06-13 23:56:27.704000 build_file: C:\Users\mel\.mozilla\mozregression\persist\2882dfa38314--mozilla-inbound--firefox-56.0a1.en-US.win64.zip build_type: inbound build_url: https://queue.taskcluster.net/v1/task/Y20SP6vcQtG9R8h46LjrPg/runs/0/artifacts/public%2Fbuild%2Ffirefox-56.0a1.en-US.win64.zip changeset: 2882dfa3831474f6361d425e3f462c634512e9d0 pushlog_url: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=2882dfa3831474f6361d425e3f462c634512e9d0&tochange=3e62702024b0b588d8b00a65d2ac7e04801326b2 repo_name: mozilla-inbound repo_url: https://hg.mozilla.org/integration/mozilla-inbound task_id: Y20SP6vcQtG9R8h46LjrPg off-topic: FWIW, I would be interested why the pushlog is always this huge? This one includes like 13 pushes and many more commits. Makes it hard to neal down the commit that caused the regression. Why isn't there a build for each push at least?
Updated•7 years ago
|
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•