Fixed
Status Update
Comments
cc...@google.com <cc...@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.
du...@google.com <du...@google.com>
sh...@meta.com <sh...@meta.com> #4
Context from dupin@ introduced with VF in ag/13832548
It looks like we are missing specializations there. Rod can you advise?
Description
Version used: androidx.paging:paging-*:3.0.0-alpha01
Devices/Android versions reproduced on: Samsung S-10
I am using PositionalDataSource in my code and when i request to loadAroud() a specific index, it loads sequentially from last loaded index till requested index instead of jumping and loading around requested index.
Its was working on stable version : androidx.paging:paging:2.1.2