4 ms·
From a link in the bug report, it's a WebKit rendering bug that was fixed over half a year ago. Either Chrome's release schedule doesn't include updating WebKi
by alec 16y ago
From a link in the bug report, it's a WebKit rendering bug that was fixed over half a year ago. Either Chrome's release schedule doesn't include updating WebKit frequently or the fix was incomplete.