The issue is Chrome-specific, tracked upstream in https://bugs.chromium.org/p/chromium/issues/detail?id=1016161