Hi there,
I’m constantly seeing season posters overlapping when on Chrome browser from the Trakt website. It happens both for landscape and portrait orientation. If I refresh the page, it shows up correctly (not overlapped). This is from my Samsung Galaxy Tab S9+ tablet.
Screenshots of the overlapping of posters.
Portrait:
Landscape:
It works fine on Chrome on my iphone and works fine on Chrome on my Windows laptop.
Is this something you’ll be able to fix?
I’ve been having similar issues on the mobile site as well for the last few months.
From the show’s main page, the seasons will overlap, and from the season page, episodes will overlap.
Happens on both chrome and the samsung browser for me, but the issue doesn’t always occur ever page load, it’s intermittent. Refreshing the page corrects the issue.
Thanks all for testing out on your devices. I just also tested in Chrome on my Samsung Galaxy A14 phone and also has the same issue.
I do agree it seems like the pattern of issues happens on Chrome browser exclusively on any Samsung tablet or phone device running Android.
This is a weird bug. It seems that device/browser is somehow affecting the CSS or JavaScript on the page. Does the orientation of the device matter? Any extensions that Samsung might pre install on Chrome?
it affects both landscape and portrait orientation in the same way where it overlaps until i refresh the page. i normally use landscape on my samsung tablet and portrait on my samsung phone.
no, not that i’m aware. chrome on tablets and phones do not have any extensions that you’re allowed to use like on windows laptops.
If there’s any particular setting(s) or configuration(s) you’d like me to check, I can get you that. Just need to know what you would like to see and where I can get you that info.
Hi @justin - any updates on this visual bug?
I don’t have any Samsung devices to try and reproduce the issue. I haven’t been able to see the issue on any other device or desktop browser so far.
is there anything I am able to grab for you as a diagnostic log that could help you pin point where they issue may reside in within Chrome browser from my Samsung devices?
