RESOLVED INVALID111935
Something is wrong with kerning on text set with textContent 
https://bugs.webkit.org/show_bug.cgi?id=111935
Summary Something is wrong with kerning on text set with textContent
Stuart P. Bentley
Reported 2013-03-10 00:09:44 PST
Created attachment 192370 [details] Test case Characters have weird, uneven spacing when set dynamically. See test case. Expected behavior: The lines with identical text have identical character spacing. Observed behavior: The lines with dynamic text have uneven spacing, different from what they would have statically. Note that this only lasts until you force a rerender (eg. by resizing the window), at which point the bug is corrected.
Attachments
Test case (1.35 KB, image/svg+xml)
2013-03-10 00:09 PST, Stuart P. Bentley 		no flags
Details
Screenshot of bug in motion (10.12 KB, image/png)
2013-03-10 00:11 PST, Stuart P. Bentley 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Stuart P. Bentley
Comment 1 2013-03-10 00:11:17 PST
Created attachment 192371 [details] Screenshot of bug in motion
Alexey Proskuryakov
Comment 2 2013-03-11 12:34:03 PDT
Where are you seeing this issue? I cannot reproduce it with Safari 6.0.2 or current nightly.
Stuart P. Bentley
Comment 3 2013-03-11 14:36:00 PDT
Chrom(e/ium), version 25.0.1364, Windows 7, 8, and Arch Linux. It's possible it's a browser bug and not a WebKit bug, I don't have a copy of Safari to test on and didn't expect this to be a browser-level code path.
Philip Rogers
Comment 4 2013-03-12 11:28:21 PDT
Confirmed on Chrome 26.0.1410.28 beta. CC'ing schenney
Stuart P. Bentley
Comment 5 2016-12-13 15:09:38 PST
I don't know if this has been fixed in WebKit, but it was eventually fixed in Blink: http://crbug.com/299497
Ahmad Saleem
Comment 6 2022-06-14 16:12:31 PDT
I am unable to reproduce this in Safari 15.5 on macOS 12.4 and test case looks same with appropriate spacing (not like anything from attach bug screenshot). It is also consistent with other browsers (Chrome Canary 105 and Firefox Nightly 103). I think this can be closed as "RESOLVED CONFIGURATION CHANGED". Thanks!
Alexey Proskuryakov
Comment 7 2022-06-16 12:48:24 PDT
Seems like this only ever reproduced in Chrome.
Note You need to log in before you can comment on or make changes to this bug.