Created attachment 158171 [details] screenshot I was viewing: https://bugs.webkit.org/show_bug.cgi?id=93901#add_comment See attached screenshot. This is in Chrome Version 22.0.1229.2 dev, but I suspect it to be a WebKit issue.
I see this regularly, but I don't know how to reliably trigger it.
I've noticed this a while ago. Maybe this is WK1 specific? I don't remember seeing this on Qt MiniBrowser.
It's very possible that some ports overpaint enough to compensate for this underpainting. :)
Too old bug and surely we might have fixed it over the period and now Safari 16, Safari 17 works fine on bugs.webkit.org and use it every day. Marking this as "RESOLVED CONFIGURATION CHANGED".