Tested it out on Chrome 125 Beta on BrowserStack, and it got solved properly!

Unfortunately there's still a bit of eye before this Chrome version gets on CI, I'll keep an eye out and close the issue as soon as the automated test does not raise a warning about this anymore