There is a Chromium bug filed for that: https://issues.chromium.org/issues/364634040.
We've run into the same issue, and I confirmed that it used to work as expected before Chrome v127.