After testing with Browserstack, it seems like this is fixed on v132 of Chromium. This version should become stable around the 14th of January.