Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
Pixel 6
- Build: TP1A.220905.004
Debugging this together I noted the only difference between google-sans* and google-sans-text* is opsz, which seems suspect.
<family customizationType="new-named-family" name="google-sans">
<font weight="400" style="normal">GoogleSans-Regular.ttf
<axis tag="GRAD" stylevalue="0"/>
<axis tag="opsz" stylevalue="18.0"/>
<axis tag="wght" stylevalue="400"/>
</font>
...
</family>
<family customizationType="new-named-family" name="google-sans-text">
<font weight="400" style="normal">GoogleSans-Regular.ttf
<axis tag="GRAD" stylevalue="0"/>
<axis tag="opsz" stylevalue="17.0"/>
<axis tag="wght" stylevalue="400"/>
</font>
This seems suspect, as google-sans and google-sans-text have different letter shapes that I don't believe would be covered by opsz
Rod, it looks like we might be shipping the wrong font for google-sans-text
on production Pixel. Can you advise and forward as appropriate.
ap...@google.com <ap...@google.com> #3
Pixel 6 TP1A
jb...@google.com <jb...@google.com> #4
Context from dupin@ introduced with VF in ag/13832548
It looks like we are missing specializations there. Rod can you advise?
Description
Seems like the regex takes longer due to the case insensitivity. Please close if WAI.
Alert on dashboard:https://androidx-perf.skia.org/t/?begin=1617055796&end=1617055797&subset=all
Culprit:https://android-review.googlesource.com/c/platform/frameworks/support/+/1656236
All cLs in build:https://android-master-ingest.skia.org/r/7243174?branch=aosp-androidx-main