[Measurer] CachedCharacterMeasurer does not work properly

[rcchen]

Given the string “27.2”, we compare the following:

• Sum of widths of individual characters: 35.233 (FF), 27.297 (Chrome)
• Width of string as a whole: 29.233 (FF), 27.25 (Chrome)

Should reevaluate whether there is a correct way of caching computations, or if this is something that cannot be done due to how fonts render on a computer.

[jtlan]

Does this happen only because of the decimal point, or are there other strings that reproduce this bug?

[rcchen]

Looks like it's not just the decimal. With the string "272", we get the following:

• Sum of widths of individual characters: 29.350 (FF), 23.391 (Chrome)
• Width of string as a whole: 25.350 (FF), 23.359 (Chrome)

[bluong]

Can you try "27" and "273" when you have the time?

[rcchen]

Format is as follows

test string: summed vs actual (browser)

"27": 19.566 vs 17.566 (FF), 15.594 vs 15.578 (Chrome)
"273": 29.350 vs 25.350 (FF), 23.391 vs 23.359 (Chrome)

[themadcreator]

perhaps your font is computing a ligature between 2 and 7?