Weird, I can't reproduce this in ungoogled chromium (117) with any of these domains. Is this a newly introduced bug?