This problem should now be solved for Chromium (>=114.0.5735.198). Please confirm or deny it if you are a Chromium user previously affected by this bug.
This problem should now be solved for Chromium (>=114.0.5735.198). Please confirm or deny it if you are a Chromium user previously affected by this bug.