This looks a lot like an upstream bug on Chromium for Android, I’ve been trying a workaround that I intend to push this week (and I’ll review the bug surface to report upstream if that’s really the case).
1 Like