Started by zim312 [1984387] on in Bugs & Issues.
Posts archived: 16 / 16 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
I've tried disabling torn tools, and all tampermonkey scripts, tried from 3 different resolution monitors, even used an incognito tab to remove possibility of any extension altering the data.
Why does my list of custom races look like this since yesterday?
Is your browser zoomed in/out? You can press Ctrl+0 to reset the zoom.
Not zoomed, and just to see, I tried every value between 50% and 150% zoom, none of those looked right either
Is it reproducible in another browser on the same device?
Firefox looks normal, and this is what chrome looked like a few days ago. (Chrome version is 133.0.6888.2)
Edge also looks normal
Chrome still looks like this.. but I see why you thought it was zoomed or something, I can't see as many of the of races on screen in the same area of chrome, but the font doesn't look any larger than firefox/edge screenshots
inspecting the element, in chrome:
this didn't look right .. 2 divs's with same id?
Then I noticed even in an incognito tab (no extensions/etc just browser) there are several div with duplicate id errors in the console.
Can you please provide your screen resolution, browser version where the bug is occurring and device OS?
Chrome Version 133.0.6888.2
resolutions I've tried
3840 x 2160
1920 x 1080
bug happens on https://www.torn.com/loader.php?sid=racing
Windows 11
Bug is specific to chrome, firefox and edge on same resolution, same page don't seem to have the display problem
Chrome:
Firefox:
Edge:
Passing along to Nikita for checking. Thanks..!!
Hello
Which system screen scale do you have?
Because sometimes, laptops are set to 125% by default (my case)
Thanks
4k Monitor:
1080p monitor:
Hello
Can't replicate it via set resolutions
Is the issue reproduced for you in the current live version (Chrome 131) ?
Because Chrome 133 version is currently dev version
Thanks
Chrome 131 does look correct, same as edge, firefox
Maybe, it's browser version related issue
We can wait until the Chrome 133 version will be on LIVE to re-check the issue
Or you can report a new issue if it will be reproduced in the Chrome 133 version LIVE
Passing up to CJ for making a decision
Thanks
We only really support the latest stable versions of the mainstream browsers. I will close this for now, as it is working fine on the current stable version 131. We can revisit this if it is an issue in version 133 after a stable release is out.
Thanks!
![[image: i.imgur.com]](https://i.imgur.com/kwnUbrv.png){kind=link}
![[image: i.imgur.com]](https://i.imgur.com/OAxNbz3.png){kind=link}
![[image: i.imgur.com]](https://i.imgur.com/QbaNOjE.png){kind=link}
![[image: i.imgur.com]](https://i.imgur.com/GWgVmWy.png){kind=link}