|Composite background-color animation
||xidachen@ resolved a few issues during this sprint.
||The first one is completely decouple paint and compositing, which is shown in the above diagram. Specifically, we were passing a boolean from paint to the compositing stage and that could introduce technical debt in the future. Now we no longer require that boolean.
||The second issue is to handle non-visible animations, which can happen in many cases such as an animation on a zero-sized element. There are a lot of discussions here, and we eventually decided that it is OK to composite these no-op background-color animations. The problem is fixed by this CL. Fixing this issue also helped resolving an existing CSS paint worklet bug which no-op animation.
||The third issue is handling non-replace keyframes. As shown in the above code snippets, we should not look at the composite mode of the animation, but rather look at the composite mode of each keyframe. This is resolved by this CL.
||Capability Delegation moved to WICG
||mustaq@ made awesome progress during this sprint, which includes
action plans</a> with Payments team (thanks to smcgruer@).</td></td>
<td><td>Secured public approval from <a
and thumbs-up from <a
<td><td>Moved the proposal to <a
<td><td>Updated/deprecated all related public threads/docs: HTML <a
href="https://github.com/whatwg/html/issues/4364">#4364</a>. Crbugs: <a
href="https://crbug.com/931966">931966</a>. Docs and repos: <a
|Click as PointerEvent
||liviutinta@ and mustaq@ collaborated on this work.
<td><td>Identified a regression in older <a
software and APIs</a> which is widely used related to fractional coordinates
<td><td>Disabled the <a
experiment</a>. Kept <a href="https://crbug.com/1192449">engaged</a> with
developers until the problem is fully resolved.</td></td>
<td><td>Reached the <a
decision</a> about what to ship: click/auxclick/contextmenu as pointer
events but with integer coordinates.</td></td>
<td><td>Closed a 5-yr old debate in the <a