No, it is purely a browser issue.
The latest canary build has a fix for the issue: Release: 2.3.0.101 (Canary) 2026-05-04