A followup here folks: a WebKit developer merged a fix for this issue a few weeks ago. I tried to test it using the nightly WebKit builds, unfortunately, I can still reproduce the problem. However, I may be doing something wrong. Will wait for the next Safari Technology Preview release (it should be soon) to test again, hopefully it is indeed fixed. (WebKit bug report is here.)
2 « J'aime »