| Composite multiple transformations |
| ![image](https://lh3.googleusercontent.com/EQb-Syn7LREAM34ygxbX7L1pyekr1XQeqvfoCv0Poe8jHCTs2dHv9mOzYksuZnT2iALiRptpqTxNAm_4BoeMVSYmzOyQlxpgYNdBA0IrPPG--eKJ4HDVl1TrWAshwt8eCdA1fQP57w) |
| kevers@ landed a CL to composite multiple transformations. |
| Background |
<td><td>CSS has 4 transformation properties: translate, scale, rotate and
transform.</td></td>
<td><td>Previously, we could only composite a single
transformation.</td></td>
| Challenges |
<td><td>Compositor only know about transform, and the others were
converted.</td></td>
<td><td>Ordering is important</td></td>
<td><td>WorkletAnimations tick later than the rest to allow time for worklet
code to run.</td></td>
| Solution |
<td><td>Expand set of target properties in CC</td></td>
<td><td>ScopedCompoundTransformResolver</td></td>
| Capability Delegation |
| mustaq@ finalized Q3-Q4 shipping plan: |
<td><td>origin trial at M94</td></td>
<td><td>ship at M96 without PaymentRequest changes, and</td></td>
<td><td>ship PaymentRequest changes after holidays.</td></td>
<td><td>We considered possible <a
href="https://github.com/w3ctag/design-reviews/issues/655">TAG</a> delays,
no-breakage during holiday shopping, and motivating Stripe changes. Thanks
to smcgruer@ and jyasskin@.</td></td>
| Android Elastic Overscroll |
| ![image](https://lh5.googleusercontent.com/FRDw2s9Fo_jgXugwAG_xmw4TiAGL62LmQDjVLyo2ZWa5Z5XxZfGqTofo0NYPmKDQmSDupTmkNt58QbnpZeBNYF3nVQiOb68XUK-LNq6iCjIm3Ab2-hZTMPYv-2fS05T-tqaqqo5uOQ) |
| flackr@ has landed all patches for elastic overscroll, which includes: |
<td><td>Transform overscroll stretch</td></td>
<td><td>Pixel shader stretch</td></td>
<td><td>Disable glow when stretch is enabled</td></td>
<td><td>Disable stretch on webview when native stretch is used</td></td>
<td><td>Disable stretch in non-scrollable directions</td></td>
<td><td>Only enable stretch on Android 12 or later</td></td>
| ![image](https://lh3.googleusercontent.com/05E_HxvKHpAv6SpaGfMb_HYRcgow4USMOtoMnLe8-bn6K9TlBnpZBbwhpw4R_wZFZg_HI9iArKEvMAeeuqpI8NC7XdxCRfRdodF-BLnEduUv636G9nZYCPiCqxjkddQUQLbnYaTsSg) ![image](https://lh3.googleusercontent.com/0scdtf1EyP1uWp8seL2Y3fYmoUTAgrGdZUwyY9UWqflcC2O1BUAkZt0uKZ0L5Mk08oThn8CgYrZJOtsQaeduhapwBuBNFUbQHriV1OsvWu1H8aTP6KVu24XNRGYMe8ig3SKBNJyp2Q) |
| Memory.GPU.PrivateMemoryFootprint and Memory.GPU.PeakMemoryUsage2.Scroll |
| The preliminary finch result for “Android Elastic Overscroll” is shown above. The only substantial difference seemed to be GPU memory usage: |
<td><td>Roughly 10% increase in Memory.GPU.PeakMemoryUsage2.Scroll</td></td>
<td><td>Slightly increase in Memory.Gpu.PrivateMemoryFootprint</td></td>
|