Laggy product-images carousel on intersport.ro
Categories
(Core :: Layout, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | unaffected |
| firefox80 | --- | unaffected |
| firefox81 | --- | disabled |
| firefox82 | --- | verified |
People
(Reporter: cfogel, Unassigned)
References
(Regression, )
Details
(Keywords: regression, Whiteboard: [qf])
Attachments
(1 file)
|
1.22 MB,
image/gif
|
Details |
Affected versions
- 81.0a1 (2020-08-12);
- 82.0a1 (2020-08-24);
Affected platforms
- Windows 10, Ubuntu 18;
Steps to reproduce
- Launch Firefox;
- Set the browser over half the screen so @media-querries affect the page-resize;
- Access this link;
- Click on the carousel to swap between images;
Expected result
- carousel goes smooth;
Actual result
- swapping images is laggy;
Regression range
- potential regressor: 1656418;
- pushlog URL;
- last good: 2020-08-02;
- first bad: 2020-08-03;
Additional notes
- attached screenshot with the issue;
- macOS 11.0 appears to work fine;
- suggested severity is S3, since it yelds a poor UX on the site.
Comment 1•10 months ago
|
||
Hi, can we please get a profile created with https://profiler.firefox.com/?
Comment 2•10 months ago
|
||
(Typically perf issues are not webcompat issues, but we can move this later)
| Reporter | ||
Comment 3•9 months ago
|
||
Got it, thanks for the headsup.
Profile linked here, navigating through the carousel for a couple of images.
Comment 4•9 months ago
|
||
Hi Mike, can I assume from P3 that severity is S3 or S4 ? Thank you!
Comment 5•9 months ago
|
||
(In reply to Jens Stutte [:jstutte] (REO for FF 81) from comment #4)
Hi Mike, can I assume from P3 that severity is S3 or S4 ? Thank you!
Yeah, something like that :)
| Reporter | ||
Comment 7•9 months ago
|
||
Updated the regression range in the initial comment.
@hiro, could you confirm if it's indeed accurate?
Tank you!
| Reporter | ||
Comment 8•9 months ago
|
||
82.0a1 (2020-08-24) is also affected.
Comment 9•9 months ago
|
||
Yeah, it's very plausible. Unfortunately the UI on the site seems to be totally different, when I click the image the image gets zoomed in.
I am wondering whether there is an ancestor scrollable element and its overflow style is hidden.
Also note that if bug 1656418 is the culprit, you can easily check it by flipping layout.animation.prerender.partial.
The product::component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.
Comment 11•9 months ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #9)
Unfortunately the UI on the site seems to be totally different, when I click the image the image gets zoomed in.
This is the behavior when the site is displayed in the large window. When I resize the window so that the width of the page is <900px, the behavior of the page changes.
Comment 12•9 months ago
|
||
(In reply to Florian Quèze [:florian] from comment #11)
(In reply to Hiroyuki Ikezoe (:hiro) from comment #9)
Unfortunately the UI on the site seems to be totally different, when I click the image the image gets zoomed in.
This is the behavior when the site is displayed in the large window. When I resize the window so that the width of the page is <900px, the behavior of the page changes.
With layout.css.devPixelsPerPx=1.6, even the window size is smaller than 900px, the UI is totally different, I don't know why.
Anyways, I believe this is another variant of bug 1660089, there is an overflow:hidden ancestor element. I just pushed a patch in bug 1660089, but I haven't have time to write a reftest for that.
Comment 13•9 months ago
|
||
Cristian, can you please confirm whether the issue persists on the latest nightly? Now bug 1660089 landed in m-c, I think the new nightly hasn't built yet, but it's coming soon.
| Reporter | ||
Comment 14•9 months ago
|
||
Added both on my TODO list for tomorrow, will check it up.
Updated•9 months ago
|
Updated•9 months ago
|
| Reporter | ||
Comment 15•9 months ago
|
||
Good news, it appears to have fixed the issue and the carousel is working fine as well on this website.
Setting this bug as duplicate to bug 1660089.
Verified with 82.0a1 (2020-08-27).
Comment 16•9 months ago
|
||
Thank you, Cristian!
Description
•