@DonoV (This may sound like passing the blame, and honestely ... it is ๐ ) Actually, if you had tried the same thing in Google Chrome or Edge (Thanks for not doing that) you would have seen the same issue (for another couple of days, unless you were using a recent Beta/Early Stable), since it was a regression that was introduced in Chromium 122 (and 3256 was still based on v120, until a few hours after that build was made, when 122 was integrated).
The Chromium team didn't get around to reverting the change that introduced it until a week ago, and that change did not get backported to 122 until after this week's Chromium security update.
We did grab that patch when we learned of it, so that it will be in a snapshot if we release it before the next security/stability update of 122 arrives in a few days, but for various reasons we unfortunately did not get around to one this week. Sorry.