See https://bugs.chromium.org/p/chromium/issues/detail?id=1432065 Basically, I thought that was a Chromium bug, but they think it's a WebKit bug.
<rdar://problem/108479586>
Add Test Case from Chromium bug in URL field and it is reproducible on WebKit ToT (273023@main). Both Chrome Canary 122 and Firefox Nightly 123 are matching each other, so adding 'BrowserCompat' since Safari is outlier.