Update here — this appears to be a Chromium/upstream issue and the team has already pushed a fix for this into Nightly for testing: