A common source of layout bugs we're seeing these days involves the output of measureText() being fed into StaticLayout's constructor. measureText() returns subpixel-accurate values, but StaticLayout only takes integral bounds, resulting in the subpixel portion of the bounds being truncated. This leaves StaticLayout with insufficient space to layout the text that was just measured, causing all manner of unexpected line breaks. This could be causing issues elsewhere, as well. Until our text pipeline is fully subpixel-perfect, it's best that measureText guarantee that the value it returns will be sufficient to contain the text, even if cast to int. Cherry-pick of Ib84947f0d0a1229287f5b19b99e7efd40f5317f7 Bug: 8164205 Change-Id: I69795ba5770112c0a3d0e752158076a8d1646b1a
…
cherrypick from ics-mr1 docs: source for nw app Change-Id: If50f407a0e56fa802fe9beedaa650e3a131872b2
…
…
Description
No description provided
Languages
Java
77.3%
Kotlin
9.2%
PowerBuilder
6.6%
C++
5.5%
AIDL
1%