tree 6a753ada523320f2ac3c2781e5594eab1fcabac8
parent 2b97f0cf4de0d51123f567115a64e8b42afa8dec
author Jason Simmons <jason-simmons@users.noreply.github.com> 1602701078 -0700
committer GitHub <noreply@github.com> 1602701078 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfh0cWCRBK7hj4Ov3rIwAAdHIIAAFohbqggjePVsSIHvlojoAC
 R9s+FORdiT8MW514a8N1tQ4q4E9Jgv5SK2k0f6A5VWGBTKU5s7K88rb3yGWu8lNr
 BvgFrATwQqlisDU5Nc4wIyBVhFvM1H07lhua5S0mrzkf89Z1rzJajAZZsmrHF676
 m2AhlTEY1xJPVaH6YzBeeJqWTTe455QjvlatvGMZ5j+eqXpsizKCE/i/RMg1bGMV
 ivPfLHZry1odXA+2vwCL1kyQb07fdE3gwFwqOgxbW99I8og6ugRbOjjqJ7DoI2TI
 FOCdAOcHxiHM0SqflGL+ZOxfqwuWSI2gxHPoJTZSuDfR3JFRdvs1MEV7/h9TRRU=
 =bm1r
 -----END PGP SIGNATURE-----
 

Fix the offset passed to minikin::GraphemeBreak::isGraphemeBreak (#21706)

The character offset passed to isGraphemeBreak is relative to the beginning
of the string (not relative to the text_start parameter).  This caused bad
results when searching for grapheme breaks beyond the first line of text
(see https://github.com/flutter/flutter/issues/24802).

This PR fixes the offset value.  It also reverts the workaround applied in
https://github.com/flutter/engine/pull/10063, which caused incorrect
calculation of boundaries between graphemes within ligatures.