diff options
Diffstat (limited to 'chromium/docs/website/site/teams')
133 files changed, 0 insertions, 19842 deletions
diff --git a/chromium/docs/website/site/teams/animations/OWNERS b/chromium/docs/website/site/teams/animations/OWNERS deleted file mode 100644 index a6e70177e10..00000000000 --- a/chromium/docs/website/site/teams/animations/OWNERS +++ /dev/null @@ -1,2 +0,0 @@ -flackr@chromium.org -kevers@chromium.org diff --git a/chromium/docs/website/site/teams/animations/animation-objectives/index.md b/chromium/docs/website/site/teams/animations/animation-objectives/index.md deleted file mode 100644 index e9818140fab..00000000000 --- a/chromium/docs/website/site/teams/animations/animation-objectives/index.md +++ /dev/null @@ -1,261 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -page_name: animation-objectives -title: Animation Objectives ---- - -We define and track progress against our goals using -["OKRs"](https://www.gv.com/lib/how-google-sets-goals-objectives-and-key-results-okrs) -(Objectives and Key Results). Here are most of the OKRs for the animations team. -Note that these are **intentionally aspirational** and so we will be happy if we -deliver 60%-70% of them. - -OKRs are given priority orderings, where P0 is the highest priority and P4 is -the lowest. Normally (for our team) OKRs exists between P1 and P3. - -If you have any questions about our OKRs, please email our [mailing -list](/teams/animations). - -**2020 Q1** - -Modernize animations programming by shipping Web Animations v1 in M82 -*#Implement* - -P1 - Sign off on spec and I2S - -P1 - Close all P1 Blockers - -P2 - Triage and address P2’s - -P2 - Address WPT gaps to improve interop *#Velocity* - -Enable richer, jank-free web experiences *#Optimize* - -P1 - Ship Off-Thread Paint Worklet - -P2 - Validate and Promote PaintWorklet - -P2 - Drive consensus on GroupEffect standardization *#Next* - -Improve the scrolling experience *#Next* - -P1 - Scroll Timeline: Implement and prep for Q2 Origin Trial - -P2 - Launch Virtual Scroller and supporting primitives - -Team Velocity *#Velocity* - -P1 - Reduce [bug count](https://bit.ly/2RbjS1C) by 15% - -\[Measure is: 1 - (bugs_at_end_of_quarter / (bugs_at_start_of_quarter + -bugs_opened_during_quarter))\] - -P1 - Iterate on improving throughput metric - -**2019 Q4** - -Implement the existing standards 0.75 - -P1 - Implement Web Animations v1 in Q1 (M82) 0.6 - -P2 - Stabilize Scroll Snap 0.9 - -Explore and define the next generation of animation 0.75 - -P1 - Animation Worklet: Ship updated AW in M81 0.4 - -P1 - Scroll Timeline: Validate Spec through Origin Trial 0.5 - -P2 - Investigate Virtual Scroller, with community+partners 1.0 - -P2 - Drive consensus on GroupEffect standardization 1.0 - -Optimize Animations 0.85 - -P1 - Ship Viz Hit Testing V2 1.0 - -P1 - Ship Off-Thread Paint Worklet 0.7 - -P2 - Validate and Promote PaintWorklet 0.0 - -Team Velocity 0.3 - -P1 - Reduce [bug count](https://bit.ly/2RbjS1C) by 25% 0.2 - -Measure is: 1 - (bugs_at_end_of_quarter / (bugs_at_start_of_quarter + -bugs_opened_during_quarter)) - -P1 - Land “Throughput” metric, and validate w community 0.4 - -**2019 Q3** - -**Implement the existing standards 0.71** - -P1 - Implement Web Animations v1 by M79 0.7 - -P2 - (Prepare to) Land Web Animations v1 0.7 - -P2 - Hand Off Scroll Snap 0.75 - -P2 - Improve WPT Compliance (fix the tests) 0.7 - -**Explore and define the next generation of animation** 0.51 - -P1 - Animation Worklet: Spec Approved (and shipped!) 0.3 - -P2 - Scroll Timeline: Specification+Feedback 0.3 - -P2 - Input For Workers/Worklets - design use case for input to animation -worklets 0.5 - -P2 - Group Effect: Publish Explainer 1.0 - -**Optimize Animations 0.75** - -P1 - Land Viz Hit Testing 0.8 - -P1 - Off-Thread Paint Worklet: enable custom property animation 0.7 - -**Team Velocity 0.75** - -P1 - Reduce [bug count](https://bit.ly/2RbjS1C) 25% 1.0 - -*Measure is: 1 - (bugs_at_end_of_quarter / (bugs_at_start_of_quarter + bugs_opened_during_quarter)).* - -P1 - Land top-level/user-facing metric for animation performance 0.7 - -P2 - End to end cc/integration testing 0.0 - -P2 - Animations Tracing - Define plan for exposing the complexity of animation -via dev tools or tracing 0.0 - -P2 - Animations Metrics Design Doc published, reviewed 0.7 - -**2019 Q2** - -**Implement the existing standards 0.7** - -P1 - Implement key missing parts of the Web Animations standard. 0.5 - -P1 - Ensure spec conformance and interoperability by driving down WPT test -failures 1.0 - -P2 - Land Scroll Snap 0.7 - -P2 - PaintWorklet: Implement Lottie (as a demo) off-thread using paintworklet. -0.6 - -P2 - PaintWorklet: Enable worklets on cc 0.6 - -**Explore and define the next generation of animation** 0.78 - -P1 - Ship Animation Worklet 0.8 - -P2 - Invest in partnerships/relationships with standards and browser partners -0.9 - -P2 - Continue to invest in adding value to Animation Worklet 0.8 - -**Optimize Animations** 0.38 - -P1 - Enable Viz layer based hit testing 0.3 - -P1 - Measure animations performance 0.7 - -P2 - Remove additional property nodes / compositing overhead due to animation -ElementId tracking 0.2 - -**Team Velocity** 0.63 - -P1 - Reduce [bug count](https://bit.ly/2RbjS1C) 25% 1.0 - -*Measure is: 1 - (bugs_at_end_of_quarter / (bugs_at_start_of_quarter + bugs_opened_during_quarter)).* - -*End of quarter result: (134 / (128 + 55)) ~= 27%* - -P1 - BGPT causes no P1 animation regressions 1.0 - -P1 - Animations Metrics Design Doc published, reviewed 0.4 - -P2 - Start animations based on ElementId existence 0.1 - -P3 - End to end threaded rendering unit test support 0.0 - -**2019 Q1** - -**Correct animations and effects** 1.00 - -P1 - Reduce [bug count](https://bit.ly/2RbjS1C) 15% 1.0 - -*Measure is: 1 - (bugs_at_end_of_quarter / (bugs_at_start_of_quarter + bugs_opened_during_quarter)).* -*End of quarter result: (128 / (134 + 49)) ~= 30%* - -P1 - Fix 5 of the top 20 animations [interop issues](https://bit.ly/2sFImqb) 1.0 - -*End of quarter result: Closed 16 Hotlist-Interop bugs incl shipping -prefers-reduced-motion + CSS transition events.* - -**Improve animations code health** 0.2 - -P1 - Begin consolidation of -[blink::WorkletAnimation](https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/animationworklet/worklet_animation.h?l=37&rcl=a4f73cdaeddaee4969614ce2832ea8b997514242) -and -[blink::Animation](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/animation/animation.h?l=64&rcl=a4f73cdaeddaee4969614ce2832ea8b997514242). -0.1 - -P2 - Make a blink driven cc integration/unit test possible. 0.0 - -P2 - Consolidate transform interpolation between blink and cc. 0.5 - -*End of quarter result: Feasibility investigated + prototype attempted, but -sidelined in favour of AnimationWorklet work.* - -P2 - Refactor code around [p](goog_624119910)[er-property -cc::Animations](http://crbug.com/900241). 0.3 - -**Smooth scrolling on all (i.e. incl/ low end) devices** 0.82 - -P1 - Ship Compositor Touch Action 1.0 - -*End of quarter result: Shipped in M75!* - -P1 - Viz Hit Testing - continue to scale up Finch trial 0.9 - -*End of quarter result: 100% on canary/dev, 50% Finch trial on beta, -improvements in performance + correctness* - -P2 - Implement paint-calculated Non-Fast Scrollable Regions 0.3 - -**Richer animation effects competitive with native experiences** 0.50 - -P1 - Ship first version of AnimationWorklet 0.8 - -*End of quarter result: almost all MVP features landed, TAG review requested, -not published as FPWD yet.* - -P1 - Ship ScrollTimeline for AnimationWorklet 0.3 - -P1 - Improve overscroll-behavior implementation 0.3 - -P1 - [Off-Thread Paint Worklet](/teams/animations/paint-worklet): basic version -behind flag in tip-of-tree 0.8 - -*End of quarter result: Two CLs still in flight, but with those in a (partially) -working prototype exists behind --enable-blink-features=OffMainThreadCSSPaint* - -P2 - Drive AnimationWorklet adoption 0.0 - -P2 - GroupEffect Implementation 0.0 - -P2 - Support snap points 0.8 - -*End of quarter result: scroll-snap-stop implemented to support AMP, some bugs -remain* - -**Easier performant effects** 0.00 - -P3 - Educate developers on when their animations are slow and why 0.0
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/animation-worklet/index.md b/chromium/docs/website/site/teams/animations/animation-worklet/index.md deleted file mode 100644 index 4e168500f8e..00000000000 --- a/chromium/docs/website/site/teams/animations/animation-worklet/index.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -page_name: animation-worklet -title: Animation Worklet ---- - -Animation Worklet is a new primitive that provides extensibility for web -animations and enables high performance scripted animations that can run on -dedicated thread. The feature is developed as part of the [CSS Houdini task -force](https://github.com/w3c/css-houdini-drafts/wiki). - -The Animation Worklet API provides a method to create scripted animations that -control a set of animation effects. These animations are executed inside an -isolated execution environment, *worklet* which makes it possible for browser to -run such animations in their own dedicated thread to provide a degree of -performance isolation from main thread. Worklet animations may be created and -controlled via Web Animations API. Animation Worklet combined with other new -features such as [ScrollTimeline](https://wicg.github.io/scroll-animations/), -[Input in -Worklets](https://github.com/w3c/css-houdini-drafts/issues/834#issuecomment-470579488), -can allow many currently interactive main-thread rAF-based animations to move -off main thread which improve smoothness. - - [Specification](https://drafts.css-houdini.org/css-animationworklet/) - - [Explainer](https://github.com/w3c/css-houdini-drafts/blob/master/css-animationworklet/README.md) - - [Design Principles and - Goals](https://github.com/w3c/css-houdini-drafts/blob/master/css-animationworklet/principles.md) - - Tests: - <https://github.com/web-platform-tests/wpt/tree/master/animation-worklet> - - Example codes [1](https://googlechromelabs.github.io/houdini-samples/), - [2](https://aw-playground.glitch.me/), - [3](https://houdini.glitch.me/animation) - - [Blink Design - Document](https://docs.google.com/document/d/1MdpvGtnK_A2kTzLeTd07NUevMON2WBRn5wirxWEFd2w/edit?usp=sharing) - -Current Status - -<table> -<tr> -<td><b> Milestone</b></td> -<td><b> Status </b></td> -<td><b> Key features</b></td> -</tr> -<tr> -<td> Animation Worklet Prototype</td> -<td>Done</td> -<td> Scripted custom animation, single effect, only fast properties, off main-thread (using compositor thread).</td> -</tr> -<tr> -<td> Animation Worklet <a href="https://developers.google.com/web/updates/2018/10/animation-worklet">Origin Trial</a></td> -<td>In progress (<a href="https://docs.google.com/forms/d/e/1FAIpQLSfO0_ptFl8r8G0UFhT0xhV17eabG-erUWBDiKSRDTqEZ_9ULQ/viewform">signup</a>)</td> -<td> Scroll input (via ScrollTimeline), basic web-animation controls (play/cancel), move to dedicated thread, optimized performance.</td> -</tr> -<tr> -<td> Animation Worklet V1 - MVP</td> -<td>Scheduled for M75</td> -<td> Animate all properties (slow path ones runs in sync with main thread), sophisticated scheduling so we do not block compositor thread, improved scroll timeline integration. </td> -</tr> -<tr> -<td>Animation Worklet V2 </td> -<td>TBD</td> -<td> Pointer input via Events, multi-input animation, support GroupEffects, improved integration with Paint Worklet.</td> -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/animations-documentation-throughput-metrics-code-health-capability-delegation-user-input-security-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/animations-documentation-throughput-metrics-code-health-capability-delegation-user-input-security-and-more/index.md deleted file mode 100644 index ef4265de10c..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/animations-documentation-throughput-metrics-code-health-capability-delegation-user-input-security-and-more/index.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: animations-documentation-throughput-metrics-code-health-capability-delegation-user-input-security-and-more -title: Animations Documentation, Throughput Metrics, Code Health, Capability Delegation, - User Input Security and more! ---- - -<table> -<tr> - -<td>July 2020</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/WRVW9VUhxNCsev-DZjUkmjGKVA5J4bJnm3JRhenzeZq7Pgfod74bwJpYLHF68ZuglJn38aoXqe2r-mkLdxk0y196l2NCsIfKIwRDhorwPGv5YbU5ZJgyQgGcup7X84_9vIx3yeQ8lA" height=432 width=561.3834586466165></td></td> - -<td><td>Animations Documentation</td></td> - -<td><td>kevers@ has made a lot of progress updating documentations in <a href="https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/core/animation/README.md">README.md</a>. Specifically,</td></td> - - <td><td>Landed 5 CLs with roughly 1300 lines of documentation - added.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/c25Dc0nGruNseouHuux9h-1LZiVy0K2G8cGHUGscwbC_7pz3bbvFIqu6k03395tpNJ35MsSg9ppQyA6UNCrptuzTg7v6HcHMmMqAdx9hOZKu3fCyxukWibg19WENJUms0CwlxcKosQ" height=175 width=282></td></td> - -<td><td>Throughput Metrics</td></td> - -<td><td>xidachen@ started discussion on adjusting throughput reporting interval. They collected data with different reporting intervals and shown in the above graph.</td></td> - - <td><td>A lot of details are missed when the interval is large such as 5 - seconds</td></td> - - <td><td>The graph can be very noisy if the interval is too small such as 0.2 - second.</td></td> - - <td><td>A 1-second interval is likely a good choice.</td></td> - -<td><td>Bug Triage</td></td> - -<td><td>Our entire team has been working to formalize the bug triaging process. We now have a great <a href="https://docs.google.com/document/d/1II4W6ymxKNc8mxBAxwHjWIhzL5PPO4AtSrorzgiU3tM/edit#heading=h.3ma2fxg0g60f">doc</a> that describes the triage process and our un-triaged bug is coming to 0.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Capability Delegation</td></td> - -<td><td>mustaq@ has completed the first draft of <a href="https://docs.google.com/document/d/1IYN0mVy7yi4Afnm2Y0uda0JH8L2KwLgaBqsMVLMYXtk/edit">Capability Delegation API</a>, and restarted the <a href="https://github.com/w3c/payment-request/issues/917">payment spec issue</a> discussion.</td></td> - -<td><td>User Input Security</td></td> - -<td><td>liviutinta@ started finch experiments for Browser Verified <a href="https://critique-ng.corp.google.com/cl/324039223">Keyboard</a>/<a href="https://critique-ng.corp.google.com/cl/324039272">Mouse</a> Activation Trigger.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Scroll Unification</td></td> - -<td><td>lanwei@ improved many web tests by replacing eventsender with gpuBenchmarking.smoothScrollByXY. Currently there are 2 out of 42 remaining.</td></td> - -<td><td>WebDriver Actions API Spec</td></td> - -<td><td>lanwei@ added webdriver <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2316405">wpt tests</a>, and <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2324972">implemented</a> the wheel input source in Chromedriver.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Code Health</td></td> - -<td><td>During the no-meetings week, our team made a lot of contributions to code health.</td></td> - - <td><td>The team landed 52 CLs and started a design doc (summary <a - href="https://docs.google.com/document/d/1hk5N4NH-kYhEqyz1glnVGvWgT9NEMlMtaC4AJWE5CfA/edit#heading=h.lowhafniytq6">here</a>).</td></td> - - <td><td>lanwei@ removed experimental delegation code for user - activation.</td></td> - - <td><td>kevers@ landed <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2313157">patch</a> - to fix flaky layout tests.</td></td> - - <td><td>kevers@ also <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2310969">addressed</a> - animation/style regressions due to recent refactoring.</td></td> - - <td><td>liviutinta@ fixed a <a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1076078">bug</a> - to ensure that when right clicking on a mis-spelled word and contextmenu - event prevented, the mis-spelled word should not be highlighted.</td></td> - - <td><td>liviutinta@ also <a - href="https://critique-ng.corp.google.com/cl/323644938">started</a> - experimenta with Click as Pointer Event.</td></td> - - <td><td>Everybody joined in to create <a - href="https://docs.google.com/document/d/1PCz35DkhYHT8zXJoKQl--WhQZpimJRyNlfEWSSjpUJ0/edit#">Interactions - RTF</a> (Read this first)</td></td> - -<td><td>Azimuth/Altitude for Pointer Events</td></td> - -<td><td><a href="https://patrickhlauke.github.io/touch/pen-tracker/index.html?azimuth"><img alt="image" src="https://lh5.googleusercontent.com/4UlT7gRKaxiEjFSMUNpgY83bcFVmaS2YqhPN2mnU5RxMJ2hSrjwi8Ky1ZKJLa5iVm2h8cvVbaLT9vI8WgL9Mw3PWQ_6NqFVL9O_HkKQZlzlNDffgv8kGPUDzmcuxI3ehHhuIoyKguw" height=155 width=282></a></td></td> - -<td><td>liviutinta@ has <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2165457">implemented</a> this feature.</td></td> - - <td><td>Sent <a - href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZRI-7X_4GwM">Intent - to Ship</a>.</td></td> - - <td><td>Sent request for official position to <a - href="https://github.com/mozilla/standards-positions/issues/411">Gecko</a> - and <a - href="https://lists.webkit.org/pipermail/webkit-dev/2020-July/031313.html">WebKit</a>.</td></td> - - <td><td>Sent <a - href="https://github.com/w3ctag/design-reviews/issues/537">TAG Review</a> - request.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | July 2020</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/april-2019-volume-ii/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/april-2019-volume-ii/index.md deleted file mode 100644 index 053aa48468f..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/april-2019-volume-ii/index.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: april-2019-volume-ii -title: April 2019, Volume II ---- - -<table> -<tr> - -<td>April 2019, Volume II</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh3.googleusercontent.com/ijzv1FoeaoQqmakoVD-22LcixO6d-o_mKKFTGwYa3JKIFBecPJtDZjHLnSTEBFBCVdcQxHg2PUAToBolahoOUz0-DmLVOi1rZjT_mksxuZA20sPrkULJVO7H3SeYSyRxA_4uIt2x" height=367 width=596></td> - -<td>One DIV, "7 lines" of script. Done! (Animation from LottieFiles: <a href="https://lottiefiles.com/433-checked-done">https://lottiefiles.com/433-checked-done</a>)</td> - -<td>Lottie in a PaintWorklet</td> - -<td><a href="https://airbnb.design/lottie/">Lottie</a> is a popular framework from AirBnB that renders After Effects animations, allowing designers to create rich complex animations. Its <a href="https://github.com/airbnb/lottie-web">web implementation</a>, however, is not very performant. This sprint, Rob Flack (flackr@) prototyped a port of the Lottie renderer to a PaintWorklet - driven by a standard Web Animation for input progress. Not only does this bring richer devtools integration, but with the ongoing <a href="https://docs.google.com/document/d/1USTH2Vd4D2tALsvZvy4B2aWotKWjkCYP5m0g7b90RAU/edit?ts=5bb772e1#heading=h.2zu1g67jbavu">Off-Thread PaintWorklet</a> effort we will soon be able to render Lottie animations performance-isolated from the main thread!</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/U9zrtaB0y4-AB2jh3ZIpZBM4h6Syh5L4ZqasUgSLmdez7iBL0r4TkUvBJczJGh7usdsZaoxdrPtLE2jMuYDa-c103TacHIZ2ghex6xyAaF9dhkTCX8dIsjTQu2iYdtcc1wD6Uivp" height=128 width=283></td></td> - -<td><td>Viz Hit-Testing - Linux Performance</td></td> - -<td><td>Xianda (sunxd@) sadly left the team this sprint, but not before he followed through on</td></td> -<td><td>his promise to bring the fast-path rate on Linux up to the same standard as other platforms.</td></td> -<td><td>The goal was to have 80% of hittests use the</td></td> -<td><td>fast path - Xianda overdelivered as usual with a fantastic 93% fast-path rate!</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/DYE-WxgyKi-r-aZ-7PNd8z9cWxufESkHmzVcqugM-wHBKU5pUjXqz2aT4v7XHQaDWXiRa6ZK0eqJKsQXkhskzkksQGQZ-yR_mmVnVFHU2IjEGiAqt-N9TrVpcL-8sZWFtxjmneD6" height=128 width=283></td></td> - -<td><td>Stateful Animation Worklet</td></td> - -<td><td><a href="https://drafts.css-houdini.org/css-animationworklet-1/#stateful-animator-desc">Stateful Animators</a> enable developers to keep local state in their Animation Worklet to perform richer effects (e.g. velocity based animations). Yi (yigu@) has lead the spec work on these, and this sprint he landed the corresponding code.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>BlinkOn has come - and gone!</td></td> - -<td><td>Two thirds of the Animations team decamped to Toronto for BlinkOn, spending two days listening to (and giving) talks, syncing with colleagues from around the world, and getting to know some of our new collaborators from Microsoft. Both Stephen's <a href="https://docs.google.com/presentation/u/1/d/1WrzDN_PiKBfOVUrrbOV8gHQO-ODN0gdCpWE4xMYv29c/edit?usp=drive_web&ouid=105513761242358226829">Off Main Thread CSS Paint</a> and Majid's <a href="https://docs.google.com/presentation/d/1BCEbLCg-o_Ko65byel5QGnO7Cwf5aPZPjqnnMNbbA5E/edit">Event Delegation to Worker and Worklets</a> talks were well attended and well received.</td></td> - -<td><td>Web Animations - Moar Interop</td></td> - -<td><td>Kevin (kevers@) has been hard at work fixing bugs in our Web Animations implementation - over 50% of the <a href="http://crbug.com/772407">known WPT failures</a> are now fixed! This sprint has seen a focus on timing issues, with plenty of nasty floating-point boundary case bugs to squish!</td></td> - -<td></tr></td> -<td></table></td> - -<td><img alt="image" src="https://lh3.googleusercontent.com/5vUZFWkmaAi__ErtI9EwMBbnBx7aRTDa74k33Ya0BQ6hLcTQU5TGX4nB6OzlJWXcdY17QGEiZi8ADo5xXF5o0EtnCxx_Naw9Fj0dGMIT8GUvCwoM3G7DLMpvzOA_7XuBnYX_NgJz" height=286 width=353></td> - -<td>Scroll Snap - supporting AMP</td> - -<td>AMP team are excited to use scroll snap for their image carousel, but need paginated behavior. We previously implemented the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-snap-stop">scroll-snap-stop</a> feature to enable this. This sprint they <a href="http://crbug.com/823998#c15">reported a bug</a> where they were able to 'break' the snapping and cause their content to go flying! Majid leapt into action: <a href="https://drive.google.com/file/d/1Jlb1IlQ66-JbCi1lBn-L0zhDBoiZF_Qb/view">reproducing</a>, diagnosing, and <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1572286">fixing</a> the bug. This should clear the way for AMP to roll out scroll snap, and we are excitedly <a href="https://www.chromestatus.com/metrics/css/timeline/popularity/499">watching our metrics</a>.</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | April 2019, Volume II</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/april-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/april-2019/index.md deleted file mode 100644 index ccbc4187e16..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/april-2019/index.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: april-2019 -title: April 2019 ---- - -<table> -<tr> - -<td>APRIL 2019</td> - -<td>Chrome Animations Highlights</td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh4.googleusercontent.com/e4d0yeYg2osuLzXs4PZ-Mocx7ILQEqgXJKvI2K5Lopqki3LxuCKFywsPcH-9JDiVOYCB4kF2I_zqkY3mGDDjBrPibOst19SBWkmVM3a0DagRZYZgm6UB5jz0k-PujynP5S8w1YS1" height=359 width=462></td> - -<td>It looks the same as you would see in Chrome Stable, but it's totally running off-thread. We promise!</td> - -<td>Off-Main Paint Worklet</td> - -<td>Work continues on our efforts to take Paint Worklets off the main thread and run them from the compositor. With the <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1525160">blink → cc communication</a> and the worklet thread<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1531153"> dispatching logic</a> landed, we are able to render a Paint Worklet off the main thread for the first time! There's still some way to go, but this is a vital step towards smoothly animating Paint Worklets.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/P0KFfWlfC7wj43S6F4IlkfQ5poIbTEFbtIxQWxRT-CEpYFR-0A-JfdpZzkE01Qw3I_TiiNB8KngKzhPQM-DCzweaW-escsvEDD3PMXnUFJxnQXv-a3ajsMTP1nDv0BukWpkEufeL" height=166 width=227></td></td> - -<td><td>Scroll Snap</td></td> - -<td><td>With sunyunjia@ sadly leaving the team, girard@ took over finishing up the work on scroll snap. Initial ramp-up went well; discovered <a href="http://crbug.com/944184">an issue</a> with scrollbar arrow buttons and scroll snap, file a <a href="https://github.com/w3c/csswg-drafts/issues/3752">spec bug</a> and <a href="https://github.com/w3c/csswg-drafts/commit/09e040f05e12bb4c303d5839e0ceee3f6bf58c67">patched the spec</a>, and Gene is now working on <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1534988">a fix</a> for the Chrome implementation.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/qTkpiW1DKDbFNM12EZdAmQ7OgdOCE8ZQPZtvqIb6Za4WC-mWlNDCmaQ3zc5Bdd1R2uEaD-dvClmRRVblyw5ChI_lRLJ3uLR6GhDp-wAYSc48ziHdOSY8F5MqRzFAF2njgYJycyle" height=172 width=172></td></td> - -<td><td>Shipping more of Web Animations!</td></td> - -<td><td>Long overdue, some more parts of the Web Animations API are going to be shipping soon - <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/1EQKF7il48U">AnimationEffect and (some of) KeyframeEffect</a>, and the <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/UMxgGkxhdCo">Animation constructor</a>. </td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>BlinkOn is coming!</td></td> - -<td><td>Our team has two presentations planned for BlinkOn 10. We also have planned a collaboration session with Microsoft engineers around animations and related topics.</td></td> - -<td><td>BlinkGenPropertyTrees</td></td> - -<td><td>We continue to support the paint-team's project to move property tree generation to Blink instead of the compositor. This has required significant changes in how element ids are treated in composited animations, and has taught us about where our tests fail to catch regressions.</td></td> - -<td></tr></td> -<td></table></td> - -<td><img alt="image" src="https://lh4.googleusercontent.com/SMf7AoFH-HS2DqUKTgH4zFTnynOaoDXioRMPyeFiO-I5bJFrT2X1NiaB6YeetcUQ0BOtLeIjwNGOWF9EkzBliu4oY1Nc6C3jZdY6XN_gVMQHA9JK9SJ3u_c375BOAZPzXimTsJKn" height=92 width=596></td> - -<td>Viz Hit-Testing Surface Layer</td> - -<td>Tackling blocking issues preventing promotion of new version to 100% of Beta users. LTHI::BuildHitTestData was reduced from ~400ms to 0.3ms in a pathological case (6000+ layers on a page), and a BlinkGenPropertyTrees masking bug was resolved. Working on tackling low fast-path rate on Linux; multiple fixes in progress which are expected to bring it in line with other platforms.</td> - -<td><img alt="image" src="https://lh5.googleusercontent.com/BGpN4LK3CTdcACVHZk4Obno9IbfAq1oSy2a3-f-uUuEwkn0_6bmAigxmZgukpJtcPPZvPI2EnKSdcgBiV4yxBhKyCwvVpw0vkhJI8An_fLZS89nZfktPFRl2DErvnik2NGYucPPZ" height=127 width=283></td> - -<td>Animation Worklet - the road to shipping</td> - -<td>Animation Worklet continues to make progress on its road to shipping. Notable features this sprint included finally making fully-asynchronous Animation Worklets as <a href="https://drive.google.com/file/d/1jF3bQlFKkbv4Sz7Q6r2rPDGxewXdw0Zl/view">buttery smooth and jank free</a> as they deserve to be (multiple weeks of work, well done kevers@ and flackr@!), <a href="https://crrev.com/386583bbe5a57761ff36bf925066f281b57d9d26">proper i18 support</a> for naming worklets, and progressing on <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1488312">support for stateful animations</a>. The Animation Worklet Origin Trial has been <a href="https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/AZ-PYPMS7EA/Fo76_FuFBAAJ">extended until M75</a> to gather more data as AMP rolls out its AnimationWorklet-based solution to all users!</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | April 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/april-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/april-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more/index.md deleted file mode 100644 index 945e77c675f..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/april-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more/index.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: april-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more -title: April 2020 - Web Animations, Scroll-linked Animations, Throughput Metrics, - Performant Meet, Hackathon and more! ---- - -<table> -<tr> - -<td>April 2020</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh5.googleusercontent.com/Asd0BAjki50O1Jd36jqK8YY87ftxZs4-UTyjagI2h_J-YXt_TCDKwOVcib-lSWoPZzyqhL9DmvaipvwzNVLkpwxr3acGYHXxUbY2m3xeNtuBRmz70cD3ii11lX7NceLqahtL_5Uf" height=244 width=317></td> - -<td>Celebrate shipping Web Animation API<a href="https://jsbin.com/weqamosare/1/edit?js,output"> using the API</a></td> - -<td><table></td> -<td><tr></td> - -<td><td colspan=2>Complete Web Animation API in M84!</td></td> - -<td><td colspan=2>The <a href="https://drafts.csswg.org/web-animations-1/">API</a> provides developers with a powerful way to create and control animations on the web including existing CSS Animations and Transitions. After years of effort by the Animation team, Kevin (kevers@) sent out the final <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Wu4yPMznUw0">Intent to Ship</a> and turned on the feature <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2161345">by default</a> in M84! Here is a <a href="https://docs.google.com/document/d/1sWAEytrZDxQWnnqozMSzI2lHvIJ0kF3dzgy9Q1PbYjE/edit">showcase</a> of all the new features. This was a collaborative effort with other browsers which is why the same rich API would be available in <a href="https://webkit.org/blog/10266/web-animations-in-safari-13-1/">Safari</a> and <a href="https://hacks.mozilla.org/2020/04/firefox-75-ambitions-for-april/">Firefox</a> as well. There is still <a href="https://github.com/w3c/csswg-drafts/labels/web-animations-2">room for improvement</a> but let’s take some time to celebrate this big milestone in animations! Thanks to the dozens of developers across five+ organizations (Chrome, Microsoft, Firefox, Igalia, Opera etc.) who have contributed to this! </td></td> - -<td><td colspan=2><img alt="image" src="https://lh5.googleusercontent.com/LqXcIohcW0fR8okipubge1E96AcHRzz3xbiq4OubalRtluI5uHTUXSmkFMPNNqy2tLIkW4sRA2sVT8Ugg_wxNNCxvLXMc7wVyhWzcv0tlcNba_EhRbQJKJlTMj_iGoeBzR0z28Ac" height=230 width=459></td></td> - -<td><td colspan=2>A long journey of shipping Web Animation API</td></td> - -<td></tr></td> -<td><tr></td> -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/YcuCWIgXIi7sSxu3o_nP5sEfCPm9JC3eFAe4-xHZ3KC3UXV5FkXsOZJqUUdZo7X9M8TcWU_CIC-ZhOZZjxiIgvZqI0jA6deOklMCJ3BgMLKhB7HBS0rw5g-aSp0Hj3_mWR6INTTp" height=40 width=273></td></td> - -<td><td>Green Volume Meter</td></td> - -<td><td>Google Meet usage has surged significantly, <a href="https://www.theverge.com/2020/4/28/21240434/google-meet-three-million-users-per-day-pichai-earnings">adding 3M users per day</a>. We’ve noticed that the green volume meter was unexpectedly re-rastered during animation, causing significant CPU usage. Rob (flackr@) came to the rescue and <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1074055">fixed</a> the issue by preserving the raster scale for animations with will-change: transform. This avoids unnecessary and expensive rasterization, and should greatly reduce CPU/power usage. </td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/xs4GcGU_ey6XxTBPJndhQgyTwZTMiNFuTX3bOTnxgImBUZGsXFIvlhTMbv-x28U93zhNiZP3TC168i_8MloXC2zT3iZxd-zWw6CLHSVYfijGqMQCHLqAwo5fNp6bT2sJes9VsL6o" height=152 width=280></td></td> - -<td><td>Better Frame Throughput Metrics</td></td> - -<td><td>Frame Throughput is severely impacted during initial page load, often dominating the metric. Xida (xidachen@) modified the sampling logic to measure from 5s to 10s, resulting in more accurate and meaningful values. One site’s dropped frames moved from 84% to 15% at 50th percentile and 99% to 75% at the 95th percentile.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Scroll-linked Animations</td></td> - -<td><td colspan=2>It’s been a productive month for scroll-linked animations. Majid (majidvp@) and Yi (yigu@) wrote a full-fledged <a href="https://github.com/w3c/csswg-drafts/blob/master/scroll-animations-1/EXPLAINER.md">explainer</a> for scroll timeline discussing many of the design trade-offs and showcasing multiple examples. Olga (<a href="mailto:gerchiko@microsoft.com">gerchiko@microsoft.com</a>) landed the spec change and implementation for using “zero” as initial start time for scroll-linked animation. Majid landed implementation for <a href="https://github.com/w3c/csswg-drafts/issues/4337">element-based scroll offset</a> and Yi added full support for running scroll-linked animations on the compositor. We now have enough implemented to see the <a href="https://majido.github.io/scroll-timeline/demo/parallax/">demo</a> we built using polyfill now works natively in Chrome Canary with the flag enable-experimental-web-platform-features.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/DrrQOx_U_ImfrYijLwAGdIm_khjezvah8V_DwBsvjgErlu-JBozu03cJ4oBy2k3yoGby56gfExyyGK210bfPnF5gMshGzXO4TuWhJ46fgW6N_GCAdG1oJ83s9JbXtDRLSkWRymYM" height=330 width=257></td></td> - -<td><td>The timeline start/end offsets are computed based on position of element on the page. When we increase the margin of the element the offsets get updated which affects currentTime and subsequently the animation output.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/7yFkBLxKEQnOW-Sdk10vdZluDxgGPQthrGPZG247xYSdHJiTDpmwuxk1mm9jNKFAR1orKDHaFO9abHThe-cdtZd20DjlRb4hdC0085ODhLqnzabP9PkpvtuiC5sYslmxtj5SFilB" height=329 width=254></td></td> - -<td><td>Scroll-linked animations show up in devtools and can be scrubbed on-demand!</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Animations Team Hackathon</td></td> - -<td><td colspan=2>To better understand the Web Animation APIs we’re using and experience the awesome ergonomics of them, and/or pain points, Gene (girard@) initiated the first ever Animations team 1-day hackathon. We created lots of fun experiments that exercise the new APIs: <a href="https://majido.github.io/animation_jam/app/index.html">interactive animation editor</a>, <a href="https://codepen.io/shengha2/pen/NWGWLvq">tetris</a>, <a href="https://codepen.io/yigu/pen/dyYPoLY">ping pong</a>, <a href="https://codepen.io/george-steel/pen/zYvYWxO">got it game</a>, <a href="https://jsbin.com/tanuzonixo/1/edit?html,css,js,output">pendulum </a>(<a href="https://docs.google.com/document/d/1VImYZIzh6mSRwBhSgwiUsB8Mj9NCASqMYzXEa4JXXk4/edit?usp=sharing">explainer).</a></td></td> - -<td><td colspan=2><img alt="image" src="https://lh4.googleusercontent.com/T_bcxoaClVBZ9n8k-zQlEaI9eMHlIamrMH4ydr7WSvu0hmvTec4RwW9ZsjCEc42w1VrhCY6QHwNXRFnUDmSkjHGvNBAKNXEb_x0C5qF2KegFbmFY2j01q_r4sBIbQnOVYdw66L4b" height=241 width=245></td></td> - -<td><td colspan=2>Constructing the perfect pendulum: an exercise in using the web-animations API</td></td> - -<td></tr></td> -<td><tr></td> -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | April 2020</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/april-2021---new-features-testing-stability-fixes-interop-fixes-metrics-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/april-2021---new-features-testing-stability-fixes-interop-fixes-metrics-and-more/index.md deleted file mode 100644 index d07f5bf22cd..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/april-2021---new-features-testing-stability-fixes-interop-fixes-metrics-and-more/index.md +++ /dev/null @@ -1,298 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: april-2021---new-features-testing-stability-fixes-interop-fixes-metrics-and-more -title: April 2021 - New features, Testing, Stability fixes, Interop fixes, Metrics - and more! ---- - -<table> -<tr> - -<td>April 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Composite background-color animation</td></td> - -<td><td>xidachen@ has been working on this feature aiming to relaunch the finch experiment. There are a few problems fixed during this sprint.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/F7Gd8acS30ufVNV31rACPtetP79aWl1e7A_6-egImHkIvP0HkTw8JezzJ9sGWDaTq90ESIT-AD2GzFziWEWT22vS8jQWypRx6XGa5jh1PhpJOqwv_e_l23yaTbPfPv7xIJzLY2ndjTOWTfw8mKN0kM5Utu3_KDwC3YtMCRXUdPwSR8VE" height=236 width=283></td></td> - -<td><td>The first one is decouple paint and compositing, which is shown in the above diagram. Before, we call “CheckCanStartAnimationOnCompositor” during the paint stage to determine whether the element should be painted off the main thread or not. Then at the compositing stage, we call the function again to determine whether or not the animation can run on the compositor thread. This causes problems because the property tree node can change during the paint and compositing. The problem is now fixed in this <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2740697">CL</a>, by not calling the above function during the paint stage, which requires us to implement a paint worklet code path to paint the element off the main thread.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/uMKCYFltvvzDFGgiOR0YM4RJAxCcXs2v1-CB6NjDKik24WSMmQ4l7QENYqmVBrwJXK_iYU-twKbkwe3qdmxuN4EhiUlAe-VzEbf3XzIQzcjdQAr2dF9fcDasCv9NrbXsOkwxvFDgd_G3PkzWVhUZFLJZpKkocEsCzFemLRAPJXyMr6c4" height=156.15577889447238 width=160.92156862745097><img alt="image" src="https://lh4.googleusercontent.com/mApGNxMJzTxfJyspM3dC2hDD5PxZPI0IbHlJXiUBojIatvcvUKruCfZ1dUaHo9oClrZybovSobha5abys1xu7JcVsoLuqVEnryeXE8O97ERzAPzQj5q_c3hfyxODc3alzEnHI9fSq6QtvcViSgCPrt1au2FDar9Yqf6hjyU7G3S6khE-" height=102 width=158></td></td> - -<td><td>The second problem is missing repaint in a few cases, which is tracked in this <a href="http://crbug.com/1184832">bug</a>. During this sprint we have fixed most of them.</td></td> - - <td><td>The first case is missing repaint when the background is transparent - during the animation. It is fixed in this <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2739318">CL</a>. - The animated gif on the left shows a background-color animation runs - correctly with the first frame being transparent.</td></td> - - <td><td>The second case is background-color animation on table row or table - col, whose background is painted into its table cell. In this case, we let - the animation fall back to the main thread. This is fixed by this <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2774182">CL</a>.</td></td> - - <td><td>The third case is background-color animation on the body animation, - while the view is responsible to paint its background. It is fixed by this - <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2779551">CL</a>, - which lets the animation run on the main thread.</td></td> - -<td><td>Experimental: native paint worklet</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/u4OXEWMRPI3jWZR3_7-yw4U3MTZzhp0HWcChG2GQzAplntSgS630soR4OHdF5FRPXDkcH7SBj2VLeubgwnZXuw5a2NbofZ5oLc_XC8DJtsB9DDmlo5WoSII-Ycf9sF9uSjis53JpIbp1CYXgoC1LR0CdJdR01p5Lc-eHpGfYPVoMxUSD" height=115 width=156><img alt="image" src="https://lh5.googleusercontent.com/LF-91rvLBmPzQjggeMwXQvees1eS98AvSlHfVn4zHgGdU-x2XVxiA9FOP3wfl2PGn_KACQX_Sl3nxmb2ve4xDOyLEohQ8TB0Nbt9NUh69KX4qok_Y8m6JT6fticXtTzNMTb0GRTKOc_FxERI9MKAcJiV_VILCai3Ip_iFD44VPgK6b9t" height=155.50314465408803 width=159.22981366459626></td></td> - -<td><td>Our team is partnering with the skia team, to develop a variant of CSS paint worklet (a native paint worklet), to paint the background faster using native code.</td></td> - -<td><td>The picture on the left shows example usage (full <a href="https://jsbin.com/foxasib/10/edit?html,css,js">JSBin</a> example). In the example, we don’t need to use the traditional CSS paint APIs such as “addModule” or “registerPaint”. Rather we use the “skottie” as the name to identify that this is native paint worklet.</td></td> - -<td><td>The change is in a work-in-progress <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2776692">CL</a>, currently the animation is running on the main thread, we need some more work to move it off the main thread.</td></td> - -<td><td>Declarative show-hide explainer</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/GBgzBa5UiaD5eZJ8uQvoFS6XgwJLNzTJXNxrAfI7YVCf1xXRAB_60I4NWtH6wq-0Hyu-CIIZfixOSVpjwGl4f084v0fUa2DX2UWifvj8i22ige0EO9VuvUDXKdamGPV72_e-DrmhwDxqb31lo6H1mlzbINbXAcxAg3cejGkZU4bpwYzY" height=181 width=283></td></td> - -<td><td>flackr@ published an explainer for the plethora of options to implement tabs.</td></td> - -<td><td>It has received early feedback from Brian Kardell regarding additional constraints and other options.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Testing</td></td> - -<td><td>liviutinta@ fixed flaky test pointer_event_pointercapture_in_frame in this <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2745276">CL</a>. Specifically, the issues found are:</td></td> - - <td><td>Successive test_driver.Actions().pointerMove might lead to coalesced - pointermove events.</td></td> - - <td><td>test_driver.Actions().send() is asynchronous, the test assumed that - it was synchronous.</td></td> - - <td><td>Differences between the test_driver.Actions() event streams between - Windows/Linux.</td></td> - - <td><td>Order of pointerup/lostpointercapture when pointer travels across - frames not well defined. Opened <a - href="https://github.com/w3c/pointerevents/issues/355">PEWG</a> issue. This - still leads to rare flaky runs.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Stability fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>CHECK failure during cc animation timing calculation</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/I6C6OMx1NCkE_II9gODyBjZWWhx5p3W5EP1eu9QYQ67bqgqud2m57pDBpCIjCTdU5W_UVj0ttJ926PJAUFi94fpXp_gFb2NcMzrkiFnZaSF2j7029gYhIZp6rd82bikH3O59P5zMboIwE1PrKfpfKt1Dz5xQjddJsCPcnp_3QOO6UW37" height=133 width=283></td></td> - -<td><td>kevers@ worked on the problem where cc does timing calculations a bit differently from WAAPI with respect to animations. The problem is shown in the above code snippets. We verified the timing conversion as part of the check for eligibility to run on the compositor, but we didn’t consider time_offset when making the determination. The solution is to include time_offset in the calculation.</td></td> - -<td><td>Crash GestureNavSimple::OnOverscrollModeChange</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/esadj0fzfzQpcgNrzGxyJ_syNrllUSVLwrHXAJv_OCtJn6hHlnI3pe0Hg7DbE6G92o7-7S5sUrqYDAta_U2MKB_UOtr8p6Xm5myTsS2j_viQ4ZP_jNghQwYv3nJbCCe0BiHzUnXG9hrpPnGY4bQdzBqfy08kllRyV4tyks-2_FrQakoq" height=59 width=111><img alt="image" src="https://lh6.googleusercontent.com/xGKhq1xxbus-Etdfb4zkdnRLnUntPYGC8TSsG-pdoi1Za2hlfrNOvoPfHAwiRf-BcEJRJfkMI8pfWlpt9QOyXP5cEtYhLRU6kxLtpbTOTtKu139Jkt4t-NK1DXrM27SWOR9bmqQ6x-CejXQQ_KUV31DjCQ5Q6mNAPaWvKiPu7JnEfbu2" height=50 width=160></td></td> - -<td><td>flackr@ <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2791883">fixed</a> a crash that is due to object lifetime issue. The problem is that an unowned pointer was given to the RenderWidgetHostViewAura’s OverscrollController delegate, when the view did not guarantee that the delegate stayed alive. In some cases the web contents (and delegate) could be destroyed before the view resulting in using the deleted delegate.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Browser-verified user activation shows misleading data!</td></td> - -<td><td>mustaq@ worked on the finch experiment on browser-verified user activation. Currently the finch data suggests verification failure rate is about 0.7%.</td></td> - - <td><td>Similar failures even in the Control groups where the feature is - disabled.</td></td> - - <td><td>The Control group is consistently better/worse than the Enabled - groups.</td></td> - - <td><td>This is the <a - href="https://docs.google.com/document/d/1_4Tg9Bt1OXO6mjAF3a-gaH07G-siGKeSkj13GQnOmjo/edit#bookmark=id.qztvoysscbtv">report</a> - for the finch.</td></td> - -<td><td>The only explanation is maybe extension messaging <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=957553">clobbering</a> user activation again. </td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Mac crash blink::Scrollbar::SetNeedsPaintInvaliation</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/sVOLsU_m4QNyn5mYqClGfgBsCZW3e1ys7TI4OvXfsRN1GzmvXVlCMxpP-rS4tLhnzfTWG-dBOwXiSM-nvHq50uJTDahsBCMfOWL2m8FgR16jVOjzVbpduB2E67yyTUiwggkNj5RxYpArtk4jh0FIk5wXfJU5m-AoXfWegbEGQ6IeMLvb" height=108 width=139></td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/P2M4ziyZ_7xRlM5REV6gCNre90jI8MGnM0wPP1Tsz5cDmmCOS8-CxzwZVix1UvwO_OoM0vKFxKfYylxt4N0aUEDMiCvP_mKXovThUMrkQaKV2unX3V1wkg_6z33x_oTJf0zpkFljE89WuswLLelb079kVXKwkPeL0WmEYmte7lxhNrK0" height=63 width=135><img alt="image" src="https://lh6.googleusercontent.com/WYXgzyOiSZdyTOQXAMJHKLg5Yceo01s6NAzNrkeO5i_xJMPj-r9ohXH2UCj8yVMZizs9BFbKtdxKV1Dr1VBvz5d6vakEddv-skoYOF-DlmhjXSWDYAJ3VjfUALC8krWRz5WHEiwX560Zj2zg57vfY5tcmt6pU2BzSQgJ8Wf_q_EiGNFg" height=64 width=138></td></td> - -<td><td>liviutinta@ fixed a crash related to scrollbar on mac.</td></td> - - <td><td>At first it looked like Scrollbar is used after free.</td></td> - - <td><td>In reality, in some cases animation_ is released/deallocated in the - middle of the call to setCurrentProgress.</td></td> - - <td><td>The solution was to keep animation alive during setCurrentProgress - by using Objective C retain/release.</td></td> - - <td><td>This is the top 7th renderer crash on latest beta on mac. It is - responsible for 4 bugs (2 <a - href="https://bugs.chromium.org/p/chromium/issues/list?q=id%3A1183276%2C1189926%2C&can=1">P1</a> - release blockers, 2 <a - href="https://bugs.chromium.org/p/chromium/issues/list?q=id%3A1194276%2C1193025%2C&can=1">P2s</a>).</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Interop fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Created sticky demo for web.dev interop article</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/mbLti-1KairtHNLRhylAT2mv25lCbch_Io8o0tZr-K8Rpve-Mh_AQD221he3KB0b8SLzKv2iZ5VWToKlBXN0bZhj9OWJR1epEGleEwA5iHC7WvAv-6UDjJZM7XWwpfDiLSuD2iktSB1qV-ziDBEvrOUs9o62O_UwlAm4k7GMoEa-VuH4" height=231 width=283></td></td> - -<td><td>flackr@ created a demo of one of the common remaining position sticky interop issues for the web.dev article <a href="https://web.dev/compact2021/">https://web.dev/compact2021/</a> which was published this sprint.</td></td> - -<td><td>Scroll-snap support for writing modes</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/GFUNUuZfoyToayBRC3SSWP7IphGoj22B-uK2MI6w_I6-1JtZRro9P9nAkTOEesL5x2mFSNpJupHzLMUACAijmKdKCzzfsDS-RiFYUfh0dfzJLFGKG2lohrqF4Yk8MQuQRd0ajDXD1YiyppnmXH0Sx_uXMNppwU92ya6FyHo4re7x62X7" height=94 width=134><img alt="image" src="https://lh3.googleusercontent.com/OHW5kXcg6uHP0ISGXjpN70Xv5R_pWv074djPWXZhWHlTCoRJCUepJecn0pdOMLx_uaQlqibW4a5Ck9tRyFNof02BWjS0B0Y_OQoGqPgOqeN6atzqWEeqpq-uLyZPKlGZIwOTHGMlpzLYmOVefrIZPJO7jatDhyf7FsmvLiRI4VT_9b5A" height=91 width=137></td></td> - -<td><td> Old New</td></td> - -<td><td>kevers@ worked on scroll-snap to enable support for writing modes.</td></td> - - <td><td>The image on the left-hand side shows the old behavior where some of - the writing modes aren’t supported.</td></td> - - <td><td>The image on the right-hand side shows that we now support all the - writing modes.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Scroll-snap outside of scroll corridors</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/nbVYNy4089lUbQyUYlN0tceM9q7lgvjWwnyoBPEL_EzqB1gwtDQDOkkF5G5kOnUUKoW7ArYZyZOtkD_BxoFLxfV2Xr8n7j0oPOcOR3guzmksRFD6QIK1CPXYrM90TNWYBQupSn1CJtKBWoq-YSpqkoKPxym0rCELfP8qLIi_gQsanV4Z" height=95 width=284></td></td> - -<td><td> Old</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/rsWuZoc7YVjlNpE7wREzQc0RTkv9pZw8F-bkZj3TLFvKNtogc6x9jab1cmBSv_XCoSgAxcgJwRpe-_mjoYmHtxeItWjfLja5UnvUoTqw5TOpqM-OEm8gS4etqmfmNUPKsaXmAR3ZVjDAANclCHOazcLl73SIs9gE25SMWm9VFSqHVF-n" height=95 width=283></td></td> - -<td><td> New</td></td> - -<td><td>The missing block was offscreen in both x and y direction. Missed as a candidate search position when combining independent x & y searches.</td></td> - -<td><td>Fixed tests in css/css-scroll-snap</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/l9uxIeMwmRJdi2FjqcXUx3KYyqDwvM5YFvNQVSEaCrRzV7fQYVxQiB6ngmfhW780IaHHUz1WbDlcqIyRPAYbWRgDvdbgPYyYZN1RhfMok6hJ4CF1jwzMzHAEdG4gurz-n38Ao0gI7idIK5BGTqc2tRmlw3eS7EZ9MLDUgIPk3-0oa1mm" height=97 width=283></td></td> - -<td><td>With the scroll-snap now support for writing mode and for snaps outside of the scroll corridor, a few tests has been fixed as shown in the above table.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Metrics</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>go/composite-relative-transform-finch</td></td> - -<td><td>kevers@ worked on a document highlighting finch results for internal use only, the efforts includes</td></td> - - <td><td>Communicated highlights in finch tracker bug with confidential bits - removed.</td></td> - - <td><td>Two cleanup CLs: one to remove the GCL for experiment, and one to - remove the web feature flag.</td></td> - -<td><td>Histograms for finger/pen drag distance</td></td> - -<td><td>We need data for the ChromeOS proposal to allow bigger slop for pen taps.</td></td> - - <td><td>The existing Event.TouchMaxDistance won’t work for us. Because it is - touch-only data, no data beyond slop rectangle.</td></td> - - <td><td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2779754">Added</a> - new histograms that splits distance-data into pointer-types. Specifically, - the histograms are Event.MaxDragDistance.{ERASER, FINGER, STYLUS}</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter VI: Bug Updates</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/Z-g42rQ4ADjdsT_O_WaXL9uVbo-Cp7XWcC3wUaUyzb_n_sLC_kxtVvS6HIUmX3vFkWv9xDXlZ-3eigN7eyJ47GzDU8-W4b3Nvv1k5d_k6svPePvj-Az6a4P0nHLwPq03aufydp4s9KJsjB69ReM5ZbwjsvrkHv3oD1W_MlqM4q1bp751" height=150 width=273> <img alt="image" src="https://lh6.googleusercontent.com/lXMwy691OYhQjVo0UFkzcmVZq7P_QCCZeJjqC_C0_4Nt2LQXIVy8F4Q0bQYOLJZ0YBnQVHiM58ut2jBYn4dJGelO60TSiRxbCqYzkdGh7x4aN5hob-OFE1RIFBXAo-a5zxM8p8Gz85P4uKpdhONqppEp7-h5rBOkuwVyIB-GvKC13XQT" height=152 width=278></td></td> - -<td><td>Our team is seeing a recent spike in P1s, and we are working on addressing the issues.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | April 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/april-2021-vol-2---new-features-testing-stability-fixes-interop-fixes-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/april-2021-vol-2---new-features-testing-stability-fixes-interop-fixes-and-more/index.md deleted file mode 100644 index ba242dd951f..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/april-2021-vol-2---new-features-testing-stability-fixes-interop-fixes-and-more/index.md +++ /dev/null @@ -1,257 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: april-2021-vol-2---new-features-testing-stability-fixes-interop-fixes-and-more -title: April 2021 (Vol. 2) - New features, Testing, Stability fixes, Interop fixes - and more! ---- - -<table> -<tr> - -<td>April 2021 (Vol. 2)</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Composite background-color animation</td></td> - -<td><td>xidachen@ resolved a few issues during this sprint.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/B_AGNBt9KFFBrKGrVF50Jlp1PqtXjwxYm2lsSP0YLcbaizx5xERcSuwz5phRvMf_HaqYCeTEAsmiZJb193hdCrcnfooYqfgwuVhtVi_--i51Q1mhIDMzaZR_iLU-lQcl9YX97BmB5g" height=92 width=283></td></td> - -<td><td>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.</td></td> - -<td><td>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 <a href="https://docs.google.com/document/d/1HtnP6oNFvcYIn91tHPhQR5n_8zhWLHfG_eXi4HG8Pzc/edit">here</a>, and we eventually decided that it is OK to composite these no-op background-color animations. The problem is fixed by this <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2795243">CL</a>. Fixing this issue also helped resolving an existing CSS paint worklet <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2841783">bug</a> which no-op animation.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/Tl9i_d3F9PEiHRIPX4S_AirQlASHhy2-iRGCZMZTadEGsvNlC_58ko-6By-j7oFG4TAIM0gQ_BGkwaix3uWCaYK9iT7VOtRy1nDUNVBpAInsugo534oM0uLatt9K4iMN9KIgInQX0Q" height=64 width=283></td></td> - -<td><td>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 <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2836907">CL</a>.</td></td> - -<td><td>Capability Delegation moved to WICG</td></td> - -<td><td>mustaq@ made awesome progress during this sprint, which includes</td></td> - - <td><td>Finalized <a - href="https://docs.google.com/document/d/1VQiJBo_hBfgKfHN3lZnhHbs9ws74TCu5i-__y8_mdBU/edit?usp=sharing">Q2 - action plans</a> with Payments team (thanks to smcgruer@).</td></td> - - <td><td>Secured public approval from <a - href="https://discourse.wicg.io/t/capability-delegation/4821/3">Stripe</a>, - and thumbs-up from <a - href="https://github.com/w3c/mediacapture-screen-share/issues/167#issuecomment-821290060">Mozilla</a>.</td></td> - - <td><td>Moved the proposal to <a - href="https://github.com/WICG/capability-delegation">WICG/capability-delegation</a>.</td></td> - - <td><td>Updated/deprecated all related public threads/docs: HTML <a - href="https://github.com/whatwg/html/pull/4369">#4369</a>, <a - href="https://github.com/whatwg/html/issues/4364">#4364</a>. Crbugs: <a - href="https://crbug.com/928838">928838</a>, <a - href="https://crbug.com/925331">9253331</a>, <a - href="https://crbug.com/931966">931966</a>. Docs and repos: <a - href="https://github.com/mustaqahmed/user-activation-delegation">repository</a>, - <a - href="https://docs.google.com/document/d/1NKLJ2MBa9lA_FKRgD2ZIO7vIftOJ_YiXXMYfRMdlV-s/edit?usp=sharing">design - doc</a>, <a - href="https://github.com/mustaqahmed/autoplay-delegation/">follow-up attempt - repo</a></td></td> - -<td><td>Click as PointerEvent</td></td> - -<td><td>liviutinta@ and mustaq@ collaborated on this work.</td></td> - - <td><td>Identified a regression in older <a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1192449#c31">Esri - software and APIs</a> which is widely used related to fractional coordinates - for click.</td></td> - - <td><td>Disabled the <a - href="https://critique-ng.corp.google.com/cl/369699904">Finch - 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 - href="https://groups.google.com/a/chromium.org/g/blink-dev/c/bta50W_Hg24/m/YAYeAzCZAAAJ">final - 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 - href="https://github.com/w3c/pointerevents/issues/100">Pointerevents - spec</a>.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Testing</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll-snap: Deflake tests</td></td> - -<td><td>kevers@ deflakes a few scroll-snap tests:</td></td> - - <td><td>The first set is snaps-after-scrollbar-scrolling-\*. The problem is - rare TIMEOUTs. The solution is to accelerate animation timing. Fixes main - thread testings only.</td></td> - - <td><td>The second is scrollend-event-fired-after-snap. The test fails due - to incorrect event ordering. The solution is to reset to prevent scroll end - during test reset from being triggered as an end before scroll is - finished.</td></td> - -<td><td>Mousewheel: Deflake tests</td></td> - -<td><td>kevers@ also deflakes a few mousewheel tests. There are a few problems with the tests:</td></td> - - <td><td>Several mouse wheel tests are flaking.</td></td> - - <td><td>Focused on <a - href="https://source.chromium.org/chromium/chromium/src/+/HEAD:third_party/blink/web_tests/fast/scrolling/percentage-mousewheel-scroll.html;l=1;drc=e51dd5c377fd47393a171f6bdcd7c1a6a9a609c5?q=percentage-mousewheel-scroll&sq=&ss=chromium%2Fchromium%2Fsrc">percentage-mousewheel-scroll</a> - which has highest scroll on flake dashboard.</td></td> - - <td><td>Scroll and wheel events getting dropped.</td></td> - - <td><td>Not differentiating between missed wheel event and incorrect - result.</td></td> - - <td><td>Missing test cleanup.</td></td> - -<td><td>The solutions to the above problems are:</td></td> - - <td><td>Set mouse position before triggering synthetic wheel - event.</td></td> - - <td><td>Ensure that scroll event is received.</td></td> - - <td><td>Ensure wheel event is received.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Stability fixes</td></td> - -<td><td>Fixed UAF due to promise resolution timing</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/K3v4CmTZiknQj2hNvwbhnT-A7daryFxJOBV_Oc8rF41LmZf6f_ngngIbjIySHjPtfJJVQKC3p57kQ8tba0WgoyckbH9iciVOGEvm-JRjFkCKVcY4eI4HcyIva3BYjvb1FVwejKJnKQ" height=207 width=262></td></td> - -<td><td>flackr@ fixed a UAF problem. Specifically, we were synchronously resolving ready promise during <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1196781#c10">RunPaintLifecyclePhase</a>. Since promise resolution already <a href="https://source.chromium.org/chromium/chromium/src/+/HEAD:third_party/blink/renderer/core/animation/animation.cc;l=2382;drc=c86618b300799fd70be83a72afbe7e15f124493d?q=Animation::CommitPendingPause">handles forbidden script context by posting a task</a> so the solution was to wrap UpdateAnimations call in ScriptForbiddenScope. We move ScriptForbiddenScope to entire lifecycle with explicit exceptions for locations where we expect/handle script execution.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Interop fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll-snap: Resnap to focused element after layout</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/pUAg3nUiQw_QiWhDPwX_-zf4Y5wK-iz41FcUKRHSaraaujjDbrsoftqCX0gQ2vFiWsOZofPDYeVbxSlhI6xkBagvhACUJsNTq57M2X8hsAK5ZBU_27reWwfoQPMIdNjsoYRNDC8bCg" height=127 width=283></td></td> - -<td><td>The problem is that when snapping, multiple candidates can be equal distance from the origin of the snapport. If one of these candidates is focused, it should be snapped after a relayout.</td></td> - -<td><td>The solution is to make whether the element is focused a tiebreaker when selecting a snap target.</td></td> - -<td><td>Scroll-snap: mousewheel scrolls skipped snap positions</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/wcoZ25PYAKWFr9ldrG3JhCVq15c_0fEQwWt193N-MvDHsrMOY5Jm7nnzASz3h1sEXgnJ84gqbRAs0gpwR0IUKdu6XgqPBY6hBdQUyLUMcGYG22T75aeWqjbH2_Vyd_BIwbWNgmZcMQ" height=193 width=283>.</td></td> - -<td><td>Here are the problems:</td></td> - - <td><td>Scroll snap called when a scroll animation ends and on a gesture - scroll end.</td></td> - - <td><td>Gesture scroll end delayed in anticipation of additional mousewheel - ticks.</td></td> - - <td><td>Results in two directional scrolls, skipping over the nearest snap - position.</td></td> - -<td><td>The solution is to snap only on animation end. The next steps are initiate snap at gesture scroll begin for mousewheel scrolls.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Bug Updates</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/asi8pz5cPdAdbRaT-2QaBXhimLiPNYUwLMuUWIN4eWnVg0wwsGzgKLpsrcnQMKLu1Z02oiSTuUoFz7_XAzp83nOPSUzagwURcAHpuvFTRPnHSmTUa3-Yc_ipIPZr7Wbi2YZ4OvYyzg" height=157 width=283> <img alt="image" src="https://lh4.googleusercontent.com/OdAwuP64GqE3kURtMFPLaBSsitA3sy6MKWaGib6vkg2Tn-1NvkJkKDgHOaooynN4ENovUyFfP5Z0UzHrGEyy3jZYThYEyEefnpqt1peP0aCyB5IDsC2Xz3UmM-nXTZbCs4A3Mf8YlA" height=154 width=276></td></td> - -<td><td>Our team had a sizable influx at the start of this sprint. Great efforts were made to stabilize the amount of bugs and even keep P1 bug number drop.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/_abXC_M3LqFDCPe31DLX4hv01AyN19LMYlV3UDx7fPGchqAutCc9tGLKuDaM51LBUKc6SBcVYiQRjJCaznQzw16sJD8xir4Mqyq1RuBfJtk05ganqrhVTSqdVv0QKdCTkkmSGUCwSQ" height=196 width=318> <img alt="image" src="https://lh3.googleusercontent.com/iYcG2KtoT0Mt7qB3T7P-PzUhH-A6HYmLG5gw28veSDEhvvxp_O0DQ18EeJwRXqB4mqaclC1PJ6WZW1T0YrMiU7AAlHLUzLbDRCA721-B2d54YoNlo1TlsNWx83zDgrDjSqODzTG8kA" height=198 width=234></td></td> - -<td><td>skobes@ fixed a scroll unification bug (<a href="http://crbug.com/1155655">crbug.com/1155655</a>).</td></td> - -<td><td>Symptom: can't scroll sub-scroller in iframe. Root cause: compositor thread hit testing had an early exit if it saw no scrolling layers, which did not check for slow-scroll regions. Extra challenges:</td></td> - - <td><td>Couldn't repro locally until realizing bug was OOPIF-correlated - (hint: rainbow layer border)</td></td> - - <td><td>Slow-scrollers can contain or be inside non-scrolling layer-promoted - elements. Therefore, we need to check slow-scroll region on EVERY layer that - is hit, not just the one in front.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | April 2021 (Vol. 2)</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table> diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/august-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/august-2019/index.md deleted file mode 100644 index e1a0a4274af..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/august-2019/index.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: august-2019 -title: August 2019 ---- - -<table> -<tr> - -<td>August 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh4.googleusercontent.com/oITVrglJINBJXDLj60V-z4SMEW9MG6rx2JrEdK6SyHqpBrYlhTL2l8LaJlvJh2jpm1XIXfjt788fB0wNN2xzzaDC1sy5tQ9jLTL-kFadhFnPNQdGNnB_vWtZHqp6QY9S4j02jkHR" height=267 width=596></td> - -<td>The opening slide from smcgruer@'s <a href="https://docs.google.com/presentation/d/1qSNpFJaCvuqibe0iPc1tBSwAPp1LSXFqPIKun-_Pj_U/edit#slide=id.g5f8061889d_0_0">presentation</a>. Fun fact: Google Slides is convinced 'casually' is not a word.</td> - -<td>Investing in knowledge</td> - -<td>To borrow a quote that was (maybe) said by Benjamin Franklin: "An investment in knowledge pays the best interest". Stephen (smcgruer@) embodied Franklin this sprint as - faced with <a href="https://crbug.com/979952">a bug</a> that he could not understand - he went back to basics and taught himself the Blink Animations interpolation stack from the ground up. His investment paid off. Stephen was not only able to fix the original bug, but he also discovered and fixed <a href="https://crbug.com/992378">another bug</a>, and gave <a href="https://docs.google.com/presentation/d/1qSNpFJaCvuqibe0iPc1tBSwAPp1LSXFqPIKun-_Pj_U/">a presentation</a> to the rest of the team sharing what he had learnt. The S&P 500 would be jealous of that <a href="https://www.investopedia.com/terms/r/rateofreturn.asp">RoR</a>.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/z53pe_NaaKwQUwC7wEzpQwDm0SgTT8WqRF91CAbqIKQ_pmh8HP_ZkhaUFx4kepVUD8QA09z961YZIfgy3OVEPy9D3oaj41aErpS_e-gypoow_vzRXtxiZKgsen6COqvZTQe_U3fn" height=171 width=281></td></td> - -<td><td>Constantly in style</td></td> - -<td><td>The interaction between Animations and Style is a subtle and sometimes fragile one. Animated objects are always changing, but we try to avoid causing full CSS style updates because those are expensive. Sometimes, however, we miss cases. This sprint, Rob (flackr@) discovered that pseudo-elements could <a href="https://crbug.com/988834#c9">override our no-change detection</a> code and cause unnecessary main frames! Thankfully our friends from the Style team were able to put together <a href="https://chromium.googlesource.com/chromium/src/+/b1cadc00d4f06846f7c426f66ee4a49e6a543177">a fix</a> and give our users back some frames.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/ScnUy4fn8zMfH0LcXR9ggqqatjErYxfCtLmcWEGgG06MI16f4PZWkHluvlzbAApSo0hE7BXCDDMSz5l8NBl6CJ2ncMTimLiaISR5eY954baOZHR3Hii6a_o8D7IxJ3XAXp7GP10q" height=227 width=115> <img alt="image" src="https://lh4.googleusercontent.com/lkKYKI9N9e8vb0OxTHmKn9UFUQcRb1JKezJUy9iDMY3anAvzIxMAGXB2VfOs03tiSfDcZKpmevU9DRz860L_O7pD6sdYUS90lfsXbcKAWKLQlSw3GS0DiL4mJTbwEvlSM3JhA9-a" height=227 width=115></td></td> - -<td><td>Smooth Paint Worklet animations</td></td> - -<td><td>An important goal of the <a href="https://docs.google.com/document/d/1USTH2Vd4D2tALsvZvy4B2aWotKWjkCYP5m0g7b90RAU/edit?ts=5bb772e1#heading=h.2zu1g67jbavu">Off-thread PaintWorklet</a> project is being able to animate Paint Worklets on the compositor thread. This keeps them smooth even if the main thread is busy. As of our most recent sprint, this is now working (behind a flag) in the latest Chromium code! The example above shows that the animation is smooth (left-hand side) with the flag turned on, and less smooth (right-hand side) with the flag off.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Timing is everything</td></td> - -<td><td>Kevin (kevers@) has been celebrating the summer months by tackling an ambitious code health project - bringing blink::Animation in line with the web-animations spec. Thanks to Kevin's hard work (and a steady supply of strong coffee), our implementation is slowly but surely converging with the web-animations spec. This not only makes it much easier to understand, but a healthy number of web platform test failures based on tricky timing issues have been squashed. Fantastic work by Kevin!</td></td> - -<td><td>Countable CSS</td></td> - -<td><td>Taking a brief break from direct Animations work, Majid (majidvp@) discovered some <a href="https://crbug.com/993039">problems</a> with how CSS UseCounters are created this sprint. The manual (!) process was complex, missing a step in it could cause cascading failures for later-added CSS properties, and there were no automatic checks at all that it was all correct. No longer, thanks to Majid - he managed to <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1752503">remove one step</a> from the manual process and also added a set of <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1755413">automated presubmit checks</a> so nobody else will have to go through the pain he did!</td></td> - -<td></tr></td> -<td></table></td> - -<td><a href="https://www.lucidchart.com/documents/edit/069541b2-a5d7-4b5f-89f3-56455afac3f3/0?callback=close&name=docs&callback_type=back&v=972&s=660"><img alt="image" src="https://lh5.googleusercontent.com/h1XoTiLsay-bJT3_4WgJYlI7xCNMbSjeppOoc04D-JAZ-d3JInkO3NQcRt13bDSifCULj3olIczD_QH9d9XEg29oG6TlP285eaX8ebrPOJeXhoGKAxG5egQ6VJ9G9Upg1wgAqiGJ" height=394.6268181818181 width=511></a></td> - -<td>Figure that shows how the verification of hit test result works and how it does not work</td> - -<td>False positives + mismatches == matches…?</td> - -<td>Viz hit testing v2 is heading to stable (yay!). This sprint Yi (yigu@) investigated the remaining cases where the v2 result does not match what Blink comes up with. In a moment of serendipity, it turns out that half of the mismatches were false positives due to an imperfect verification path. When iframes are slow to load, there were <a href="https://docs.google.com/document/d/1AlDyVvKtZ_SZZey_76srFqaTM-QPor0pKc6VXE7lEMU/edit">three points in time</a> where Viz and Blink used different hit test data for the verification - which lead to mismatched results being reported. With this bug fixed, the mismatch rate dropped from 0.04% to 0.02%.</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | August 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/august-2020---code-health-animations-context-menu-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/august-2020---code-health-animations-context-menu-and-more/index.md deleted file mode 100644 index 9123ad5d3fd..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/august-2020---code-health-animations-context-menu-and-more/index.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: august-2020---code-health-animations-context-menu-and-more -title: August 2020 - Code Health, Animations, Context Menu and more! ---- - -<table> -<tr> - -<td>August 2020</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Code Health</td></td> - -<td><td>Our team had an awesome sprint on bug fixing.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/owiAyDpZzfTYW5rAik3nJan9W6E4DsI0s127oetssl1Zpt1CrnI3BFqNW_HoOR3IRQFga05EQ1eiobzNGqISyuo4jxVC6H8eGZyxNXd_uGdBAVUImHk-koHYjRv4E26J-BPZ-7h9QA" height=168 width=307></td></td> - -<td><td>Thanks to kevers@, we now have a bug dashboard (<a href="http://goto.google.com/interactions-dashboard">go/interactions-dashboard</a>). The above graph shows opened vs closed bugs during this sprint. The dashboard also includes:</td></td> - - <td><td>Breakdown of cumulative issues opened and closed by - component</td></td> - - <td><td>Total number of open issues by component</td></td> - - <td><td>Breakdown of closed issues by reason</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/v5UeZaDBwG0E8xifSNGs1zWxbO1IrJjsnUf1CXk-Urydx7EyS6ooei0deoEbs5Zxn2p9FvWQq4XeLlnaRMnY8lgGND36PfW6qnDmRWKVcqzaDuUg3lpezDfWp5g0iKll5StZi2xG7Q" height=158 width=492></td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/tyCAkYty-BGkwHg3GgW3MJwsn17hn1f6OmLDsZ03KTF6EdRRbYxvo2NkYmnipCd8-FmCIlNjy8P6wogQz9n0y6ArNgEXT6PQqFAGjutSPARPCT_rry5ERxuWaYkgjxCem5iPYZHgow" height=164 width=500></td></td> - -<td><td>flackr@ fixed <a href="https://crbug.com/1116020">flicker when setting style in finish callback</a> (<a href="https://output.jsbin.com/darepen">demo</a>)</td></td> - - <td><td>The top demo is broken, and the bottom one is fixed.</td></td> - -<td><td>liviutinta@ fixed several bugs:</td></td> - - <td><td>A Pointer Events tiltY reversed on Mac bug (<a - href="http://crbug.com/1111347">1111347</a>).</td></td> - - <td><td>Fixed flaky test where pointermove on chorded mouse buttons when - pointer is locked (<a href="http://crbug.com/1025944">1025944</a> <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2360494">CL</a>)</td></td> - - <td><td>Fixed 3 failing browser tests for Unified Scrolling: <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2364055">CL</a></td></td> - -<td><td>gtsteel@ made great contributions to bug fixing.</td></td> - - <td><td>Fixed crash in run_web_tests caused by increased number of X11 - connections used: <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2368420">CL</a>.</td></td> - - <td><td>Fixed AnimatedCSSProperties metric to count properties when animated - (by anything which uses a KeyframeEffect) (<a - href="https://crbug.com/992430">Bug</a>)</td></td> - - <td><td>Started UMA study towards fixing transition cancelling when - resetting style (<a href="https://crbug.com/934700">Bug</a>)</td></td> - - <td><td>Relanded patch adding ontransition\* event handlers: <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2258467">CL</a>.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/hvsHNNrrxW1mAKU5UZUYURv7Man5793AmBYMJKxYNpazzfTZNao081OYbnQXawm_DaQC8mU9TcmEqfv1OoJBozBgQ5mFfUWptIfor2IkQq3hC9L5XKdms_CGuLy1YoNIjPOG21J6Ng" height=146 width=273></td></td> - - <td><td>Top animation is composited</td></td> - <td><td>Bottom animation is main thread</td></td> - - <td><td>After the fix, the composited animation aligns with the main thread - animation and there is no jump on reversal.</td></td> - -<td><td>Animations</td></td> - -<td><td>kevers@ fixed a weird reversal of composited animations with start-delay.</td></td> - - <td><td>The problem is that the process of converting timing properties to - time offset for the compositor assumes the animation is running in the - forward direction. The time offset is incorrect if playing in the reverse - direction and there is a start delay (<a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1095813">1095813</a>).</td></td> - - <td><td>The solution is to Include the tweak for start delay only if the - playback rate is positive. (<a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2339712">CL</a>).</td></td> - -<td><td>kevers@ Fixed 5 WPT test flakes and one non-WPT test flake for animations. (<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1093451">1093451</a>,<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1092177"> 1092177</a>,<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1092141"> 1092141</a>, <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1064065">1064065</a>, <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1085564">1085564</a>, <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=623434">623434</a>)</td></td> - -<td><td>WebDriver Actions API Spec</td></td> - -<td><td>lanwei@ finished the implementation in Chromedriver and Webdriver (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/2324972">CL</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2316405">CL</a>)</td></td> - -<td><td>Azimuth/Altitude for Pointer Events</td></td> - -<td><td>liviutinta@ shipped the Azimuth and Altitude.</td></td> - - <td><td>Received 3 LGTMs on <a - href="https://groups.google.com/a/chromium.org/forum/?utm_medium=email&utm_source=footer#!msg/blink-dev/ZRI-7X_4GwM/Sp1ZMIw5AgAJ">Intent - to Ship</a></td></td> - - <td><td>Landed <a href="http://crrev.com/c/2343385">CL</a> to enable the - feature flag by default</td></td> - - <td><td>No feedback yet from <a - href="https://github.com/w3ctag/design-reviews/issues/537">TAG - Review</a></td></td> - - <td><td>Positive signal from Webkit, no signal from Gecko.</td></td> - -<td><td>Context Menu with Touch-Drag</td></td> - -<td><td>mustaq@ Added context menu support to draggable elements: behind a flag, show Window native draggable behavior of showing context menu on drag end (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/2340287">CL</a>).</td></td> - - <td><td>Before: draggable divs can’t show context menu because a touch - interaction has to choose between dragging vs context-menu. We have links - and images always non-draggable for this reason. (Hi-res video <a - href="https://drive.google.com/file/d/1W2zX7_SdCVVoV0yh9nwK6SY7X29ozOII/view?usp=sharing">here</a>).</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/mI0QBIs9oloJh6Foi_XwnQJzfH4VwmPZejBZkcPwmMOEjj2k4R9l-ledgLWkVXpVONHg6sHtsZU1JhlPqWkoz5RZqbv8MoMBmkjcL70QaqXT9n9fvov5ltkyj_5xqNOF_dDNh1jbZQ" height=200 width=280></td></td> - - <td><td>After: draggable elements shows context menu on drag-end, like - Windows desktop icons. Context menu depends on where the element is dropped. - Works on divs, links and images. (Hi-res video <a - href="https://drive.google.com/file/d/1MkUOjoi6qJnUl_XFphFzqonVQjg9XyO5/view?usp=sharing">here</a>.)</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/Y4BB2dlHUTM3gmFARKxmlPRJ0WWZhSLkaCwNr_r7LrbsRPBBqaoY6sSvKYgEe13wMVEmZFWsUI4bTnTSHnZnewJiJWDqjhChVNLLbkOZqw_klQOQ1ZusQw8cvyAApXSkCLFRDuM3Rg" height=200 width=280></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Throughput Metrics</td></td> - -<td><td>xidachen@ fixed wrong reporting in video frame sequence length (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/2342247">CL</a>), where 50% had length of 0 frames.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | August 2020</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/august-2021---new-features-fixit-testing-code-health-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/august-2021---new-features-fixit-testing-code-health-and-more/index.md deleted file mode 100644 index d31cb9f84f8..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/august-2021---new-features-fixit-testing-code-health-and-more/index.md +++ /dev/null @@ -1,361 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: august-2021---new-features-fixit-testing-code-health-and-more -title: August 2021 - New features, Fixit, Testing, Code health and more! ---- - -<table> -<tr> - -<td>August 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll timeline spec</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/m5zIa5C1ZvdM09GFsx1cTUAA5aMCjRCMYDm5hT5ug7WGQqca86W_kSBc2bYuyFEc1y3cB7bDBg8RBBCX2RE_P--GbZUX0NxR4yG_d9tn0NryDCOmMYzutUnC6tpydCMaIfz06BHxxA" height=145 width=283></td></td> - -<td><td>kevers@ changed the spec for the “setting the timeline of an animation” part.</td></td> - -<td><td>Problem</td></td> - - <td><td>Scroll-timelines are now progress based and not time based. Two - cases where we need to preserve the “progress”:</td></td> - - <td><td>Switching to a scroll timeline while paused</td></td> - - <td><td>Switching from a scroll timeline.</td></td> - -<td><td>Solution</td></td> - - <td><td>Augment procedure to include calculation of previous - progress</td></td> - - <td><td>Preserve position.</td></td> - -<td><td>kevers@ is also changing the CSSNumberish current and start times. CSSNumberish is a double or CSSNumericValue, where CSSNumericValue has a value and a unit.</td></td> - - <td><td>The problem with current & start times remaining as doubles is that - it requires inferring a different unit depending on the timeline. Animations - associated with a scroll timeline are progress based and not time - based.</td></td> - - <td><td>This would allow:</td></td> - - <td><td>scrollAnimation.currentTime = CSS.percent(30);</td></td> - - <td><td>timeAnimation.startTime = - CSSNumericValue.parse(‘-30ms’)</td></td> - -<td><td>Composite BG-color animation</td></td> - -<td><td> <img alt="image" src="https://lh6.googleusercontent.com/YwLTJWcJyqJCA3Qp3Udo7jVtFHSpaW_DltCWoYfwHucQ5S6TsUlcI1s-OOCVq-EnGpuStDav3F26tpwZYB4lUXtkEa-_fJ6QTfX8nCmzr3t6-HuFSIDNMxVJQnjyI8FnosUWhwlRqg" height=124 width=283></td></td> - -<td><td>xidachen@ launched the finch study for composite bgcolor animation. The preliminary <a href="https://uma.googleplex.com/p/chrome/variations?sid=9249d9466a749268e49631a32938b1bb">result</a> looks very positive.</td></td> - - <td><td>The above table shows the summary of the result with all platforms - combined, canary + dev channels.</td></td> - - <td><td>Note that the blue ones show significant difference, the black ones - are “not significant”.</td></td> - -<td><td>Given the positive finch result, we will ship this in M94.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Fixit</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - - <td><td>FixIt organizers are awarding skobes@ with a <a - href="https://docs.google.com/presentation/d/1ahjM6k4TjGw6Pf_DGg1d7b30xROnav-7vV9ec-6CI1U/edit#slide=id.ge570983615_0_2467">High - Achievement award</a> for fixing the <a - href="https://crbug.com/43170">oldest bug</a>.</td></td> - - <td><td>We closed <a - href="https://bugs.chromium.org/p/chromium/issues/list?sort=Pri%20-Stars&x=Status&y=Owner&cells=counts&q=label%3Achrome-fixit-2021%20owner%3Aflackr%2Cgirard%2Ckevers%2Cmustaq%2Cskobes%2Cxidachen%20status%3Afixed%2Cverified%2Cwontfix%2Cduplicate&can=1&colspec=ID%2BPri%2BStars%2BType%2BComponent%2BStatus%2BSummary%2BOwner%2BModified%2BOpened">15 - bugs</a> in total:</td></td> - - <td><td>Got rid of bugs with <a href="https://crbug.com/716694">52</a>, - <a href="https://crbug.com/1148143">37</a>, <a - href="https://crbug.com/43170">27</a> and <a - href="https://crbug.com/61574">12</a> stars.</td></td> - - <td><td>Landed code to fix <a - href="https://bugs.chromium.org/p/chromium/issues/list?sort=Pri%20-Stars&colspec=ID%20Pri%20Stars%20Type%20Component%20Status%20Summary%20Owner%20Modified%20Opened&x=Status&y=Owner&cells=counts&q=label%3Achrome-fixit-2021%20owner%3Aflackr%2Cgirard%2Ckevers%2Cmustaq%2Cskobes%2Cxidachen%20status%3Afixed%2Cverified&can=1">7</a> - of bugs.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Testing</td></td> - -<td><td><table></td></td> -<td><td><tr></td></td> - -<td><td><td>Deflake scrolling tests</td></td></td> - -<td><td><td>kevers@ fixed quite a few flaky scrolling tests.</td></td></td> - -<td><td><td>mouse-autoscrolling-on-deleted-scrollbar:</td></td></td> - - <td><td><td>Timeout: fixed by deferring start until ready</td></td></td> - - <td><td><td>Position mismatch: fixed by waiting for scroll event before - checking position</td></td></td> - -<td><td><td>wheel-scroll-latching-on-scrollbar</td></td></td> - - <td><td><td>Timeout: fixed by deferring start until after - onload</td></td></td> - - <td><td><td>Position mismatch: fixed by allowing for fractional - offset.</td></td></td> - - <td><td><td>Note this was the top Blink>Scroll flake!</td></td></td> - -<td><td><td>mouse-scrolling-over-standard-scrollbar</td></td></td> - - <td><td><td>Position mismatch: fixed by using established way of determining - scroll thumb position and waiting on scroll event.</td></td></td> - -<td><td><td>Deflake an animation layout test</td></td></td> - -<td><td><td><img alt="image" src="https://lh5.googleusercontent.com/QPnqYwNJLp7eAqU1gLSfLhImusPZX2D2kIs1E0j_IglvO4r7DOSfHCIVBfyA5mV3pNcH5O5i_WfhegxFsuuoaBqfZXUO0L7HmmXnbiD7tQm-omNhSlSx-47ZUCCQIASa-fHRGS-hCA" height=39 width=277></td></td></td> - -<td><td><td>xidachen@ fixed a top Blink>Animation flake. The root cause is that we do “A==B” when we compare two AnimationTimeDelta, and that the precision issue caused flakiness.</td></td></td> - -<td><td><td>The fix is shown above, which is by introducing an epsilon when comparing two AnimationTimeDelta.</td></td></td> - -<td><td></tr></td></td> -<td><td></table></td></td> - -<td></tr></td> -<td></table></td> - -<td>Chapter IV: Code Health</td> - -<td><table></td> -<td><tr></td> - -<td><td><table></td></td> -<td><td><tr></td></td> - -<td><td><td>Remove use of DeprecatedAtOrEmptyValue in animations</td></td></td> - -<td><td><td><img alt="image" src="https://lh4.googleusercontent.com/ui6bPPR-paFdFEVPGiMhTMZFVQbPfxyYsjpq3EElvbp7Z3EfAZZ8SawdFzxoyn5B25f-eEN4QumftjcjYPjtGQUrSZJcYgSq7hB-T42eTh1OjVkamB8HxpuP-x-Av1Uxj44uJ95sQA" height=21 width=277></td></td></td> - -<td><td><td>kevers@ removed the usage of DeprecatedAtOrEmptyValue in the animations code base.</td></td></td> - - <td><td><td>Here is the <a - href="https://docs.google.com/document/d/18JIiajErikZaBzCtZvl-wwAJShqZsg0jT9wVyPBhSdU/edit">design - doc</a> for WTF::HashMap<>::at() refactor.</td></td></td> - -<td><td><td>Cleanup of CompositorKeyframeModel constructors</td></td></td> - -<td><td><td>kevers@ cleaned up the CompositorKeyframeModel constructors.</td></td></td> - -<td><td><td>The issues are:</td></td></td> - - <td><td><td>3 public and 1 private constructor. All public versions end up - calling the private constructor</td></td></td> - - <td><td><td>Unnecessary if-else construct</td></td></td> - - <td><td><td>Opportunity to improve efficiency with move-value - semantics</td></td></td> - -<td><td><td>Resolution:</td></td></td> - - <td><td><td>Single constructor that takes a KeyframeModel::PropertyId - argument</td></td></td> - - <td><td><td>Add move constructor and move assignment operator to - TargetPropertyId</td></td></td> - - <td><td><td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/3060658">Negative - line count CL</a>.</td></td></td> - -<td><td><td>Refactor Native PaintWorklet</td></td></td> - -<td><td><td>xidachen@ refactor the native paintworklet code.</td></td></td> - - <td><td><td>Detailed design <a - href="https://docs.google.com/document/d/12g1OLIxZk9ayLNbOI87ru_yoUUWdxcKewDLRR4tqzi8/edit#">doc</a> - here.</td></td></td> - - <td><td><td>The refactor reduced a middle layer, and made the entire - workflow simpler.</td></td></td> - - <td><td><td>Landed 3 CLs. (<a - href="https://chromium-review.googlesource.com/c/chromium/src/+/3016115">Part1</a>, - <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/3044499">Part2</a>, - <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/3067315">Part3</a>)</td></td></td> - -<td><td><td>Magic behind move-value</td></td></td> - -<td><td><td>kevers@ learned something about std::move.</td></td></td> - -<td><td><td>Move constructor</td></td></td> - - <td><td><td>Foo::Foo(Foo&& other): other is a temporary object that may have - its contents reset as a result of the move. Note the r-value ref cannot be - const.</td></td></td> - -<td><td><td>Move assignment:</td></td></td> - - <td><td><td>Foo::operator=(Foo&& other): same thing. Other is temporary and - may be reset.</td></td></td> - -<td><td><td>Foo foo = CreateExpensiveObject(...)</td></td></td> - -<td><td><td>In this case, no std::move is required since RHS is already an r-value.</td></td></td> - -<td><td><td>Foo expensive_foo_instance = TakeOwnership(std::move(expensive_foo_instance));</td></td></td> - -<td><td><td>std::move is required to take advantage of move-value semantics since expensive_foo_instance is an l-value. Adding std::move converts to an R-value reference.</td></td></td> - -<td><td><td>Useful instead of const & when not able to share an instance but can pass ownership. <a href="http://thbecker.net/articles/rvalue_references/section_01.html">Further reading</a>. See also <a href="https://docs.google.com/spreadsheets/d/1U8byWhb9_vGWVzYtnh8UoH0Xv0vpEyfumUnh2GpOruw/edit#gid=0">pkastings C++ 201 talks</a>.</td></td></td> - -<td><td></tr></td></td> -<td><td></table></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Stability/security fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Fake user activation from Extension Messaging</td></td> - -<td><td>Interactions team and Extension team together made a concrete plan about an old P1 security issue with fake user activation (<a href="https://crbug.com/957553">Issue 957553</a>).</td></td> - -<td><td>Here is a brief history to see why this is important:</td></td> - - <td><td>The problem was known 3+ years ago, and we got the security bug 2+ - years ago.</td></td> - - <td><td>We posted solution ideas but compat risks held us back. Our <a - href="https://docs.google.com/document/d/1TKjjwFlQGh2LLm0_mOW6FJdmmwyOBMj_fdWJyAJ_Q50/edit?usp=sharing">design - doc</a> in early 2020 didn’t get enough traction for the same - reason.</td></td> - - <td><td>We added UMA in late 2020 to slice the problem but got <a - href="https://docs.google.com/presentation/d/1xyyeMLNFFPNlMkulSb_nVvmpOZJ6OpYyE1TNsZvFyZQ/edit#slide=id.ga4b082cc16_1_0">confusing - results</a>.</td></td> - - <td><td>We committed to look again in Q3 this year, and coincidentally got - an <a href="http://crbug.com/1233544">escalation</a> from fbeaufort@ and the - Media team just in time!</td></td> - - <td><td>Brainstorming in early Q3 by mustaq@, flackr@ and rdcronin@ led us - to a solid plan, finally!</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter VI: à la carte</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>\[Scroll Unification\] Scheduling investigation</td></td> - -<td><td>skobes@ investigated on the scheduling improvements for scroll unification.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/KzoJ1wz9JNBOE4niu0yJi1m8kRTEnT7NbNJXLJnJIaZuOrjCTmHd15yxkvHBf8AVDg-S2shF3__QGBN-4Gp0N5DUot3_M3VXppGLPGpZjQ0AF911GQJZ89ZybDi3yNZWb5cgD4NZqA" height=119 width=283></td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/nE2WWtZkK69TinInED4oHRiMojIbDnoQucrmY9F3qRVTfZLC9XIg4z78xCQDfyQQlKv1z-gP6vnodL4jXpwNRARabUEeQNkRXKbrenRd4mZ3Exdy8ttXEyn6UBNcPBR4_510lAWVow" height=112 width=283></td></td> - -<td><td>Less motion, plz!</td></td> - -<td><td>Remove animations option in settings disables a lot of system animations including stretch overscroll.</td></td> - -<td><td>In Chrome, remove animations sets prefers-reduce-motion:</td></td> - - <td><td>This <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/3046841">CL</a> - plumbed prefers-reduced-motion from blink to compositor and wired it up to - input_proxy_client.cc to disable elastic overscroll (on Android - only)</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter VII: Bug Updates</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/yx34TxFllV0ep-DPg1EYjWu52FJDaFuXyFk5bjznHkSCdSVfVWputqfO3rJkZau0pzpeiexbNcpgd3QbpqNG-i-Mr9TSpOKJEv8uJk8UwvgRUMSMqdqqr3JFxcvPLzNYYzgMY42a-g" height=156 width=287> <img alt="image" src="https://lh6.googleusercontent.com/7asOshHrb-Mi9gCdsGobedpUlzBQgvlWAsLj4BSr8VDN6tZ9FuMrH4Zy2eL2vmH-IcUMXGDTYf8py1pFocLtCPnul_Ljgg-HWToEjP5V-a9VUrWKmbHm9T94Z8hrtsF7fl1yRaRuuA" height=157 width=285></td></td> - -<td><td>Our team lost a bit of ground in P2s && P3s, but kept the P1s in check.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | August 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/august-2021-vol-2---new-features-code-health-stability-security-fixes/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/august-2021-vol-2---new-features-code-health-stability-security-fixes/index.md deleted file mode 100644 index 0a80929af99..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/august-2021-vol-2---new-features-code-health-stability-security-fixes/index.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: august-2021-vol-2---new-features-code-health-stability-security-fixes -title: August 2021 (Vol.2) - New features, Code health, Stability/security fixes ---- - -<table> -<tr> - -<td>August 2021 (Vol. 2)</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Composite BG-color animation</td></td> - -<td><td>xidachen@ resolved a few problems and this feature is now close to finch on Beta. Specifically we have enabled field trial testing (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3085961">CL</a>) so all perf bots can run tests with this feature. All regressions and improvements are summarized <a href="https://docs.google.com/document/d/1Fkp7udbCgYqVtNf4gn-NXGVYamPrd_n0qKqalruTq6E/edit#heading=h.6genmqxclwba">here</a>.</td></td> - -<td><td>We have resolved the memory increase (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3088776">CL</a>). Here is an <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1238995">example</a> where a perf test used to crash due to OOM now works fine.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/BlgpoWYHjGO-GwxXaaDY5Bx0AFAp6cww8WbcxkZecQRKvkvY5tIw60xzDE6XiWEbGIzGoH7f9deTeZKU_0QNoQkLwKJzl9PGfYVYW_SI3iFnwP-9j3zQ2EWUpytmUK4qtebbkwU6_w=s0" height=47 width=283></td></td> - -<td><td>There is a performance regression (<a href="http://crbug.com/1238554">crbug.com/1238554</a>) that has been addressed as well. It was fixed by this <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3099785">CL</a> where we found that we were doing a lot of un-necessary work which slows it down.</td></td> - -<td><td>Note that the above curve has improved, but didn’t go back to the original level. With further investigation, we found that the root cause is because the tests aren’t well written. Specifically, the tests contains background-color animation on a solid-color layer, and our system has optimizations towards solid-color layer which is not implemented in CompositeBGColorAnimation yet.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/No7kJ2RfnZ3hpi1d_b0LDRdEFLDcUr-vyYLSOJode6Ie9Hz1lc5Eb1tE_seIIroBsuH0th5CDWb5D3h4DGzXOBFDYIxBzmQAyCvhEi0zdnuV5hUfXjcTm7agkTIxhL4znpgP4biLzQ=s0" height=111 width=283></td></td> - -<td><td>A <a href="https://pinpoint-dot-chromeperf.appspot.com/job/16e27f8d320000">pinpoint job</a> was started where the layer made to be not long solid-color and the above shows the result. The right column is with CompositeBGColorAnimation and we can see that it actually made a performance improvement.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/_h4jB7RpT2aAS7wMfWe_gT486MtA5VxCbyNwkZT9JN3Z4GP8bMaWrucDgES4rAxjw-SQcdoJUSgrJ7DMixmtbIc9kVCaDPGWSZ2iFK9ExmHguggBqnFXEuzggI1040MFLAKwO7AueQ=s0" height=239 width=283></td></td> - -<td><td>mehdika@ modified Element Fragment code (that already exists) to work for any other element.</td></td> - - <td><td>For now we just scroll to the element, later we will add more - features like highlight the element, etc.</td></td> - - <td><td>We use the <a - href="https://github.com/WICG/scroll-to-text-fragment/blob/main/EXTENSIONS.md#proposed-solution">following - syntax</a> and find the element with the help of QuerySelector().</td></td> - - <td><td>https://example.org#:~:selector(type=CssSelector,value=img\[src$="example.org"\])</td></td> - -<td><td>Elastic overscroll</td></td> - -<td><td> flackr@ fixed two problems in elastic overscroll.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/f60VPX4rF8xa05SmWJoUaHAyIB6tYNNOsJiT6bDIH68vIkGxrFu6P80qxYfSkQgkCxN1KavWA1Nl6-i79f-LrePYMQ1diCPvWemIgasnclYNVnqmES49Vb3OXAXruuDkhYNoxCCO6A=s0" height=271 width=140></td></td> - -<td><td>The first problem is the <a href="https://crbug.com/1241128">subtle shift in content</a> during overscroll bounce. The fix is to use ScrollTree::container_bounds which includes container_bounds_delta.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/luovHFpiZXnYWJflHP4bK1bmtxsX3if5-7Wb1n9bRMnptIcAWRvBr4bjsAjpQtM1K3JEApvhm8rZ_xBvepJsBvv_hftRmUhJUZsvhqHIHm_OVkkEMLen2WWZ6lkoyaMLSdwtalM5BA=s0" height=304 width=144></td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/S-vMAJInKPvA5rr9AV0AYucyWnksNnOyqjFuvQbDy7dXrl7Kl34d7ZEwu5h5EcVbqoGORR25GkHp3quncnezDchwCW90pLQ_RYg70bDBioUBYyqWL1zpbTuZu8c8ZoLSSrszZ0jhXg=s0" height=120 width=283></td></td> - -<td><td>Another fix is to reduce elastic overscroll stretch. Particularly, we have updated parameters in ElasticOverscrollControllerExponential to more closely match native overscroll.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Code health</td></td> - -<td><td>Native paint worklet</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/9afv77mmImR7H4z7fyr8ZS-XToIG4RhBMkejhY3AOIQUKMXWlA_ySV-EVb-NMYPjga5O-022spge9UB5YYU9CNEOY0Oec9VAL2qqmnRIDm_bTFBoprjXri3myxnLJR-gMvL-Q473BA=s0" height=166 width=267></td></td> - -<td><td>xidachen@ moved some common variables && APIs among different native paint definitions to their super class, which results in a negative line count <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3107065">CL</a>.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Stability/security fixes</td></td> - -<td><td>Elastic overscroll crash</td></td> - -<td><td>flackr@ fixed a crash in blink::ElasticOverscrollController::ObserveGestureEventAndResult.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/jzBDWMpXaZA89CHIfAgkHHbtj7ZUhGSTXZKdgHtXbrWMBeg5qnpQNg-W8tJo-ZJ1PFVVJwEF1spteUiqZZAU916zfZGTQkitaBZKNJeDnG33GUDr0_u2yZH0tWB87DvIJmbeN68bMg=s0" height=113 width=281> <img alt="image" src="https://lh6.googleusercontent.com/l1LVluQlx5yCSgI90jRXu7kapwviFAWiwQ6LLmuf49essWuTiHcwWtgLrBLAjSMxHZzzLHbHCd2UN0jlCkXQvfS6TBVeEzsEUCdDtX3GZ6gBZ1nUwXNhYHNDlMQVHJJ_vcGJ9lVUGg=s0" height=91 width=289></td></td> - -<td><td>The above shows the stack trace, which indicates that ObserveGestureEventAndResult is called on nullptr ElasticOverscrollController.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/cNwoM-2-Z2HdN09LJm6TuAH9Rr79DKL_UmMgnLhe4O0pXArSweGnVnflrGUHKj6JeckhafOcK5-YIDsiFah6HinZqgc31dCj4N9ef5GlQNEpVNxyQvRiJXqEm-Vxet4T5Aq0lNXXMA=s0" height=94 width=303> <img alt="image" src="https://lh5.googleusercontent.com/FHMh0qf5yC9jQ3ur_xkp88Gu0beOaqKMd4W8Pj9igoOa2kRaoBVANIhouGa-EKmOsU75nVrdW3yeBH5aDi6GQtz8q5mwNdrXovTda4qGKGxuxPAxgdZUxY_OFLbOrFK1YLgHQJmlRA=s0" height=101 width=261></td></td> - -<td><td>It looks like we have added check, as shown in the above. But why didn’t it crash before? It appears that the crash is from the posted task.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/baTU4Jeg3NHXIYO6WXzlHVNOW2Z0qFZ3A-zQ7Wj-osP-2nk2FG1QuLk1bf6VqOuy4QsziT0yXkLpwNpPZvf3YBRjYUodulN5EpQ2e38l0256PTmNr1kaQg2jlQF5xYlHZOJ-3f9N9Q=s0" height=177 width=367></td></td> - -<td><td>Further investigation shows that the ElasticOverscroll is now controlled dynamically by prefers-reduced-motion, so the fix is to check that too.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Interop fixes</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/hcw7zn56d5_NPAcmaJy1PaiMmtLKJul2Ze_tfE610DNIQs-wca7nZtOxOtXW-_v2i4IlpP-wyb4_zpJRm2uL2KPlUEGdciq-POm2T7UwR4dcwUyuFeOtLPomHUtDd8TvyNXOqHC1lA=s0" height=236 width=264></td></td> - -<td><td>skobes@ fixed a <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1114794">bug</a> where scrollTo doesn’t abort mouse wheel scroll animation. The solution is to cancel impl-side scroll animation when we get a programmatic scroll. This also fixed a bug in scroll unification.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | August 2021 (Vol. 2)</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/february-2021-new-features-testing-stability-fixes-code-health-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/february-2021-new-features-testing-stability-fixes-code-health-and-more/index.md deleted file mode 100644 index 4793c050ece..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/february-2021-new-features-testing-stability-fixes-code-health-and-more/index.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: february-2021-new-features-testing-stability-fixes-code-health-and-more -title: 'February 2021: New Features, Testing, Stability Fixes, Code Health and more!' ---- - -<table> -<tr> - -<td>February 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New Features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Content-visible CSS animations & transitions</td></td> - -<td><td>kevers@ has been working on this feature and fixed some problems.</td></td> - -<td><td>Problem 1: Wasteful to run animations on hidden content (content-visibility hidden or auto + offscreen). </td></td> - -<td><td>Problem 2: Wasteful to check each frame if the conditions apply.</td></td> - -<td><td>Solution:</td></td> - - <td><td>Document has some global state for display locks.</td></td> - - <td><td>Added time of last lock update</td></td> - - <td><td>Use time of last lock update to determine if locally cached lock - state is stale.</td></td> - - <td><td>Unblocks remaining steps in developing the feature. (<a - href="https://docs.google.com/document/d/1Enj8nD-y2vgCp2A6-M2QFoUKf1-nxMX023ervOoXi50/edit?usp=sharing">Design - doc</a>)</td></td> - -<td><td>Composite background-color animation</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/T329-TOc6C-VtU5u5Dry6zo-250r722wLDaPyE7QrioBJWEzmLezgu9OpHZP3X7Us9GSJc-0L2bcU2IABFNziUPI-wl19ECPiL0rcAHy1CSMFKq0vArDbw4qlOG8Q_amwpp9JFUXfN1CK0ibHfhXywQO6xl-YjWk7q99dff4MSE34Y9R" height=203.57052631578944 width=217.23208556149734></td></td> - -<td><td>xidachen@ landed some CLs to complete the implementation for this feature, and then started a finch experiment.</td></td> - - <td><td>The first finch study had a lot of crashes, xidachen@ <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2675160">landed</a> - fix for that.</td></td> - - <td><td>The second finch try crashed a small number of users, xidachen@ <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2692609">landed</a> - fix.</td></td> - - <td><td>Currently, there are two known problems, and we are actively working - to resolve them.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Animation Validation</td></td> - -<td><td>xidachen@ worked on validating main-thread animation detection logic, as part of the core web-vitals effort.</td></td> - - <td><td>Here is a <a - href="https://docs.google.com/document/d/1iz0YdNKHpcObTe3UrM7uY6fsGv8xOlwY35m5dZzIoR8/edit">doc</a> - that describes how to detect different types of main-thread animations from - traces. And here is a sample <a - href="https://drive.google.com/file/d/1IdObZMCYRMraUIYcM5RSQo2L9u2Uhqw9/view?usp=sharing&resourcekey=0-rTeQ2zu0ajWxMtGGhFAKng">video</a> - of output.</td></td> - -<td><td>Impulse animations</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/28lZWBVSb1BQHulAMjKveaDG9I3uaNXJzPzD5ZdwTS2KhNWn85CZdnDZL-e_f2P6BT1PLiIYvCw6nzpmFsCmiKtJsEwBWBJhxctZDOb4-U16TuvW6j5ursJPg7H0T5EEiGztd1LShDKjzfIs02ulLhPAVhJAV_Ydrsj1lSQzPV7KB5VO" height=92 width=134> <img alt="image" src="https://lh4.googleusercontent.com/3SRHx6N3NrBhVlYRrGv_d70qwqH_zQyQL_0PXr2D3HI4tTRXYr8RzirbqcOKtBj6Xg4TPfWZtwwUfSk8nNekZ8Yi5CSkiqDta1-I3bpSBpn0MRo8OYXnQPrWbXp8cCK6NSULireHlRgvC-7ji80BER6HBB12jqNgaVproz-4RXMykV7Z" height=90 width=133></td></td> - -<td><td>flackr@ supported <a href="mailto:arakeri@microsoft.com">arakeri@microsoft.com</a> to implement this feature, which has a faster initial impulse when scrolling. This is shipped in M90.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Click/Auxclick as pointer event</td></td> - -<td><td>liviutinta@ made some great progress in this sprint.</td></td> - - <td><td>Bug hunting - no bugs identified.</td></td> - - <td><td>Expanded finch experiment to 10% stable.</td></td> - - <td><td>Landed Accessibility click <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2679278">CL</a>, - part of which was relevant to Click as pointer event.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Testing</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Deflaking tests</td></td> - -<td><td>In order to fix some flaky tests, kevers@ made some changes to gesture_utils.js. Work was already underway to replace use of waitForAnimationEnd with waitForAnimationEndTimeBased. </td></td> - -<td><td>The problem with the former method is that the timeout is expressed in animation frames and for our fast tests these trigger every 1ms instead of the usual 16ms. </td></td> - -<td><td>The later method is a step in the right direction, but tends to flake when test machines are under load. The reason for this is that the timing starts when the gesture event is queued and not when scrolling begins. Also, since we snap after the initial scroll completes, we are queued up a second smooth scroll, which can timeout while queued. </td></td> - -<td><td>A third approach, waitForScrollEnd, is being introduced to address these problems. This method can also deprecate the waitFor method (same timeout issue as waitForAnimationEnd). By using scroll events, we avoid flakes due to queuing delays and handle chaining of scroll events better, while at the same time tests complete faster by avoiding unnecessary waits once the target position has been reached. </td></td> - -<td><td>TestDriver Action API</td></td> - -<td><td>lanwei@ kept improving the TestDriver action API and made more WPT tests automatic.</td></td> - -<td><td>The following two pictures show the wpt dashboard for the TestDriver action API.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/N4_vKH1JiDu3pf13Ng6QfmjemCO1fSzV_QyfO6vHmB_AnaWTK8SPDoiLYag3lmb5FfmQfbW_4rdzbZiccNbQlv1j-JKigVmajoNNXbNciRwh1isPOfOTDfanvP6vcaHCq9VBtFWGMe-1l7CsDqDQuk4jWp_ROYO2R5Ah1u3sxcpLJcVK" height=102 width=140> <img alt="image" src="https://lh6.googleusercontent.com/vH3v_xKD--xwrrRcy4UosP2hEkBrVoK9WXRRZ5rAqIhi8vzlhN9COtKbNXeOkcXk5BvTNELRXJQlxVmk0rOlcDlvOkO2y_zN7AJZ3hiJBimD7R--jjIx9x1D9B7YMrHp32x4VY966SH9cKbaFhZOgeRYn3gXMPlyQBc8d5Q85ie5FQm5" height=71 width=135></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Stability Fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Fixed crash in set current time</td></td> - -<td><td>xidachen@ fixed a crash when the timeline time is Infinity or -Infinity and that timeline is attached to an animation. The solution is to special case when the current time is Infinity or -Infinity.</td></td> - -<td><td>Fixed crash in null animation timeline</td></td> - -<td><td>The problem occurs when we set an animation timeline where its previous timeline is null. xidachen@ resolved this by loosing the condition of some DCHECKs to ensure that we can handle the case where the previous timeline is null.</td></td> - -<td><td>Prevent user from exiting fullscreen</td></td> - -<td><td>mustaq@ fixed this issue which has complicated initial repro and that misguided our initial investigation. mustaq@ spent hours to narrow down the root cause, and it is due to the print dialog on another tab halts the main thread. Moreover, now we have a minimal repro of 12 lines of HTML + JS.</td></td> - -<td><td>Fixed crash length interpolation</td></td> - -<td><td>The crash happens when the “from” and “to” value of the interpolation is interpreted as Infinity. xidachen@ fixed it by only DCHECKing when the interpreted value is finite.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Code Health</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/jyVUQx4WQb7YDctRAjafGXZE-w7qxcUmoGFWxzW_ujPxx7YlWgKFZiF_Y982jngBopZsRX-hW70W5fDTdXcAhFwTWa15TZ8Tq-29VLl2PmiCu1FQE1DnoXfcatmbzlq1c_YqpaKuOf2gV2UeZ2MkJ47vkjPsi3xKxRAMjC7YZPJkG869" height=152 width=282> <img alt="image" src="https://lh3.googleusercontent.com/wEPBpfUYaObQqvjrBwCsfE7sIQ0bSJTIUS0345K6O9QICMbn1PPbIQdu0d8ApDFGSqUWPgPt43sJ8EweAgRR2o1Wt9OZWSOK5bO5uWMkyfu8njZ5nFa_DK5VLudJBfcSffh8AW2oYLJ2_RExeqCndVT4yyhNfwWGnqRxKRqwXNrGEvK5" height=152 width=278></td></td> - -<td><td>Our team holds ground on P1 bugs. In terms of bug tracking, we switched the y axis from “issues” to “bugs”, which more accurately reflects goals to improve product excellence.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Miscellaneous</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Tabs</td></td> - -<td><td>girard@ started this Tabs <a href="https://docs.google.com/document/u/0/d/18C_W5SRsuPfCyyXbEsCjiHOGc8OWJXRlKvKKN-rlYsQ/edit">One-Pager</a>, and a lot of people are contributing to it now.</td></td> - -<td><td>flackr@ and nsull@ took a first pass at an <a href="https://docs.google.com/document/d/1HcQ75iRhO-dT7EHB6JrjmMATa9XlSCYZKWrXbzakexQ/edit?resourcekey=0-kYHpL3r3jY3Q8wtTaOa6aA">explainer</a>.</td></td> - -<td><td>Disable double tap to zoom for mobile viewport</td></td> - -<td><td>liuviutinta@ has a <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2679278">CL</a> in review, and still working on writing tests for Andriod.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Accessibility click indistinguishable from real click</td></td> - -<td><td>liviutinta@ landed a <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2679278">CL</a> to fix this <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1150979">bug</a>. The fix included:</td></td> - - <td><td>Added pointer events up/down.</td></td> - - <td><td>Populated mouse events coordinates appropriately.</td></td> - - <td><td>Cleaned up the code by using SimulatedClickCreationScope as argument - for <a - href="https://source.chromium.org/chromium/chromium/src/+/HEAD:third_party/blink/renderer/core/dom/element.h;drc=763c071aa91f87c5e404edff98bc5bac8075d4a1;l=600">Element::AccessKeyAction</a> - instead of bool send_mouse_events to clarify where the simulated click - originates from</td></td> - - <td><td>Added wpt tests for clicks from accesskey and clicks from - enter/space keys to ensure interop</td></td> - -<td><td>Pointer lock: pointerrawupdate coordinate jumps </td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/5O-XkmmvjyGYYQDme-3cP1Jgn2AjV2DE7szj47ylMZKvthruyejkLyCsC5XlO_CafCOkJVrVrD1dkPGjXfrxgZ7JigZFxv4A_su8UR_EldHtTJQ5fdDWJv2t8bhe5WYWeBMIymwE7cmXdr23S_Xtvyl1xon4aJEVoPOV5xTvPXd1RrA6" height=224 width=247></td></td> - -<td><td>musta@ discovered a regression due to a code “improvement”.</td></td> - - <td><td>In the code shown above, the Create() function does more than what - the name applies!</td></td> - - <td><td>Regression has been fixed, a test has been added.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | February 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/index.md deleted file mode 100644 index 8c71dba5c6f..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/index.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -page_name: highlights-archive -title: Highlights Archive ---- - -This page contains an archive of previous Chromium Animations team highlights. - -[February 2022 -highlights!](https://docs.google.com/document/d/1l_zGo07HRoj1ffvrc4VQKh4q1oI-qx6N1jnuc_abIXY/edit?usp=sharing&resourcekey=0-u6ySQmvFaOB3vs9nHtA3Fg) - -[January 2022 -highlights!](https://docs.google.com/document/d/1LGl_0kpUKsvX17sJOn-0hXuVDGZRpxit481FpkCIXS0/edit?usp=sharing) - -[November 2021 -highlights!](https://docs.google.com/document/d/1s1gbZ_2LZEM_-HJtv8W_15hzWzuVVMlSMdli5JKW8yI/edit?usp=sharing&resourcekey=0-o0n9VKkG9jC_WsFGx0GDaA) - -[October 2021 - 2 sprint's worth of -highlights!](https://docs.google.com/document/d/14hFArq_0KHZ9HncBpiMR8RF_a7wEl-hvWob5DIgWqvc/edit?usp=sharing) - -[September 2021 - New features, testing, code health, interop fixes and -more!](/teams/animations/highlights-archive/september-2021---new-features-testing-code-health-interop-fixes-and-more) - -[August 2021 (Vol. 2) - New features, Code health, Stability/security -fixes!](/teams/animations/highlights-archive/august-2021-vol-2---new-features-code-health-stability-security-fixes) - -[August 2021 - New features, fixit, testing, code health and -more!](/teams/animations/highlights-archive/august-2021---new-features-fixit-testing-code-health-and-more) - -[July 2021 - New features, fixit, stability/security fixes, interop fixes and -more!](/july-2021---new-features-fixit-stability-security-fixes-interop-fixes-and-more) - -[June 2021 (Vol 2) - New features, stability fixes, Interop fixes and -more!](/teams/animations/highlights-archive/june-2021-vol-2---new-features-stability-fixes-interop-fixes-and-more) - -[June 2021 - New features, stability fixes, Interop fixes and -more!](/teams/animations/highlights-archive/june-2021---new-features-stability-fixes-interop-fixes-and-more) - -[May 2021 - New features, Testing, stability fixes, Interop fixes and -more!](/teams/animations/highlights-archive/may-2021---new-features-testing-stability-fixes-interop-fixes-and-more) - -[April 2021 (Vol. 2) - New features, Testing, Stability fixes, Interop fixes and -more!](/teams/animations/highlights-archive/april-2021-vol-2---new-features-testing-stability-fixes-interop-fixes-and-more) - -[April 2021 - New features, Testing, Stability fixes, Interop fixes, Metrics and -more!](/teams/animations/highlights-archive/april-2021---new-features-testing-stability-fixes-interop-fixes-metrics-and-more) - -[March 2021 - Fixit week, New features, Testing, Interop, Metrics and -more!](/teams/animations/highlights-archive/march-2021---fixit-week-new-features-testing-interop-metrics-and-more) - -[Feburary 2021 - New Features, Testing, Stability Fixes, Code Health and -more!](/teams/animations/highlights-archive/february-2021-new-features-testing-stability-fixes-code-health-and-more) - -[January 2021 - New Features, Testing, Stability Fixes and Code -Health!](/teams/animations/highlights-archive/january-2021---code-health-new-features-testing-and-stability-fixes) - -[October 2020 - Code Health, Scroll Timeline, Synthetic User Activation, Scroll -Unification and -more!](/teams/animations/highlights-archive/october-2020---code-health-scroll-timelines-synthetic-user-activation-scroll-unification-and-more) - -[September 2020 (Vol. 2) - Code Health, Logical Property Animation, Off-thread -PaintWorklet, Capability Delegation and -more!](/teams/animations/highlights-archive/september-2020-vol-2---code-health-logical-property-animation-off-thread-paintworklet-capability-delegation-and-more) - -[September 2020 - Code Health, Animation Timelines, Smoothness Metrics, -Animation event handlers and -more!](/teams/animations/highlights-archive/september-2020---code-heath-animation-timelines-smoothness-metrics-animation-event-handlers-and-more) - -[August 2020 - Code Heath, Animations, Context Menu and -more!](/teams/animations/highlights-archive/august-2020---code-health-animations-context-menu-and-more) - -[July 2020 - Animations Documentation, Throughput Metrics, Code Health, -Capability Delegation, User Input Security and -more!](/teams/animations/highlights-archive/animations-documentation-throughput-metrics-code-health-capability-delegation-user-input-security-and-more) - -[June 2020 - Web Animations, Scroll-linked Animations, Throughput Metrics, -Scroll unification, WebDriver, Pointer Events and -more!](/teams/animations/highlights-archive/june-2020---web-animations-scroll-linked-animations-throughput-metrics-scroll-unification-webdriver-pointer-events-and-more) - -[April 2020 - Web Animations, Scroll-linked Animations, Throughput Metrics, -Performant Meet, Hackathon and -more!](/teams/animations/highlights-archive/april-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more) - -[March 2020 - Web Animations, Scroll-linked Animations, Throughput Metrics and -more!](/teams/animations/highlights-archive/march-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more) - -[February 2020 - Web Animation, Scroll-linked Animation, Snap after layout, -Throughput metrics and -more!](/teams/animations/highlights-archive/web-animation-scroll-linked-animation-snap-after-layout-throughput-metrics-and-more) - -[January 2020 - Off-thread PaintWorklet, Web Animation, ScrollTimeline, Virtual -Scroller, ScrollSnap and -more!](/teams/animations/highlights-archive/january-2020---off-thread-paintworklet-web-animation-scrolltimeline-virtual-scroller-scrollsnap-and-more) - -[Nov & Dec 2019 - BlinkOn, ScrollSnap, Lottie, HitTesting, VirtualScroller, -WebSharedLibrary, WPT and -more!](/teams/animations/highlights-archive/nov-dec-2019---blinkon-scrollsnap-lottie-hittesting-virtualscroller-websharedlibrary-wpt-and-more) - -[October 2019 - Microtasking WebAnimations, Frame Throughput metrics, Group -Effect polyfill and more!](/teams/animations/highlights-archive/october-2019) - -[September 2019 - TPAC 2019, Scroll Timeline polyfill, Paint Worklet launch, -team changes, and more!](/teams/animations/highlights-archive/september-update) - -[August 2019 - Viz hit-testing false positives, code-health projects, counting -CSS properties, and more!](/teams/animations/highlights-archive/august-2019) - -[July 2019 - GroupEffect, color interpolation, Viz V2 hit-testing heading to -stable, and more!](/teams/animations/highlights-archive/july-2019) - -[June 2019, Volume II - Spooky bugs, prototyping ScrollTimeline, better bezier -curves, and more!](/teams/animations/highlights-archive/june-2019-volume-ii) - -[June 2019 - Lottie renderer, jump timing functions, scroll-snap-stop and -more!](/teams/animations/highlights-archive/june-2019) - -[May 2019 - shipping more of Web Animations, jank-free PaintWorklet animations, -and more!](/teams/animations/highlights-archive/may-2019) - -[April 2019, Volume II - Lottie animations, stateful Animation Worklets, and -more!](/teams/animations/highlights-archive/april-2019-volume-ii) - -[April 2019 - an update on PaintWorklet, performance improvements in Viz V2 -hit-testing, and more! ](/teams/animations/highlights-archive/april-2019) - -[March 2019 - better transform animations, AMP origin trial updates, and -more!](/teams/animations/highlights-archive/march-2019)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/january-2020---off-thread-paintworklet-web-animation-scrolltimeline-virtual-scroller-scrollsnap-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/january-2020---off-thread-paintworklet-web-animation-scrolltimeline-virtual-scroller-scrollsnap-and-more/index.md deleted file mode 100644 index 2cc22e02d4a..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/january-2020---off-thread-paintworklet-web-animation-scrolltimeline-virtual-scroller-scrollsnap-and-more/index.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: january-2020---off-thread-paintworklet-web-animation-scrolltimeline-virtual-scroller-scrollsnap-and-more -title: January 2020 ---- - -<table> -<tr> - -<td>January 2020</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh3.googleusercontent.com/YUOJZ1fWnO_xlHUDQwtYmpu-WxSH85_WGBxALF-sBbEKcuUmU9kYfM4n0HgfL9dLAQh9rm8CniR3f8MN1zSSq26Q-PQ1J2bur6eQSOWYbGIMri6MpQzwUutY8bN9tvF-fmYqG_fm" height=254 width=579></td> - -<td>Off-thread PaintWorklet shipped!</td> - -<td><a href="https://developers.google.com/web/updates/2018/01/paintapi">PaintWorklet</a> is a great example of Houdini's value offering, allowing developers to build complex yet compartmentalized controls like <a href="https://googlechromelabs.github.io/houdini-samples/paint-worklet/qr-code/">QR code generators</a>, <a href="https://googlechromelabs.github.io/houdini-samples/paint-worklet/ripple/">Ripple effects</a>, <a href="https://googlechromelabs.github.io/houdini-samples/paint-worklet/circle/">Custom</a> <a href="https://googlechromelabs.github.io/houdini-samples/paint-worklet/parameter-checkerboard/">background</a>, <a href="https://googlechromelabs.github.io/houdini-samples/paint-worklet/diamond-shape/">custom shape elements</a>, <a href="https://googlechromelabs.github.io/houdini-samples/paint-worklet/border-radius-reverse/">custom border effects</a>, etc. Off-thread PaintWorklet moves these effects off of the main thread, ensuring jank-free performance even under load. After a year of effort, Xida (xidachen@) proudly drove the feature to completion and turned it on by default in M81 on behalf of Rob (flackr@), Stephen (smcgruer@), Ian (ikilpatrick@) and the Animations team. The <a href="https://twitter.com/slightlylate/status/1225102256053182464">gif above</a> shows how the popular Lottie animation library is adapted to use PaintWorklet. Do pay extra attention to what happens when we inject artificial jank! There are a few caveats which will be addressed soon: it currently <a href="http://crbug.com/1046039">requires</a> will-change: transform etc to force a compositing layer and the animation <a href="http://crbug.com/1049143">must</a> start after the PaintWorklet is registered.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/NvUQu5IYtvdtY7R45QmkSgu3nQeN-09U0OevkZGYHxYzevW-kSTXG9OWwvm5l_F6YIHpmeEvfRrhjjlyUSObcRycnh6E8ujOPZxY6aSXV65PUj8PkIqaz_0Q1HkEmlK-O2Cj-WP0" height=166 width=292></td></td> - -<td><td>new animation created every mousemove</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/GvvT0tEqot8b8GNtWYK1gT4WAMuj2CInVNIoIKDYPYj0Y6W8Vrlj77L6vDKJ2As-oYs0NzTKc5BIAjU7bE3qR2zf9DdqoErxUPJvT3a0jnNyrOZM9cgNXqkR1ZIZpDE7CP3FySRb" height=166 width=265></td></td> - -<td><td>finished animations automatically replace older ones</td></td> - -<td></tr></td> -<td></table></td> - -<td>Support replaceable animations</td> - -<td>When a fill forward animation finishes, it remains in effect. If enough of these animations build up, they can negatively impact performance and leak memory. e.g. with the following code snippet we would create one animation per mouse move over and over until the memory runs out (left gif).</td> - -<td>document.body.addEventListener('mousemove', evt => {</td> - -<td> const animation = circle.animate(</td> - -<td> \[ { transform: \`translate(${evt.clientX}px, ${evt.clientY}px)\` } \],</td> - -<td> { duration: 500, fill: 'forwards' }</td> - -<td> );</td> - -<td>});</td> - -<td>Our team has worked closely to introduces a <a href="https://drafts.csswg.org/web-animations/#replacing-animations">solution</a> for this in the specification in the form of replaceable animations. This sprint Kevin (kevers@) implemented replaceable animations to tackle the issue. With this effort, animations that no longer contribute to the effect stack will be removed once they are finished (right gif). No more memory leak and performance degradation. YaY! See the <a href="https://www.chromestatus.com/feature/5127767286874112">I2P</a> for more details.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/4qcWWtrg9phgX7dhxKdmlxP3U954Xmql0JSasLQXOyQIMhPCu7S-JFaJoJNsJJucARKfOZxd6wXs45LxzPdQw70EiT_Om0Y6MXhMeBwjjr8xPVCppUvkpgteZUsB02lq2M4fgVNy" height=157 width=290></td></td> - -<td><td>--wpt_failure</td></td> - -<td><td>Kevin, Hao (haozhes@) and George (gtsteel@) made awesome progress towards shipping Web Animation this sprint. 78 previously failed tests now pass.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/Uyg0fdPdGq6ODnXLgjZGnmNCFS5pO9P1ddwD01GGPmarYHpy_e84ZPhlbtVRtWC7LpelF30LzhyQU_-kTye4-vaiAAQ-yGrYnxBV_5GLRKWC7y4GABOXm9HvhTndtw1eM-GqawOt" height=163 width=292></td></td> - -<td><td>Throughput metrics</td></td> - -<td><td>Frame throughput is designed to measure the smoothness of Chrome renderer, which reflects the performance. In the past weeks, Xida, Rob and Sadrul fixed a bug where a large number (~20%) of Canary users reported 0% throughput. The fix was landed right before M82, and now the number has dropped to ~1.6%. As a result, the 20% users with the worst throughput now report ~23% in M82 (green curve) compared to ~0.95% in M81 (red curve).</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/9PzpLhk5NoA-WWwcSA57_H8WhpxEcniJ2gBW2tScCrN5W3wNJDcuRMkRBANs4zxTCEd7HNYlfjlBsCF8Np7lWldJzxPus9LxZRbbYSyuqKN7QjpzFDirgGFZ9f_SzlydnxHhmolG" height=144 width=137><img alt="image" src="https://lh4.googleusercontent.com/Lrl4uTP7YZpFBi4-ni3PQBrE59h_4a3d05jelqPXpmLBPLg2CCvAwvXYGb9r4azaCvrRU9SgCR1gaQrj8sQxyZcoJo32WfYdQkj45nnSA58IjkmvoLwvrCfebksvFAuYmb1ykRAb" height=141 width=135></td></td> - -<td><td>++scroll_snap_after_layout_robustness</td></td> - -<td><td><a href="https://docs.google.com/presentation/d/1WUa6nFfkzXm2O1V70hr49vPFP4TOAbUh2q8fppkybJs/edit#slide=id.g6c0755777a_4_441">Scroll snap after layout</a> frees developers from forcing a re-snap after layout changes with JavaScript. Yi (yigu@) fixed a ship-blocker this sprint, i.e. transform inducing resnap, and turned the feature on by default in M81!</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/nap0TfLZVJKZObpmhgBK24I9qfmyZz9SI4qKnGtFidKd0xQqOs025U1QPHJNazzGMWNnb-eK0iMFkAx82mFuETIEj7IQISFkoPoPCcO-DydKrwAXVQY_DGhB2PgpEGUp1t6yOiAr" height=135 width=124><img alt="image" src="https://lh3.googleusercontent.com/8I7tcRP5Nc4yU9FX1zwGwzjmTN67a7oCVh9VZkzT6sMUTtsaAc3fDlj5wuBFntOnn6X6b84H9XZqfmH47bQDtML1njBCKZkpCCTUeSARKAgTF2yRj44VSaCOScdFADHqfxDn1p0q" height=161 width=145></td></td> - -<td><td>Free animations from pending state</td></td> - -<td><td>When there are composited animations in the process of being started, we used to defer the start of main thread animations in order to synchronize the start times. This process could lead to main thread animations getting stranded in the pending state if composited animations are being continuously generated (left “gif”). With Kevin’s excellent work, main thread animations queued up in a previous frame no longer get blocked waiting to synchronize with fresh composited animations (right gif).</td></td> - -<td></tr></td> -<td><tr></td> -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Virtual Scroller</td></td> - -<td><td colspan=2><img alt="image" src="https://lh6.googleusercontent.com/4V1EVsDDGrmPaAcKIvuQU3aCOU-3uycfFi91_Zso6_sMqJ5tfnoeoiCpXaXAAe9kuHa-xITdMgGR9Q9VjVIIlP-OC35-nGF1itJPN4bE05vlDpLVMMDSaC9rlcRTJSn846di0PI9" height=216 width=276><img alt="image" src="https://lh3.googleusercontent.com/rP5n2ImsLCT49zKMIU8Z_oqbyj9QbHqn3roRV94A0Kgi1_3y3V3PhOlwKugvbpfASuL8RGt-yktBhma9YVl1sxJBCTkRz7Mq6gMuBdvIo7nYD1aO3rGFaB_4oH28MYDQU9hqpMVX" height=216 width=280></td></td> - -<td><td colspan=2>Rob worked with Vlad’s (vmpstr@) viewport activation, created a simple version of virtual scroller which exposed a <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1043674">scrollbar drag instability bug</a> (left). This was initially an open design problem - changed content sizes changes the scroll bar position and track length. While scroll anchoring keeps the current content visible the next drag tries to go back to the absolute position on the scrollbar. Rob applied a simple solution (right) - consistent with scrollers which load more content - treating scrollbar dragging as a delta from current position. To find a general solution, he started a <a href="https://github.com/WICG/display-locking/issues/109">discussion</a> and came to a tentative idea of locking the scrollbar area when drag starts.</td></td> - -<td><td colspan=2>Scroll-linked animations</td></td> - -<td><td colspan=2>The Animations team has been collaborating with Microsoft engineers towards shipping scroll-linked animations . This sprint we made solid progress on both standardization and implement work. Olga (<a href="mailto:gerchiko@microsoft.com">gerchiko@microsoft.com</a>) drove a <a href="https://github.com/w3c/csswg-drafts/issues/2066#issuecomment-568565738">discussion</a> with spec owners to settle some key concepts w.r.t. inactive timeline. She also made ScrollTimeline a first class citizen in AnimationTimeline. i.e. we now schedule frames for scroll linked animations only when scrolling changes instead of ticking them on every frame regardless. Yi did some fundamental refactor work on cc side and prepared to integrate ScrollTimeline with cc::Animation.</td></td> - -<td><td colspan=2><img alt="image" src="https://lh3.googleusercontent.com/wjWoc8_v9g3xloeJG_hM20QMJTS7O0Ge5wwCu8z1hsbHQJPRs-aHcRzNuLIsm6aXO66S9BReqtvmsrc2O9xauzcPQ0ThsstMKabq-GS3Eq99cNQswP-JwW_n_UOwO_UogX1m9Ml7" height=389 width=580></td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | January 2020</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/january-2021---code-health-new-features-testing-and-stability-fixes/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/january-2021---code-health-new-features-testing-and-stability-fixes/index.md deleted file mode 100644 index 39463ad6b33..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/january-2021---code-health-new-features-testing-and-stability-fixes/index.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: january-2021---code-health-new-features-testing-and-stability-fixes -title: January 2021 - Code Health, New Features, Testing and Stability Fixes ---- - -<table> -<tr> - -<td>January 2020</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New Features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll timeline polyfill</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/wDUAhebw0vhXO9C35VZA1VuJY-pNYDGPaurAXLhap5vN_7mmeaAKs1Bv1feGheZzowhF0Q8pJAb0gBZq5pC7V9msHgBd4Xww5X6xOMjgvPOon7w_fCLXfyNDK5anNuG63XGj3jCg0g" height=175 width=280></td></td> - -<td><td>Both kevers@ and flackr@ have been working extensively on this feature.</td></td> - - <td><td>Over 93% pass rate on the scroll timeline tests.</td></td> - - <td><td>Over 350 passing tests.</td></td> - - <td><td>Recent areas of development:</td></td> - - <td><td>Extended the scope of the polyfill:</td></td> - - <td><td>EventTarget</td></td> - - <td><td>Promises</td></td> - - <td><td>Tasks</td></td> - - <td><td>Support writing modes</td></td> - -<td><td>Compositing percentage based transforms</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/s0yra2ZzXVDUViwMExbnMhRNT-wV5_1XN3BjCLKg8CahRv4X29TbHcZBvZ7hWBBEH-Bv31nuoQtG6Hj685Lxe8xNljDtpH-vB-C4Y07nh2v_T1nsUEqX-ZOb5MxJNmWY1MqQ6l9vVg" height=172 width=225></td></td> - -<td><td>menu.hidden { transform: translateX(-100%) }</td></td> - -<td><td>kevers@ re-enabled this feature in M89:</td></td> - - <td><td>The challenge is that size dependency could change while the - animation is running. And we need to catch the change and restart the - composited animation.</td></td> - - <td><td>The feature is in common use. One can write CSS only animations - without the need to resort to JS for size calculation, such as the above - demo.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Aspect ratio interpolation</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/J2Ao_wP4zetydT84MzFOI9sBrfbjXjfYsIwOwspHUn-66j0reQlqj_8CnMYqoJpYsU7sc4Gpmsi1PpDmdXhcsjE20NzhYkpDs1vcCLkEhc13WG27wY9ThX3B36qJ0Af3Yvh32foVGw" height=111 width=132> <img alt="image" src="https://lh4.googleusercontent.com/Jk1F0TdSK1OjQuphK-Z-h8sE-mB2beGCnzTRCU8VHcIkHwkqn7G_vps1dj4JPAgMR1M0FDGYEUvjrTAdu5c8vB5mf1hLCshite8C66pKVJNF0cVqHWvDJTdQfK3oy5So2iheBH1erw" height=110 width=141></td></td> - -<td><td> <a href="https://output.jsbin.com/niyuref/quiet">Demo</a> Before <a href="https://output.jsbin.com/niyuref/quiet">Demo</a> After</td></td> - -<td><td>flackr@ implemented aspect ratio interpolation, and enabled it by default in M90.</td></td> - - <td><td>Recent spec <a - href="https://github.com/w3c/csswg-drafts/issues/4953">discussion</a> - decided that aspect ratios should be interpolated by the log of their value, - to preserve the same visual speed whether they are wide or narrow.</td></td> - -<td><td>Composite background-color animation</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/Cr89iFEq8k2axei93_YW0wmhvqmaiXE4XaIF50OVncHHUZqcDP23r2TeDsnSP_2nzuqP4_1N0gUqTIBoRPW0cS_ccxgsE5f3pY3wHJ2_0bWDDANBgbfsm4RBfZjLY-pnX9X3JnKGaQ" height=203.57052631578944 width=217.23208556149734></td></td> - -<td><td>The above background-color animation <a href="https://output.jsbin.com/xocoroh">demo</a> runs on the compositor thread with the experimental flag. xidachen@ has made great progress on this feature, including:</td></td> - - <td><td>Setup infra for animating on the compositor thread.</td></td> - - <td><td>Implement the interpolation logic.</td></td> - - <td><td>Handle transition keyframes.</td></td> - - <td><td>Handle multiple offsets in keyframes.</td></td> - - <td><td>Implement main-thread fallback logic.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Click/Auxclick as pointer event</td></td> - -<td><td>liviutinta@ and mustaq@ co-worked on this feature and shipped it to stable. Here is the major work:</td></td> - - <td><td>Finch experiment: 50% on canary + dev + beta.</td></td> - - <td><td><a - href="https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/bta50W_Hg24">Intent - to ship</a> has been approved with 3 LGTMs.</td></td> - - <td><td>Enabled for stable at 1% starting with M88.</td></td> - - <td><td>Improvement of the feature is still on-going, such as the <a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1150979">simulated - clicks</a>.</td></td> - -<td><td>Capability delegation with payment request</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/5MDu8JUMJOsu95kCUwcMhSlfw5kd8uU6vwXSDPG_ycd6mSBoDWnU-EfRY9ssODQuDPXG3C076zhHaO_OrmqKJK-uwzAG41pCoLJJ-1SGmahYvrK_v0JbkUm4-1zVRiqFtEUOrOghyg" height=194 width=256></td></td> - -<td><td>mustaq@ built an initial prototype that allows PaymentRequest in subframe provided a token is passed into it. The PaymentRequest now consumes user activation.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Scroll unification</td></td> - -<td><td>liviutinta@ kept working on this feature, and has made progress.</td></td> - - <td><td>Landed <a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1113863">scrolling - the <select> popup</a>.</td></td> - - <td><td>Designed <a - href="https://docs.google.com/document/d/1w_Pr4sKPXfHz03ZUxVSZL23xjQy-TiKAKf8rmbcW1Fc/edit#">metrics</a> - for scroll unification and LGTMed by the metrics team.</td></td> - - <td><td>Landed scroll bubbling from OOPIFs to ancestor frame</td></td> - - <td><td>Schedule frames for popup widgets in tests using compositor - thread.</td></td> - -<td><td>Scroll to images (and videos)</td></td> - -<td><td>flackr@ has created and uploaded the <a href="https://github.com/WICG/scroll-to-text-fragment/blob/master/EXTENSIONS.md">explainer</a> for this feature.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Testing</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Deflaking tests</td></td> - -<td><td>kevers@ addressed some test flakes in animations and scroll-snap. These flakes were largely triggered due to common gotchas like antialiasing, floating point precision, or test timing. </td></td> - -<td><td>Animation timing checks have been updated to accommodate 1 microsecond accuracy. This fix was not a pure test change as there was a lurking issue with numerical precision and setting the finished state of an animation. It is not just strict equality checks that are problematic when working with floating point numbers.</td></td> - -<td><td>Several layout tests in animations make use of an internal pause for testing API, which predates and is largely deprecated by the web animations API (WAAPI). One test flake was addressed simply by switching over to WAAPI. </td></td> - -<td><td>Several timing flakes were fixed in scroll-snap tests, by injecting a listener for scroll events. Unlike web animations, scroll animations do not fire an event to indicate completion of the scroll operation, and the end is inferred based on an absence of position updates over time. Unfortunately, this can lead to flakes when testing machines get bogged down and tests start running slower than expected. Simply waiting on an initial scroll event before starting the countdown, largely addresses this type of flake in scroll-snap tests. Once scrolling starts, the number of animation frames (rAFs) required to complete the scroll has a strict upper bound.</td></td> - -<td><td>xidachen@ also fixed quite a few paint worklet flaky tests by using the standard animation API. </td></td> - -<td><td>Before: we are taking a screenshot at rAF, which doesn’t guarantee the start of the animation.</td></td> - -<td><td>Now: with the animation ready API, we take a screenshot when the animation has started which prevents the flakiness.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/Dx0Odk5DcCkNfcAetXSysZmPSIIcC198hA3S56TcCbGBm2hLF1Tn-gBC4fuzitR4kSWVmBzblZcL5g9Pwq1XHcJ3pZhcho-i99oSHnJ5NRSbJnw79M6TgXSoZzfisUJnm6AgeLyWcg" height=72 width=283></td></td> - -<td><td>Before</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/FDMhgeEl1cuWOajwHO1P7dzgH09IAE06j0e_vGeUbyAXBa3jOc7xvfLBmcYwSsnNZUb9r0vjQhSn_m4VQGStucPhTcpxNHYeJxR1cuoBwyTxTSnqZLI8ob80dqnr56gKf7u8hEYeZw" height=71 width=283></td></td> - -<td><td>After</td></td> - -<td><td>WPT test coverage</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/rdOjKXaS2ht4sGwGCgrOuB1JQFVuOqvNiFumSW_zh89KsUBu1PenVeuy1oN3HJwAwF5bsTNUscPo_pLKIqgcHzWvYaKWyPRG1KnF-XcoQgxRtBpctW-TtxAiWv83RatSHvAxQ6EHvw" height=55 width=283></td></td> - -<td><td>kevers@ and girard@ <a href="https://docs.google.com/spreadsheets/d/1aUnU5Igiescq93oY01bBPJ77TBb3oy5Y-jvUf7u_600/edit#gid=15396280">measured</a> test coverage in WPT for input/scroll/animation. The data can help us understand which category of tests needs more attention.</td></td> - -<td><td>TestDriver Action API</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/rcHUPkETRQuNvGLbl_2x0o9KA2PhTUnHISjRsr0Oon68LKo9LtgnUynF997aTlPbj18znph4sfrEeZhNzyPlUA7oINLMWQT_oyemx_m_oCRxjzvUqZKkbXpIK1eUYT0torK1rqRiEg" height=178 width=237></td></td> - -<td><td>lanwei@ kept improving the TestDriver action API and made more WPT tests automatic.</td></td> - -<td><td>The following two pictures show the wpt dashboard for the TestDriver action API.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/VZ_e8LDAUVDSGmSXU8OcOjoqUtEQdpk2Xm9wbtCohj3nk2Dc-cVxFvyrg4hMQxwME1gRVzdlnOAiVs_qRkNqpvSqreNLBW7-U3xjXbUj-jHeF2BkbFjnAzC2UGbzaMZdiCouHcO8Rw" height=101 width=144> <img alt="image" src="https://lh6.googleusercontent.com/uCRgxqbX_Vp5mUsc3z0umBfFrdZtMBYySftCvpx8vQCy81r8Ljgftfw594GnAipZBazHUK7D59iNF5s2BGSTiZBK3vVrmZFM2ZdaB245E7Qb-vj294VLRF7MR3jwxTpf1Qg4ZDYZHA" height=108 width=127></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Stability Fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Animation security fix: use after poison</td></td> - -<td><td>kevers@ fixed a crash in Animatable::Animation. The problem is that running user code (JS) can result in the destruction of an execution context. We cannot simply check and forget about the execution context. The solution is to double check if the context is used downstream of script execution.</td></td> - -<td><td>Float-cast-overflow in MouseEvent::PageX</td></td> - -<td><td>liviutinta@ fixes a float-cast-overflow bug that is caused by static_cast<int>(double value) when the value is out of range. The solution is to usd std::trunc and clampToInt instead.</td></td> - -<td><td>Paint worklet regression</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/LRW7Vq-NI5lusgpbWRv6HVUKTn0mZQztrsHkqtw9Yh-AtGXPD5pKQPJNtIY_0BcSEdKnBykk2KoZ_afKqK17-PbFJDWUfV91I0tzte96FktV2V67DsPIPTrsRD0UchD0uYyExNKkYA" height=222.4665071770335 width=284.0179856115108> <img alt="image" src="https://lh4.googleusercontent.com/PRq4eiC7ydMEjQ3gF6CKwFT_AdhAYjsxJ9vODczpmLtVRwjToS0UdnaJ5thn0jnKuzqTh7TqtJt_cSGd8IfurJ4DJp7eETLIRHVhBogoKEcJINDTwxFX-0fMARFxj8krVA2iINYVFQ" height=223.95238690885697 width=281.9892857142857></td></td> - -<td><td> Stable Canary</td></td> - -<td><td>xidachen@ fixed a regression due to a misuse of hashmap. In the above demo, the same animation is applied to both elements. In other words, the animations of the two elements should be in sync. However, the stable version is wrong. The canary version has the fix in it, and it is correct. </td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Crash in PointerEventFactory</td></td> - -<td><td>mustaq@ untangled a mixed-up <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1164347#c4">crash report</a> that becomes release-blocker-stable at the last moment. The effort of fixing the crash includes:</td></td> - - <td><td>Determine the root cause, landed the <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2488181">fix</a> - on ToT.</td></td> - - <td><td>Merged the fix back to M88 and M89.</td></td> - -<td><td>Paint worklet crash</td></td> - -<td><td>xidachen@ fixed a crash where the root cause is that our code path hits a DCHECK that is no longer applicable. The solution is to remove the outdated DCHECK.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Code Health</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/ewdZ0ZzCsU5ix0iB-HZ3b9Rd_D2cpoVJTrlRAMh9lgyhQ96jCl2qEG2PLS_He6sp2Og_8BVheiG83LFJqDG1Bf4XwSyb1NxlJ_fEbzXlNV3hD-jsYHOdgSJkdIIa3WEeK9UQcpNprA" height=162 width=292></td></td> - -<td><td>Our team had a great start to the year by closing over 70 bugs in this sprint:</td></td> - - <td><td>Specifically, we closed more bugs than opened in P1 and P2 - categories.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/-hszaQS6D49VBAmVoXwrtim2_Z_vFlVFNJH4L0YtdLHFo_4kQPX9dmwBrW3kQPpHv1nQOceCi6QWOGQtyq3HLpBysTtD57n2zUbsU9fM3_br_re6EfeEqGbe1VptGOzNdv0GUUYHuQ" height=136 width=217> <img alt="image" src="https://lh3.googleusercontent.com/h8ggB6_4DB7Mov_O0H4AJhF7gxhzAjxbo7Abgjz-6dzH9bVz1-mnXG7leBnPB0CF2fQb_kPIezzcEartcLY4TV9HG8OCHLFsZSxfvq35pAk389xH3Oa95Yg_4LWXUbyc8RNe5WEA5A" height=140 width=227></td></td> - -<td><td>girard@ collected our team bug data and generated graphs to visualize it.</td></td> - - <td><td>Our P1 and P2 bugs are less than 40% of total bugs.</td></td> - - <td><td>~40% bugs have owners assigned.</td></td> - -<td><td>girard@ re-enabled “<a href="https://chromium-review.googlesource.com/c/chromium/src/+/2643444">MissedTOUCHEVENTF_UP</a>” which tracks a hack in windows touch. We would like to <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=811273">tear out the hack/workaround</a> once usage drops.</td></td> - -<td><td>liviutinta@ removed the <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2595636">AzimuthAltitude flag</a> since it has been turned on by default since M86.</td></td> - -<td><td>lanwei@ and liviutinta@ fixed input failing tests on the new WPT bots.</td></td> - -<td><td>mustaq@ landed Mouse/PointerEvent related code cleanup.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | January 2020</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/july-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/july-2019/index.md deleted file mode 100644 index 0a11c9470a9..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/july-2019/index.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: july-2019 -title: July 2019 ---- - -<table> -<tr> - -<td>July 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh3.googleusercontent.com/w9kTMoKBL0rbJTFvKmkNWwY3xG4Z3UqhW7iLHeK9aV4YsUitV1OdoR1WEsmHnz4jiwphbWtGyO31tp_j6lxpnlmRYvfAjdVTB5vJA_vDgjqAagHNh7Zb7kATsCecD8lVfYMmiqlj" height=283 width=565></td> - -<td>One of three example effects that yigu@ created to show the potential of Group Effect. I'm staggered, really.</td> - -<td>GroupEffect - Showing a need</td> - -<td>When exploring new potential features, it is important to understand what usecases they enable and how ergonomic they would be for web developers to use. This sprint, Yi (yigu@) spent some time exploring the <a href="https://github.com/yi-gu/group_effect">proposed GroupEffect</a> concept. After <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1710156">building a prototype</a>, Yi created demos for three types of linked effects, such as the 'stagger' effect above. This work helps us understand the potential impact of GroupEffect, and also see how easy the proposed APIs would be to use.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/TweoRh0njZWyEESeBZAjj8CRazxBzSQYhiB3k72KH0tPLQRJMRdXx56EpBceCuuLHgExjuK_Vp7BrtfL6j2fH1Jg8eGNVcIsmnFYM7gIBtv4pckxtNZKzvFz8GJBxqqBKlLPakrP" height=184 width=271></td></td> - -<td><td>Web Animations - towards an I2S</td></td> - -<td><td><a href="https://drafts.csswg.org/web-animations-1">Web Animations</a> is a big focus for the team currently, and we continue to move towards our goal of being able to ship the full API.</td></td> -<td><td>This sprint included fixes for getAnimations (majidvp@, smcgruer@), AnimationClock (flackr@), animation events (kevers@), and CSS property serialization (gtsteel@) - resulting in 50 newly passing WPT tests!</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/4zapRR1JUKCEExT9Dy78adDfv0BZVOEics7z7LoQfb2gCZ6JRwukYMkSyCibRxMB8fjEfSw20riiW9mJkbKHPqa_B16Uso8QdhVJnNP29M3f9c5P3i812LKoxlqyCNaAPZFSs_Au" height=208 width=253></td></td> - -<td><td>Viz hit testing V2 - heading to stable</td></td> - -<td><td>Yi (yigu@) set his sights on Viz hit testing this sprint, with sensational results. He was able to close 12 hit-testing related bugs, including all known bugs blocking the 'V2' launch. As a result this new, faster hit testing model is now re-enabled for the M77 release and should be rolling out to stable sometime later this quarter.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/k4oS7E04Mz46HL5n13FzLh2ev0LCQNuNvg2VYkrzLEC807Bxurf32asE05BcHMaca1lPqr9zgIYEHWWKm6V_PT8c0DRUqhzeHBVqgGaP3nmsZNq1-Lo4mFsLOHxBbGj0HiHLnA4R" height=113 width=281></td></td> - -<td><td>Complex Crash Bugs</td></td> - -<td><td>Chromium is a big codebase, and sometimes simple looking crash bugs can turn out to have complex causes. Thankfully these bugs are no match for Rob (flackr@) and guest star Dana (danakj@) who tackled <a href="http://crbug.com/974218">such a bug</a> this sprint.</td></td> -<td><td>After multiple weeks of effort they tracked the crash to an old scheduler experiment which was unexpectedly re-ordering IPC calls! <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1692577">Disable the experiment</a>, and the crash was fixed. Magic, or perhaps just <a href="https://en.wikipedia.org/wiki/Clarke%27s_three_laws">sufficiently advanced debugging</a>.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/_d5BW7phRaKRlndSuxtEz8gidiwiNmYZ8NzvSpX5Iv9FplDwBinrCUcp1SgTKN1oazrAqRZYAvm3E68YfGx08KfLUEATZgD4wvIyuRd2LTGxTvOc21iS9aQIxwW-YQwC3oZmao53" height=121 width=286></td></td> - -<td><td>Scroll Snap Interop</td></td> - -<td><td>Blink's viewport style propagation for scroll snap was incorrect based on the latest <a href="https://github.com/w3c/csswg-drafts/issues/3740">spec changes</a>. Majid (majidvp@) dived in to fix this issue before Firefox's implementation ships, to ensure that the interop issue is addressed before usage grows and makes it more difficult to backtrack. </td></td> - -<td><td>Since this is a breaking change, we needed to understand its impact on the web. To do so Majid performed an <a href="https://docs.google.com/document/d/1DxVjr3m02cPE81UrDMT_SN36bFDg5f4K3wESSwMOqck/edit#heading=h.a1k7isoapl5s">analysis</a> using <a href="https://docs.google.com/document/d/1FSzJm2L2ow6pZTM_CuyHNJecXuX7Mx3XmBzL4SFHyLA/edit">cluster telemetry</a> in conjunction with <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1715906">use counters</a> to confirm his findings - all clear, thankfully!</td></td> - -<td></tr></td> -<td></table></td> - -<td><img alt="image" src="https://lh3.googleusercontent.com/K6hFM4soJErRvy01DD6mh_CQBnhGKbyWG-ymrlIptHnSNUVT1A53TNDoE2zr7YSBkIsDxFd9sjymzqQQzof2xw86kL-Z8uwXlj_KSbiWRP1xzArmob40InxUv4wFvDPsYsEeJfqZ" height=207 width=596></td> - -<td>Thanks to this demo by gtsteel@, it is easy to see why animating in the RGB color space is preferable to sRGB.</td> - -<td>It's a colorful world</td> - -<td>While discussing a <a href="http://crbug.com/981326">color interpolation bug</a> that Xida (xidachen@) was working on, he and George (gtsteel@) realized that by spec colors interpolate in the sRGB colorspace. This is unfortunate as sRGB is a non-linear space which results in less natural looking animations than the linear RGB space. George began investigating the possibility of adding RGB interpolation support to the various animation specs, however luckily we discovered that the <a href="https://www.w3.org/TR/css-color-4">css-color-4</a> spec is working on allowing web developers to <a href="https://www.w3.org/TR/css-color-4/#working-color-space">change the page's color space</a> which should also fix animations for developers who opt in.</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | July 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/june-2019-volume-ii/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/june-2019-volume-ii/index.md deleted file mode 100644 index 93c2f47a6eb..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/june-2019-volume-ii/index.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: june-2019-volume-ii -title: June 2019, Volume II ---- - -<table> -<tr> - -<td>June 2019, Volume II</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh4.googleusercontent.com/et9ryoulZxztot-SLE6W1uC3kLdirsX9ha2wyFDxr7nGs0gAH_64JV5xiHk97i4w-urHvJpsmbzHGwdHtOgwBPdEuQTyw_nvlmguJ4eH27gSTADAB7QjeIdEjSoua_BoDKNL4uNs" height=334.29598821989526 width=593></td> - -<td>Is there a poltergeist trapped inside Chromium? Not any more, thanks to flackr@.</td> - -<td>Gmail, possessed?</td> - -<td>A spooky bug floated our way this sprint as users began reporting that their gmail and twitter pages were <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=962346">scrolling without any user input</a>! After initial analysis from the input team (great work by bokan@!) identified it as a BlinkGenPropertyTrees-related Animations bug, Rob (flackr@) spent days teasing out first a reproduction, then a diagnosis (surprise, <a href="http://crbug.com/962346">it was complicated</a>), and finally landing <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1256422">a fix</a> that took care of this ghostly occurrence. Who you gonna call? Rob Flack, apparently.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/dG77X96y5b6huezy55beT998DAxMlJb5Bv_bI9d2WFqcyiJS0Fgx9K8JHcZIaRVEn-ljQusGlsLThtcV54ChP-tZx4mgIgdNmzie2pMDvcBT4fBUbzg1_zlbNfFvR9Ev5ywFVVXm" height=179 width=251></td></td> - -<td><td>Animation Worklet - it's (more) official!</td></td> - -<td><td>Animation Worklet took not one, but two big steps forward this sprint. We sent our official <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/aRKT0BkrF-8/discussion">Intent to Ship</a> to blink-dev@, reflecting our opinion that the first version of Animation Worklet has reached maturity and is ready for real users. Coincidentally - and nearly simultaneously - the spec was also <a href="https://www.w3.org/blog/news/archives/7830">promoted to First Public Working Draft</a> during this sprint.</td></td> - -<td><td>Congrats to all the people who have and continue to work on Animation Worklet!</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/6640vwTykAzTgcwoKk0u4ZqXpZioR6PYeo48yUPWIb9S4jaLgOc-kfxXGrGvTscFRVW51tJVpdt0bUiD0VhYZhhNbRrEhgiAZC2vrT6-uZgjHVaPDIeUpOAHAd9Shz8Jknd38Xef" height=179 width=277></td></td> - -<td><td>ScrollTimeline prototype lands</td></td> - -<td><td>Browser support for scroll-linked animations is a common request from web developers, as JS based solutions suffer badly when the page janks. We took one step closer to fulfilling such requests this sprint with Olga (<a href="mailto:gerchiko@microsoft.com">gerchiko@microsoft.com</a>) landing a (main-thread only) prototype of <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1597286">ScrollTimeline for Web Animations</a>. </td></td> - -<td><td>Interested developers can now run Chrome with --enable-blink-features=ScrollTimeline to play with the prototype - but be warned, this is still very early stage!</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/RSKmCRIPTTUphzkYEdus7axPNzy7YgZaToyRaJ2gSvyS4RECsUSwcBvKOqXBxHJ63uoZFLFCJOAzm2lEq5KBKmVo8vL5Qs149NrizzxlPxqY-Xx5ZC4_IpTwwBEQ7eBnm_hvTEXu" height=164 width=283></td></td> - -<td><td>Exploring the Animations space</td></td> - -<td><td>It can be easy when working in the browser space to lose sight of what our corner of the web platform is actually like for web developers. This sprint Gene (girard@) put together and published <a href="https://docs.google.com/document/d/1hPfNx9aM7KHRO7DZDTvrBAQUbTdYIap9U__uqp_-EQo/edit?usp=sharing">an overview</a> of the tools and processes web developers are using to create and deliver animations on the web. This form of insight is vital to better understand what features we should be prioritizing, and to deliver a better web for everyone.</td></td> -<td><td>(Chart above uses data originally from <a href="https://trends.builtwith.com/">https://trends.builtwith.com</a>.)</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/8HBpbkDCHE7aPyKADf56885lm6O9DjjjxZ4PEpqWoW2oc0n89WUMnJK6ySLkUMH7afHHKB5U7CP-fggLDrFcHD0uYKOHTZbb3JPk8gha16UvPrpMQVp-2HWvkb7eHNt6I2ImCoX8" height=173 width=283></td></td> - -<td><td>PaintWorklet HiDPI bug squashing</td></td> - -<td><td>When developing his PaintWorklet-based Lottie renderer <a href="/teams/animations/highlights-archive/june-2019">last sprint</a>, Rob discovered a few rendering bugs relating to PaintWorklet on Mac HiDPI devices - such as the unexpectedly cropped image above. Thankfully such bugs are no more, as Xida (xidachen@) spent time this sprint hunting down multiple zoom and HiDPI related PaintWorklet bugs and fixing them.</td></td> - -<td></tr></td> -<td></table></td> - -<td><img alt="image" src="https://lh4.googleusercontent.com/5698PMmqluSrFNc6Ejfmw43rLCwUvxnbGistZt8RddT1RsxFRiHQdBm5P2RbliVc3cr77vgp0PS8Vou8XaLGFmLd4MsBQn5pJbKstBDX4u3o-T58FCv5_mmwOgk3pdAFTitVJODA" height=413 width=418></td> - -<td>Do you understand this? Yeah, me neither. But kevers@ does!</td> - -<td>Better Beziers</td> - -<td>Sometimes, you just have to get down into the weeds to improve browser interop. This sprint Kevin (kevers@) did exactly that as he tackled the hairy problem of bezier curves - namely, why does Chromium's implementation produce different values than other browsers? Details of Kevin's explorations could probably fill a small maths textbook, but in the end he was able to <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1643973">land a new approach for Bezier estimation</a> that took half the time of the old method, made Chromium pass almost 20 previously-failing WPT tests, fix two Chrome bugs (issues <a href="http://crbug.com/591607">591607</a> and <a href="http://crbug.com/827560">827560</a>), and exposed a <a href="https://github.com/w3c/csswg-drafts/issues/4046">hole in the spec</a>. We think Monsieur Bézier would have been proud. </td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | June 2019, Volume II</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/june-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/june-2019/index.md deleted file mode 100644 index 72ffa4c4561..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/june-2019/index.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: june-2019 -title: June 2019 ---- - -<table> -<tr> - -<td>June 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh6.googleusercontent.com/m4coonQxOBK51yMEp5SzIVklqRrtqAYwfdXWZXoXSu3aes8t_mLkYnflh0fKVs4EXQPNeRLttrdBjC8R6GcDHMlc6YwMYc1ps2eKlq6H-RAMX6-rSukfKe23fQfzux059NrGHe28" height=151.34334224680958 width=593></td> - -<td>Lottie Paint Worklet Renderer</td> - -<td><a href="https://airbnb.design/lottie/">Lottie</a> is a popular framework from AirBnB that renders After Effects animations, allowing designers to create rich complex animations. Following up from the <a href="/teams/animations/highlights-archive/april-2019-volume-ii">previous proof of concept</a>, Rob (flackr@) <a href="https://github.com/flackr/lottie-web/tree/paint-worklet">created a proper renderer</a> preparing to send a PR to land the code upstream. The <a href="https://twitter.com/flackrw/status/1135714462546182144">response on twitter has been very positive</a> and with the demo <a href="https://flackr.github.io/lottie-web/demo/bodymovin/">publicly accessible</a> we have seen an <a href="https://chromestatus.com/metrics/feature/timeline/popularity/2385">increase in the usage of Paint Worklet</a>.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/bQ1CSbp3EmX4fKEjkXY1dlKZ8MRvdtfBR4eoQt57owRNba-xw00y_2hGh90_o0LoSWECa5BT_ip3kJh0K988KWFfgKF1L_SzSQo3h-VutcgqTAY0sgFam3ndvD_OIsIf0oijOywi" height=121 width=198.1957328066892></td></td> - -<td><td>Jump timing functions</td></td> - -<td><td><a href="https://drafts.csswg.org/css-easing-1/#step-easing-functions">Jump timing functions</a> allow developers to choose the starting / ending behavior of the steps timing function. Thanks to Kevin’s (kevers@) <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1634722">hard work</a> chromium has <a href="https://groups.google.com/a/chromium.org/forum/?utm_medium=email&utm_source=footer#!msg/blink-dev/u65DesVOzmY/htUnPfFcBgAJ">shipped these functions in M77</a>!</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/BHmrokKErIb7eNeCsjGw4Ae6c-PDYX3YCjfB8ENHs70ELIQLDuL2nwSOza0XygjTYFQ5ZMKh8vmY11gBqmRZRv9FBbrh0aOmzD3dZcAhkIS9yYNZStUQle-EIFrjIKbhBM1x06eN" height=121 width=291.65571205007825></td></td> - -<td><td>Scroll snap … stop!</td></td> - -<td><td>A common use case for scroll snap is a paginated UI. Often, developers want users to be able to easily swipe to the next page. Thanks to Majid’s (majidvp@) efforts scroll snap stop has now <a href="https://groups.google.com/a/chromium.org/d/msg/blink-dev/bkUwigYHJDM/Bzvm8tkHAgAJ">officially shipped</a> in <a href="https://www.chromestatus.com/features/5439846480871424">M75</a> and used by <a href="https://drive.google.com/file/d/1D-xXO6wstu0HJJXvvwFjNpa2R1gzwuhG/view?usp=sharing">AirBnb</a>.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Houdini Face-to-face</td></td> - -<td><td>Majid and Rob attended the <a href="https://wiki.csswg.org/planning/toronto-2019">CSS working group</a> to advance <a href="https://github.com/w3c/css-houdini-drafts/wiki/Toronto-F2F-June-2019">several Houdini spec issues</a>. Notable topics discussed include: <a href="https://github.com/w3c/css-houdini-drafts/issues/869">StyleMaps for Animation Worklet</a>, <a href="https://github.com/w3c/css-houdini-drafts/issues/877">cycle detection for Paint Worklet</a>, and <a href="https://github.com/w3c/css-houdini-drafts/issues/872">cheaply passing large data in the typed OM</a>.</td></td> - -<td><td>Off-thread Paint Worklet</td></td> - -<td><td>Support for running paint worklet is steadily approaching completion with Stephen (smcgruer@) adding <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1639079">asynchronous paint dispatch</a>, Xida (xidachen@) is designing <a href="https://docs.google.com/document/d/1a7gO6cBxsJhn53akuJuieUiXvB74vvEmFDyKww8NKdw/edit">animation integration</a>, and Adam (asraine@) <a href="https://crbug.com/948761">added fallback</a> for the cases we can’t support.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/r6Wkle2R-fnxzk4IwP-s_ssaMFE3-kmJP1FO20H9N2eJezr6Kc8yKo8JleHnY1czBkbVEhw-FKNAcb344bvyyntsfoiFH74OV5I37bmEM4wYQ1rBVHW6-zCHbPuz2DQFvJdaTr34" height=121 width=188.74074074074065></td></td> - -<td><td>Group Effects</td></td> - -<td><td>Majid and Yi (yigu@) have put together a new <a href="https://github.com/yi-gu/group_effects/blob/master/README.md">explainer</a> for Group Effect proposing changes to the existing draft design to make if more customizable and <a href="https://github.com/w3c/csswg-drafts/issues/4008">restarting</a> the effort to standardize the feature as part of WebAnimations level 2.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/cdBRl4mdiK_TkHcothUZSYhUXGbZ-NKD13Kx3P2-tcq_VjatfaOTov0Sd5AxGzPdr0ogyHw77mNKdZqfVh6_rRlVspirZmjkwB7LFuoZVJ_gXudDAgShHBRcR_QpL6aGqZLJ7ym5" height=126.00000000000023 width=202.27926371149522></td></td> - -<td><td>Bugs, bugs and less bugs</td></td> - -<td><td>We’ve continued our effort to stay on top of incoming animation bugs. Over the 3 week period 13 animation related bugs were closed, however 11 new ones were opened in that same time.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | June 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/june-2020---web-animations-scroll-linked-animations-throughput-metrics-scroll-unification-webdriver-pointer-events-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/june-2020---web-animations-scroll-linked-animations-throughput-metrics-scroll-unification-webdriver-pointer-events-and-more/index.md deleted file mode 100644 index 7f999422825..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/june-2020---web-animations-scroll-linked-animations-throughput-metrics-scroll-unification-webdriver-pointer-events-and-more/index.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: june-2020---web-animations-scroll-linked-animations-throughput-metrics-scroll-unification-webdriver-pointer-events-and-more -title: June 2020 - Web Animations, Scroll-linked Animations, Throughput Metrics, Scroll - unification, WebDriver, Pointer Events and more! ---- - -<table> -<tr> - -<td>June 2020</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh5.googleusercontent.com/qa4CnhPdM0cesetEwVq7R6MRWTpi_RtZkOAI2uteVUXnr4cSA_eUp7CW5wrayRElFCzMiko7wLECykKFllzcU0WWIcilwBWTyFro4uRcHxcVd3AMpHQfv4_FYkZDFrCz4fGH0o9fLw" height=343 width=406></td> - -<td>Fix transition retargeting</td> - -<td>The CSS transition property is used to create a smooth transition of a CSS property on a style change. If the property is currently being animated (via an existing transition or other animations), this needs to be accounted for when calculating the starting point of the transition to avoid abrupt jumps in the value of the transitioned property. This process is called transition retargeting. We currently set the starting point based on the computed value from the last frame.</td> - -<td>Our team members (kevers@ and gtsteel@) have made significant progress on this issue. Per spec, we need a base computed style (without animations) and then apply active animations on top of the base style to get the before style change for retargeting. Fortunately, the style resolver already tracks the base computed style (conditionally) in order to accelerate style recalculations that are driven purely by animation ticks.</td> - - <td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2185509">Step - 1</a>: Add test cases for reversing modified transitions to WPT.</td> - - <td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2252642">Step - 2</a>: Always cache the base computed style in the style resolver, tracking - when it can be used for style recalc. Highlights:</td> - - <td>Fewer flags to track</td> - - <td>Fix storing the cached style on the first frame of an - animation.</td> - - <td>Reusable for transition retargeting</td> - - <td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2220263">Step - 3</a>: Compute the “before change” style by playing active animations on top - of the base computed style.</td> - -<td><table></td> -<td><tr></td> - -<td><td colspan=2>A better fps meter</td></td> - -<td><td colspan=2>xidachen@ has been working on measuring renderer’s smoothness and developed <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2244002">a better fps meter</a> that reflects smoothness. This new-looking fps meter is available on canary.</td></td> - -<td><td colspan=2><img alt="image" src="https://lh4.googleusercontent.com/7X6mpuYlg8ai4-U3yphi45I7mEFYKW74K27X_2ekbw-_TXxaY51pIQ9elyjSu2tIzFlTmo8KFdIXrv56tTq_XS1US1Dl7_SUMK9U3PYFxA8X43nsq5vdmMLq4Xshjxd4rAqJ0OleEw" height=439 width=580></td></td> - -<td><td colspan=2>Improved throughput UKM</td></td> - -<td><td colspan=2>In the last sprint, we <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2112953">changed</a> the UKM reporting logic such that we report the median throughput of a page, which better reflects users’ browsing experience. Following graph shows the UKM curve where the red arrow points to the date when our change is landed.</td></td> - -<td><td colspan=2><img alt="image" src="https://docs.google.com/drawings/u/0/d/sy-viUUomGinfT8KjKYZiDQ/image?w=270&h=335&rev=15&ac=1&parent=14Nvi8kAwj_lSQYSf2z6Ywhvz7TD4B8S9Z-LViAhB5LI" height=335 width=270></td></td> - -<td><td colspan=2>Scroll-linked animations</td></td> - -<td><td colspan=2>flackr@ made a lot of progress and discussions on <a href="https://github.com/w3c/csswg-drafts/pull/4890">progress-based animations</a>, particularly focused on procedure for converting time based animations. With this, developers won’t need to specify an arbitrary time duration for the animation:</td></td> - -<td><td colspan=2><img alt="image" src="https://lh5.googleusercontent.com/pexwnQ-nbMSOhhDhEjfSJKinMbjJxbW3lLZWHk2DN4dl5vAJMEyZriNbYgFjAZ4lEMFXXZrXdTmHO6nkTYLwtn9aqws7V_yKfxYllK500DtZCB6kQJUVyK-7IpJ9RKP-xEhL8TspMw" height=124 width=408></td></td> - -<td><td colspan=2>Scroll unification</td></td> - -<td><td colspan=2>lanwei@ <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2171955">replaced</a> eventsender with gpuBenchmarking.smoothScrollByXY (<a href="https://docs.google.com/spreadsheets/d/17NdL_750nAk51FN-dUprUNpBsp0_QCZZwKFJGENMXPE/">test list</a> 12/62 remaining)</td></td> - - <td><td colspan=2>Unblocks scroll unification, because after we finish the - scroll unification, the scrolls happens mainly on the compositor thread, and - the scroll code in the main thread will be</td></td> - -<td><td colspan=2>removed. eventSender sends the scroll events to the main thread, so it would not work after the scroll unification. (<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1047176">Issue</a>)</td></td> - - <td><td colspan=2>Tests full event delivery path</td></td> - -<td></tr></td> -<td></table></td> - -<td>WebDriver Actions Spec</td> - -<td>lanwei@ is adding wheel source type to the spec and associated WebDriver tests. In particular, the spec change pull request is <a href="https://github.com/w3c/webdriver/pull/1522">here</a> and <a href="https://docs.google.com/document/d/1DdoNXbGspv4H5rmeCTgoiNPN5JGCitYbzVFd8FjSJiU/">design doc</a>.</td> - -<td><table></td> -<td><tr></td> - -<td><td>{"actions": \[</td></td> - -<td><td> {"type": "wheel",</td></td> - -<td><td> "actions": \[ {</td></td> - -<td><td> "type": "scroll",</td></td> - -<td><td> "x": 0,</td></td> - -<td><td> "y": 0,</td></td> - -<td><td> "origin": element,</td></td> - -<td><td> "delta": 30,</td></td> - -<td><td> "direction": "y"} \] \] }</td></td> - -<td></tr></td> -<td></table></td> - -<td>Pointer Events altitude/azimuth attributes</td> - -<td>liviutinta@ sent a Pointer Events pull request to fix <a href="https://github.com/w3c/pointerevents/pull/323">problems with default values</a> for altitude/azimuth/tiltX/tiltY attributes. The associated <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2165457">CL</a> by liviutinta@ is under review too. mustaq@ sent a follow-up pull request to fix <a href="https://github.com/w3c/pointerevents/pull/324">boundary value conversion errors</a>.</td> - -<td>The first <a href="https://github.com/w3c/pointerevents/pull/323">pull request</a> above adds important missing details to existing azimuth and altitude attributes: </td> - - <td>Support C++ code generation from pointer_event.idl and - pointer_event_init.idl files. This was a blocker for C++ implementation in - this <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2165457">CL</a>. - As a result the default values for tiltX, tiltY, azimuthAngle, altitudeAngle - were removed from pointer_event_init.idl. This change allows one of the - angle pairs to be specified in the PointerEvent constructor and the other - pair will be automatically calculated by the user agent. </td> - - <td>Change the default value for altitudeAngle from 0 to /2 to better align - with default values for tiltX and tiltY.</td> - - <td>Specify the rounding method when computing tiltX, tiltY from - azimuthAngle, altitudeAngle </td> - - <td>Specify what happens when only some of the angle values are provided for - untrusted pointer events: the user agent will never overwrite a value - provided by the author even if the values are wrong. If the values provided - for tiltX, tiltY, azimuthAngle, altitudeAngle are not consistent, it will be - considered an authoring issue.</td> - - <td>Specify that for trusted pointer events the user agent will populate - both sets of angles. </td> - -<td>Example specifying tiltX, tiltY in PointerEvent constructor and being able to use altitudeAngle, azimuthAngle afterwards.</td> - -<td><table></td> -<td><tr></td> - -<td><td>var event = new PointerEvent("pointerdown", {tiltX:0, tiltY:45});</td></td> - -<td><td>console.log(event.azimuthAngle); // will print the value Math.PI/2</td></td> - -<td><td>console.log(event.altitudeAngle); // will print the value Math.PI/4</td></td> - -<td></tr></td> -<td></table></td> - -<td>Example specifying azimuthAngle, altitudeAngle in PointerEvent constructor and being able to use tiltX, tiltY afterwards.</td> - -<td><table></td> -<td><tr></td> - -<td><td>var event = new PointerEvent("pointerdown", {azimuthAngle:Math.PI, altitudeAngle:Math.PI/4});</td></td> - -<td><td>console.log(event.tiltX); // will print the value -45</td></td> - -<td><td>console.log(event.tiltY); // will print the value 0</td></td> - -<td></tr></td> -<td></table></td> - -<td>Visual representation of azimuth and altitude for a pen <a href="https://www.raywenderlich.com/1407-apple-pencil-tutorial-getting-started#toc-anchor-006">here</a>.</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | June 2020</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/june-2021---new-features-stability-fixes-interop-fixes-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/june-2021---new-features-stability-fixes-interop-fixes-and-more/index.md deleted file mode 100644 index 998568e9c98..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/june-2021---new-features-stability-fixes-interop-fixes-and-more/index.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: june-2021---new-features-stability-fixes-interop-fixes-and-more -title: June 2021 - New features, stability fixes, Interop fixes and more! ---- - -<table> -<tr> - -<td>June 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Composite background-color animation</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/rHya85oxF853pbXs1D5q8q9SV2xekZtWIWWGcmYQ4s6DlvXcyGeuS_9Zk9Vb5qk73JxTEjFTzLQHUxj8laup5dbCOZ4vXP0fXUL_xtd-WNFlLQn6El0whQwe5Do1V192eHW1hJrzKA" height=19 width=283></td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/RNatxDtrJzdHYIC5oHcgxL7ajcpK2Iv2l2-_ShR6Idv0KXInV0qYhlB-Bh9n7Ft7UW70gucCbUWJAw0bBwMP-taUrZUjttltaiFpnzfw6Yugeniws_M4LjMjajXuT628gNL1cKRKKA" height=19 width=283></td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/IJMi8TbxUl9qriGc6ChrTf74Z7Bhz0Cv3kJ31Ja-JSoR4c-HKqULxw2yBiC7JZzHbExW3uuug6BEcxqyfpZCWXOh3hFEg9Njp4eALgbJLCPtJi7JZwttbKeUZqOZJIzV-BVbOlhUAQ" height=19 width=283></td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/hlpW92nOALGoQeoWIryCOpkDHyUL7jSqn5k41puVwjNqgz2JZNUmY5lPlHNu2udqf1xarZjBsvaeIaInsD-2Vrh4lEeGLMvg7HvKxWCEM90y_EkbUjWZcUKQ9mfT2kPs1p2b68X-mg" height=16 width=283></td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/Lmtm-9xfWUAEkzirIRr0U0UyWXKpC21Po57pjhX3P_Zx6_97j_yToFzmmXvL373Z2pMZs_ihciB-8qnPbqPDlzB_xXizKfkt1aiL4ynidq2PXRmOZNMawljumRcslU3kG5KmuKyT-A" height=59 width=283></td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/Rs6HguE0Zjz-SYNiIOZ83SbSe3Mdfb0ogO8T14iY7WAp2DOr96Jbn5HVUnjKui8AApsIToC1WJQzwPfXU6aSJh3IW_-ZjZssMtjWn9uHmwjPVSw1up81oN2B211uLI9OLLkvEkve8w" height=21 width=283></td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/scZffxszmv6AWdv6iaxx2_56xvqqTe6bBLPlV8hMp3SVoDKEOmFms5N48S0KIjVMteqCeu5ZWiuv93U0AdZmQhVyN6ubSRPANxtJZc6wCEywMlqNs0uTFdkFvqtNrDiGAyHIKwV4rQ" height=40 width=283></td></td> - -<td><td>xidachen@ launched finch study for this feature and this <a href="https://docs.google.com/document/d/1Fkp7udbCgYqVtNf4gn-NXGVYamPrd_n0qKqalruTq6E/edit#">doc</a> summarizes its result. Here are some high-level points:</td></td> - - <td><td>We are seeing more animations being composited.</td></td> - - <td><td>Unfortunately we don’t see improvement in the “PercentDroppedFrame”, - which reflects the smoothness of the animations overall. One possible reason - is that background-color animation is mostly applied on small buttons and it - is not the dominant factor of dropped animation frames.</td></td> - - <td><td>We are seeing memory regression and this is tracked by <a - href="http://crbug.com/1210221">crbug.com/1210221</a>.</td></td> - -<td><td>Moreover, this feature is now experimental, which means one can enable it by enabling “Experimental Web Platform features” in chrome://flags.</td></td> - -<td><td>Capability Delegation Spec</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/QZpkzz-EcZyPGYxfeNVDeC5oyrwyLaDXLDJDPXlZXIouySfVIVqPvOWJPliQFiOlc2EbyU467uu5dVFd9exgj2aYo5kg6-rg59ma-zb_Yxp7jmQdyNJb3GbX3K7t2ppDOh_tDUOD8w" height=88 width=283></td></td> - -<td><td>mustaq@ finished the draft spec (<a href="https://wicg.github.io/capability-delegation/spec.html">link</a>) and it is ready for review.</td></td> - -<td><td>Android 12 Overscroll</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/0h7u2zpQbuiN4fQIIkFzibmx86KdLvK5X-P-vFKr1bGrj5AhP5FV5_ZMHQ6_YnWA-a24li0BjD2_JMwr5vC4FHCIunYc9StHR8m4MLuViGUoYS8xQewQYJIVIQ9nY1vTN70pCqRHzw" height=507 width=240></td></td> - -<td><td>flackr@ has finished the initial version of working overscroll.</td></td> - - <td><td>It re-uses elastic overscroll physics from Mac overscroll.</td></td> - - <td><td>Instead of translating, it applies overscroll stretch on the - transform node.</td></td> - - <td><td>There are lots of follow-on work including:</td></td> - - <td><td><a - href="http://crbug.com/1213217">crbug.com/1213217</a></td></td> - - <td><td><a - href="http://crbug.com/1213248">crbug.com/1213248</a></td></td> - - <td><td><a - href="http://crbug.com/1213252">crbug.com/1213252</a></td></td> - - <td><td>Enable only on Android-S</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Stability fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Fix privacy leak of visited links</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/U7PEC5Lsr_AZGA2ft-FNFL1QB__w3tp_c5JqGfL20L0qnE_MSu6L3U62BNNoSEAt3GO_dAmvcgkMac1Ue0xGHp0tfU7xK0h1eK2XLksH5vlhTbAqCaNoo_8n6akgSW-6dATvDJIWrw" height=119 width=283></td></td> - -<td><td>kevers@ fixed a privacy leak issue of visited links. A repro case is shown above. The fix to the issue is:</td></td> - - <td><td>Extract the visited style even if link is unvisited during style - resolution.</td></td> - - <td><td>Generate a transition if either the visited or unvisited style - changed.</td></td> - - <td><td>animation.effect.getKeyframes reports unvisited style regardless of - whether visited.</td></td> - - <td><td>Visually render with the correct style. This is possible since the - interpolation code retains a pair of colors to interpolate corresponding to - the visited and unvisited style.</td></td> - -<td><td>Fix a crash in Mac IME fix</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/dpHdLwkQP2mvEqUTWU9WqebZlmcMHpkvca2sQQ_PDj6vI0xu_U5Gfuj2nZtp_1qr0sPM9ii3oWPPjHzGoT8yXVrrgF8Zoa48yDC5IrR91f9oJHF9nEqPZ63rcY_B3wkVntyVeRBHsQ" height=112 width=283></td></td> - -<td><td>flackr@ fixed a crash by performing a null check.</td></td> - -<td><td>Removed one fake user activation</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/UFQIE4kr5dmWZAXVGBKCYupnAMRfM5mnJOZzxQV5hNium6j1f8EZNgiiYpTU3ANfDA86IdaiwzE6A5ROxhkidFQSZ6c_41ESS9MmG-4TaIUx6Qva4YSktkMXi7RzNesE_lsQ6kTVaw" height=40 width=283></td></td> - -<td><td>mustaq@ fixed a fake activation issue as a suspect for <a href="http://crbug.com/1201355">a navigation problem</a>.</td></td> - - <td><td>UMA investigation revealed <a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1082258#c7"><0.005%</a> - page loads could be affected.</td></td> - - <td><td>Tentatively removed the fake user activation notification from JS - play() and everything seems good as before!</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Interop fixes</td></td> - -<td><td>Overscroll-behavior</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/S2OGqJ8UBP5vXu-AHhhmG08aQ8vAqNZiIfalExhOPEMLceQvuMFl46LyzwWSQ8z7GuIAN72tD8D1ggtAWgoxMyyMu3fT_mq_a7C8pEzfn6AJGJQpdqNOC9TBCy0ETSsiXw1rFtJ7Pw" height=249 width=219></td></td> - -<td><td>xidachen@ kept working on the <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=954423">bug</a>, where chrome propagates overscroll-behavior from the <body> element, while by spec it should be from the <html> element.</td></td> - - <td><td>A detailed <a - href="https://docs.google.com/document/d/1-pqljDgzzgRVve2oWUq237JPgtT12wcoctxbtBaHZdU/edit?ts=609ec0c2#heading=h.1xrzhx8chbuz">doc</a> - describing the problem.</td></td> - - <td><td>Break the feature counter into two cases. (<a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2896470">CL</a>)</td></td> - - <td><td>Querying UKM table shows that google.com is the major site that have - this problem.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: à la carte</td></td> - -<td><td>Bisecting on Android</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/m4--LoEEaNPk4c_0-r7W7qUQT-Mt9LxW1868uj1C_nkaaI0eRXELyBdeKBxezMPUxQOOYdeVdDp49kFfesUTzjUcnIH0LbsriCUxgNahkomeazrCDesL0A3wSlGxxz09goTyRACTzQ" height=197 width=283></td></td> - -<td><td>skobes@ found that it is quite annoying to bisect on Android, but it is possible, and also that the tool could be improved.</td></td> - - <td><td><a - href="https://docs.google.com/document/d/1e6IXv9hZQKeOsBx5ywjsBnqS0ZLW9kY2kald_RErJ0w/edit">go/chrome-android-bisect</a> - contains all the details on how to bisect on Android.</td></td> - - <td><td>skobes@ used that for two recent top-controls regressions</td></td> - - <td><td><a - href="http://crbug.com/1167400">crbug.com/1167400</a></td></td> - - <td><td><a - href="http://crbug.com/1207888">crbug.com/1207888</a></td></td> - -<td><td>AtomicString for PointerEvent type</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/-60-y1VG2NM4PHDvKf5ZjwIymMNYmYsGdxDZXwvQurFZFpIpsgzJ3VtVNqtOCofZHu0HEd8rPwAk6Wx89o2n4AhjHqLYtZL-fWGiwZuf5SIcEUDafQaa8NpUqOPuPFGQPw6uZ5vQ2A" height=222 width=283> <img alt="image" src="https://lh4.googleusercontent.com/FaaGEYPh_5yWVoGm20LLQ6CEutr55-nK29wKIhTRLLqcZ-4_oyH4A5NDAEcfVmcusUa04evUcPSucEzzCnDcnqcAU9PgdRL_vCikZY3xrpuE-EilMwRQZ4pB7YkE65zZx6r9O3qVdw" height=216 width=280></td></td> - -<td><td>flackr@ <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2878101">replaced char\* with AtomicString</a> for PointerEvent type. Why?</td></td> - - <td><td>The returned string is passed to PointerEventInit::setPointerType - implicitly cast to a WTF::string for the rest of its existence. What’s the - problem?</td></td> - - <td><td>First, we take the strlen of the string, which is O(n) - operation.</td></td> - - <td><td>Then, we allocate storage space and copy the string constant, which - is O(n) time + space.</td></td> - - <td><td>If we instead construct a String from another String, then it just - adds a ref to the StringImpl, and that’s O(1). Refer to the screenshot on - the left hand side for details.</td></td> - -<td><td>Now the String is constructed, are we done? Well, not yet, we have to compare two strings.</td></td> - - <td><td>Comparing two arbitrary Strings is O(n), see EqualStringView - implementation.</td></td> - - <td><td>But, comparing two AtomicStrings is O(1)! Refer to the screenshot on - the right hand side for details.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Bug Updates</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/9pOwepddVaq1FOyV6gnlnpNiwcjT7bJTpRPEsbmAF4_pHGvoXvHSXPVJT3564WtjQMcPaf2kBxdO8LI3PYbh6UAuL4knuYVgCgQK6hR3OdHwCATe4UcB1-B8z_I02CMj6XCpIBSbcA" height=155 width=280> <img alt="image" src="https://lh3.googleusercontent.com/DQwfAQnP-zJ455WAFGOv6VvpLyKTwXBlBTnDiz9EopH_xeLuGmQVvFH-OqjbEqjBczQfcHPpe-lW4yxg7v5iQ5P09SRMiVUXYdRMriK-oNKkfctmtimxAfJEaVsLIPTwTFN7ZMgEMg" height=153 width=278></td></td> - -<td><td>Our team kept on top of bugs. We closed almost the same amount of P1 bugs vs opened P1 bugs.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | June 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/june-2021-vol-2---new-features-stability-fixes-interop-fixes-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/june-2021-vol-2---new-features-stability-fixes-interop-fixes-and-more/index.md deleted file mode 100644 index 1f6097c43ff..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/june-2021-vol-2---new-features-stability-fixes-interop-fixes-and-more/index.md +++ /dev/null @@ -1,240 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: june-2021-vol-2---new-features-stability-fixes-interop-fixes-and-more -title: June 2021 (Vol 2) - New features, stability fixes, Interop fixes and more! ---- - -<table> -<tr> - -<td>June 2021 (Vol 2)</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll Unification: fix autoscroll crash</td></td> - -<td><td>kevers@ fixed an autoscroll crash. There are few problems including:</td></td> - - <td><td>WeakPtrs to the same object were dereferenced on different - threads.</td></td> - - <td><td>Waiting for input to be processed on main</td></td> - - <td><td>Waiting for a main thread hit test on the compositor</td></td> - -<td><td>Here are the fixes:</td></td> - - <td><td>WidgetInputHandlerManager is now ref counted.</td></td> - - <td><td>Safe to pass around the “this” pointer for callbacks that will run - on the compositor.</td></td> - - <td><td>Use AsWeakPtr only for callbacks that will be run on the main - thread.</td></td> - - <td><td>Fixes 5 crashing tests!</td></td> - -<td><td>Scroll Unification: untangling iframe issues</td></td> - -<td><td><img alt="chain.png" src="https://lh6.googleusercontent.com/GF5f11bWr7884waypGiE3bi4y-AEY-OWfnVskKZlpAfGuLvFak_GwhKYVOfaJMocFKSX6zEsg7ytdkkqej1kRACQO_oIeAcS7O-Og690MGOnW2gZ_T6LxG9h17QxAaikOAAMVLA7ZJlmSOF6E481OYnLBiSzkCoe7DF0yxBvOf0gKafc" height=190 width=279></td></td> - -<td><td>skobes@ landed the <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2983821">CL</a> to handle the case when a scroll hits an iframe that isn’t scrollable for some reason. In this case, we need to look for scrollable container in the parent frame.</td></td> - -<td><td>Composite BG-color animation</td></td> - -<td><td>xidachen@ fixed two crash cases.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/lIiIaL2x898PdeBhWHW8u22XUNxlSPfhGHbIRsbbVcLhWEq7ornl3q_7rqwz85Eqt2wOmtrue4nsh4Jr0rVb9-JqMtVBum-9M0y_W05tuPEaWwJbfwIh-Mqd5WQRvfmcQLBmCPoVlGkSsc0pw4774yejCh96gNjknKZIWCyq--RxPayt" height=76 width=283></td></td> - -<td><td>The first case is shown above where the frame is detached during animation. The fix landed <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2951382">here</a>.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/_yovKVwj7Cc83Md-0ngT8poGR47TZ24Xs5qvWizKG_aWszkI_gKZwblELJCEksA8_JGcHB___vtzdsHpvSUEJTtByTLafZFbrqdRTEU0Lyv8ttXBhfYiEiGLNjBIozw90YO26V6mzdYCOa_HoJxYx8CnFP4Pj5QsRUyDRgMqxZ4Y6-kN" height=157 width=141></td></td> - -<td><td>The second case is shown above, and the crash is due to antialiasing that changes the draw operation bounds. This is the <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2954479">fix</a>.</td></td> - -<td><td>Progress based timelines/Scroll Timelines</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/sXJITc1_VocnlLddIAps2gR_spLrMg3hNfh1OfeKOdMn8S0WSTEoIqcBTat3D_6PJEn94VejqwJVbDJrBi72Q401j9syWMLmmwnNGCEo-fouH0tC8VVdr9sjpHneH24A6PFe9kjugsJXltHSN8iN7DYRFtL53G4fPc5wAOFZZLwSJ-bv" height=200 width=283></td></td> - -<td><td>kevers@ made a lot of progress on <a href="https://drafts.csswg.org/web-animations-2">specs</a>. </td></td> - -<td><td>Highlights:</td></td> - - <td><td>No longer need time-range for a scroll timeline; Times are converted - to percentages. (<a - href="https://github.com/w3c/csswg-drafts/pull/6410">patch</a>)</td></td> - - <td><td>Support duration = ‘auto’ (<a - href="https://github.com/w3c/csswg-drafts/pull/6337/">patch</a>)</td></td> - -<td><td>Here’s an example of un-timed timelines:</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/-pz0DHZNano7yrdoIHbn_3L08AT_InCiZDZ7A8uvHkgf1csjMi-2M1PJV6YnGb5Sjqyk1ozrW3TvmhIr0AucjD8FTfWpSm1qUX7atIsK2NUePkd48J1gp4HLBzrbMABQ6seLIRdAy6io1qeUvy6MadntwNpOw12W4dCdx9Ta-8ah0hro" height=124 width=283></td></td> - -<td><td>Another example of empowering progress based animations</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/sOOLJ5DSjTrxW8oYTqIHccfgzcUvqe2c8Z70ao3NeQH7rtIDIwLu6dvtH3GeHTKOPAjdWm9kIwixT6ZbQdUvHgdFKRAdDZ3_2ewjncEoeZkodfSUw8BqK5tEG2EC-8CJwY7WlpXy8vUJ9be6EJdHF89jsajz_dmehjYkiy75rRMc0DJe" height=155 width=215></td></td> - - <td><td>Normalization procedure to convert time-based animations to - progress-based.</td></td> - - <td><td>Animations are scaled to 100% with iteration and delays adjusted - accordingly.</td></td> - - <td><td>Smooth integration with web-animations API</td></td> - -<td><td>Capability Delegation is ready for TAG review</td></td> - - <td><td>mustaq@ <a - href="https://github.com/w3ctag/design-reviews/issues/655">kicked off</a> a - TAG review for the <a - href="https://wicg.github.io/capability-delegation/">explainer</a> and the - <a href="https://wicg.github.io/capability-delegation/spec.html">draft - spec</a>.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/DTQM0AAbpo4H-S7bcy9udCr-jtZ4QenLeuLj6qu_C-HloTqU51QYym46H5gYpYoGN8TQBCqPRt_J91bfgicQfD1706FD7n2eHxcXzhbJTxqw19M9XJy-oVpZOLnebaoqy3PCFSSjIABAAAd61QwsZN8h8Sl74mghfvGMKZbMwEOzBXyj" height=83 width=256></td></td> - - <td><td>Also investigated possible shipping options and finalized <a - href="https://docs.google.com/document/d/1L66B1QtqHCzAKlLQXdtv-YCmlXrJhi2Je2Vo91XWMsQ/edit?usp=sharing">a - plan</a> working with smcgruer@ (Web Payments) and jyasskin@ (Web - Standards).</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Stability fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>DCHECK in ConvertTimingForCompositor</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/eyBq9_FmfclUlfQjaMQmR5adk-l1XtWKism64bdBFe0qbCFnFEiCztGpEhF5olqDkZNr-ggEO28XfJ9t2MGgILKt6a-890Vvsz9mWiS5cYTNNIMAXgsStdc55cjCYdO9ZOIjhiDfjQpER8Njl16ghE6oEKQ8Cdlt8G2XzDXVEQwU1BbU" height=163 width=283></td></td> - -<td><td>This function did a bunch of math to check whether the result is finite or not, then either abort or carry on. But what if the intermediate result is indeterminate?</td></td> - -<td><td>To solve that, we check intermediate results if there is any risk of the following in subsequent calculations:</td></td> - - <td><td>infinity - infinity</td></td> - - <td><td>0 / 0</td></td> - - <td><td>infinity / infinity</td></td> - - <td><td>Division by zero</td></td> - -<td><td>FullscreenControllerInteractiveTest flaky fix</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/ATmakcwLRkU0fhQgB3lhLXeJry1hUqEuSkZ9OB_Y6HXVuTsg0Q4kDYWlzGUg6la_dmmlxhtO5CuA0M7ToABMYZXutB04sXdz5SaseLymhW45u0-nWRu5VnVeMNIq_ohJlI1pa1AoJ0z3E_2KhMp924z0ryu-4oGHAICgPTP_O6A7tWxM" height=44 width=283> </td></td> - -<td><td>mustaq@ found an issue that might cause flakiness in a large suite of tests: an <a href="https://source.chromium.org/chromium/chromium/src/+/main:net/test/embedded_test_server/embedded_test_server.h;drc=172a2a554e8b556203c962152d3b19d55240725d;l=341">initialization problem</a> with EmbeddedTestServer could be causing flakiness in all FullscreenControllerInteractiveTests! A <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2969924">fix</a> has been landed, and we’re hopeful that flakiness will be greatly reduced moving forward.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Interop fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Fix interpolation of integers</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/dwWcE_WQ7lAnDlzDHXYS4PX74JG45uW1NkiqcVk_jHGHWcftBOl9VGSk8HgiGNQ4FqxAkKEDpaSaS2a185e2i3jqNrUVjra8HJFGsYvafm3QfjVApujEw_OgnLB-abUQIMVbSsQo_D4wz-3YINcUx5px_w77bzy8cLZ-AcJUSXNoDgNv" height=268 width=283></td></td> - -<td><td>The test case above demonstrates a bug: the 8 digit CSS number was serialized to 6 significant digits, and the out-of-bounds treatment turned it into a 0..</td></td> - -<td><td>Below is the fix to the problem.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/7VFctlPazHy6OcCxSRmLho80W_1aRSct288IUC88n4aA-mlgpWy7OGMJLnRqcl-9y4gZ04A8h9qCI5i9i-j1dXZhvcl9NFwDx6JXTh_VnOWn3djnBh0taY3ichwvnmSlIMHTcKDDPE1TYSDUiq2QIS4lQvdv_h2qdmlrLThih4j8UZg3" height=47 width=283></td></td> - -<td><td>overscroll-behavior</td></td> - -<td><td>Our ongoing effort to reduce mis-usage of overscroll-behavior (<a href="https://docs.google.com/document/d/1-pqljDgzzgRVve2oWUq237JPgtT12wcoctxbtBaHZdU/edit#heading=h.1xrzhx8chbuz">details</a> here) moved forward with a fix landing on Google Search.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/AbvzIFWaIWqOw7OrIaCNCm-UlAonjWT78-em1KgWUDV4cDzbEPzdgFSlRhemYow7gzCrffeb7nMrj7c72IkFAAQdN9ZT9-XmzEjPDHMudAU52i_PAUcU8QaS_oEayjSLxvrOM7Z5n9ae_z6-0qbC1d92JeU-kFD2ELY3lRswb8q9zGbv" height=59 width=283></td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/pzrNAt-Kl8VKbRTrvOvrtQLcFb7im-nW5--4Wx_BNkOCa-ZL3MIOWXyzbrPRz_PR8A6dyCoUHITbPe-6PjOYvDy4Vt7b4G-xQ4PSq95b7gPqUTbpyDkcyHpuKyBwD_6YWIG_jfjHMRoaKYoSv4PXtdi7RKXltISb0zih3FeC5vG29dCi" height=105 width=283></td></td> - -<td><td>The first graph shows the usage on Google, and the second graph shows the usage of all page load, which is about 0.3%.</td></td> - -<td><td>There are two ways to move this forward:</td></td> - - <td><td>Through devrel outreach (<a - href="https://docs.google.com/document/d/1-pqljDgzzgRVve2oWUq237JPgtT12wcoctxbtBaHZdU/edit#heading=h.1xrzhx8chbuz">doc</a>)</td></td> - - <td><td>Push a spec change (<a - href="https://github.com/w3c/csswg-drafts/issues/6406">proposal</a>)</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Position: sticky 100% pass rate on chrome!</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/eNLvAI5MdHjZRW1284KVgALG5aQcZUluy3twk8P9GsZyr6XsfvXlTb0s3ZBjx_C8nGiy7F2LNFVsnlXIHT8Rr4ofTVtuhDxA2OaXu0BpLokp99uOff3GpAIM05Y24HtZCNE54glfHGM6kZX2HSzobneiU-46_SMZA-dZjohBHddExuM9" height=135 width=283></td></td> - -<td><td>flackr@ wrapped up one of our team’s key product excellence/interop OKRs by fixing all WPT tests for position:sticky. Thanks to all the folks on the DOM team that contributed. (<a href="https://wpt.fyi/compat2021?feature=position-sticky">link</a>)</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Bug Updates</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/DgKWR43wOdhft-vh_ub8eFt_JbD7XgQ4r4mFRz1DRPLdLvd2RmZI4rnzkPmD1nnkYPYXPXGYB1QglE3LFnB2FFW-oZ_O4CBqgwLn16DG9YlutSRXV2-xDU6SQ2B8HjG93Jl2OSwxO3lpHqVPlVk_tf7IrmXl7Xsh4ukG0KcyQl5i9aBo" height=159 width=288> <img alt="image" src="https://lh4.googleusercontent.com/x5OkzI6ZArtT0yPVOCJoEmt_fxe7tCcE_L5pq5eZ_4uns0qpnNfmQErEXdu3iq9mCaVBgg3jxjIqH-OqRRbGQueSwqi8NJN91sRc8xVcw_YBGAntWLmXtQblkkYtrl3dzT6me0wNvIyfr_8dqiK6UudVqcXv4vPbveQ6gOx1rsMF44ZS" height=158 width=284></td></td> - -<td><td>Our team made great progress on fixing P1&P2 bugs and the numbers are going down!</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | June 2021 (Vol 2)</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/march-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/march-2019/index.md deleted file mode 100644 index 88e23a54225..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/march-2019/index.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: march-2019 -title: March 2019 ---- - -<table> -<tr> - -<td>MARCH 2019</td> - -<td>Chrome Animations Highlights</td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/bT81a8VO0AgQk_m0F1KqBnoC5oYBcHNHpgknmtbpr3qLjsrHM3F0GE3K20VzUDlXjx47SUe7K1oV0GLC7Xcs1hEfMOc3hKuMCIbwR2XR1hrRBTMB8Q8pTK4EOp5YPIK3e0H6Qh21" height=181 width=185></td></td> - -<td><td>Degenerate case in computing sign of quaternions. </td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/dvKfGyIqut3spwESpQ5gUXzdfMs8FvL5OndVdmtFSd9tynbci3E1z3xCO3G3lZA2Y2mq9Ypu1dU9SX_3yUjicYe0lGHi5iFKX8FPyVLNyVKARi0xqB0OBofd1vUlusUVi_ZuFrIF" height=181 width=185></td></td> - -<td><td>Step 1: Fix quaternion calculations. Avoid degenerate edge cases.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/MYDxbzoQPU76BSHi8UQawTmlX9eDDWuEBD7kyjtvQUQv8Gy5_RCbaem7xEdbNAukqTiuyNWRvTJNG4RXp9KQgu_xphSZLuwaHU22Deo6e3T5879Rj-x9Jz8SXuCgl_DNesljbp8o" height=181 width=185></td></td> - -<td><td>Step 2: Support 2D matrix decomposition.</td></td> - -<td></tr></td> -<td></table></td> - -<td>Improved 3D and 2D transform animations</td> - -<td>We have continued to address 2D and 3D matrix decomposition issues that were causing transform animation and interop bugs. Above is one example but 16 more wpt tests are now passing in Chrome. The fact that there are two implementations (in Blink and Skia) of the same matrix operations is not helpful and we are considering options to consolidate them.</td> - -<td>This work help identify inconsistencies and inaccuracies in the css-transform specification for which issues have been filed: <a href="https://github.com/w3c/csswg-drafts/issues/3709">1</a>, <a href="https://github.com/w3c/csswg-drafts/issues/3710">2</a>, <a href="https://github.com/w3c/csswg-drafts/issues/3711">3</a>, <a href="https://github.com/w3c/csswg-drafts/issues/3712">4</a>, <a href="https://github.com/w3c/csswg-drafts/issues/3713">5</a>.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/BQeMOUyYU4rbjq7gr7IOZD-LfcTsBwYbnPWF5yfh-rAex7JNjMTeVC8hNQxrsl3Pawcx1y6TOutPkgG2jS5RRYFbI1-_8Du9YqX0uw-V3xpwcBG6sYw6D20VUCjN4POBqf2LdpV3" height=291 width=164></td></td> - -<td><td>Existing implementation using scroll events.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/qP-hDF8ZwIY3DLAxCX4pXhO4Qc3OVVEHHcSnzsjJUP6LgBdCwWG1Kq6yZsNkXRulL8QkYhHoI-WQtl3aEOV4xUeapzwmxxKd7YvyB9PWmPdB2Suo91aD3H69x6X1F_pl133XX8Bm" height=286 width=160></td></td> - -<td><td>New “Buttery Smooth” impl using Animation Worklet and Scroll Timeline.</td></td> - -<td></tr></td> -<td></table></td> - -<td>AMP Origin Trial Updates</td> - -<td>AMP animation team has a near complete<a href="https://github.com/ampproject/amphtml/blob/master/extensions/amp-animation/0.1/runners/scrolltimeline-worklet-runner.js"> re-implementation</a> of their<a href="https://ampbyexample.com/visual_effects/basics_of_scrollbound_effects/"> scrollbound effect</a> system using Scroll Timeline and Animation Worklet. They have identified<a href="https://docs.google.com/document/d/1TZBb88apJ41Ibi3mued5ZB0Z9YY7h83UjAi2Q9b1fQM/edit#heading=h.eb8fxcagf7ig"> gaps</a> in the API which we collaborated on an<a href="https://docs.google.com/document/d/1XFPgy3g57njeesgJdbVSc2x8vZJQFAJBxUwuHLc3VXs/edit?usp=sharing"> action plan</a> to address (mainly by proposing changes to Scroll Timeline API). It was also decided to<a href="https://groups.google.com/a/chromium.org/d/msg/blink-dev/AZ-PYPMS7EA/kffOspnyBwAJ"> extend</a> the origin trial to allow AMP's new implementation to be gradually turned on for real users - which also helps us learn more about the performance of these features at scale.</td> - -<td>Here is a<a href="https://drive.google.com/open?id=1WqNNyJC1r9yUoYTgATlRX4mYIPo8R3yU"> recording</a> of the<a href="https://amp-article.herokuapp.com/"> demo</a>. (To run locally enable experimental web platform feature flag and enable relevant AMP experiment using \`AMP.toggleExperiment('chrome-animation-worklet')\` in devtools console)</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/OyXkbEam5SYQ1dD04AR3HrX-hQ6z2fklO7BTRRPy5ZYFqVPwctNRQbXTcp4JgxA95sPL99cQUfixsSOWmr4g8mdbONwlKX2iN9oMBxAPPGD9Qlc4pkIKxXuYGhh70Pqk2vDaGWL9" height=125 width=283></td></td> - -<td><td>Viz Hit-Testing Surface Layer</td></td> - -<td><td>Finch trial is showing improvement over previous Draw Quad version. We are seeing 14%/8%/5% improvements in hit test requests answered in the fast path on <a href="https://uma.googleplex.com/p/chrome/variations/?sid=7bf43df040ce9f90cbea1e762c5c03d5">Windows</a>/<a href="https://uma.googleplex.com/p/chrome/variations/?sid=035b5f6d5f7ca030b7887f5b4e7f6b07">MacOS</a>/<a href="https://uma.googleplex.com/p/chrome/variations/?sid=e16a589895889a2310b4bc5f4387b43c">Android</a>, with 8% regressions on <a href="https://uma.googleplex.com/p/chrome/variations/?sid=2ffbcd8b59f4a74e05490d98f34cb579">Linux</a> (under investigation). Across all platforms, <a href="https://uma.googleplex.com/p/chrome/variations/?sid=5a3437665f748a4b4bcc679013900143">hit testing error rates</a> are lower than 0.05%.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/PdcNk4yzu3sVovMt1mQcuDwfoinb7N2EwvpdAgdC16SVQbeJOY-9snyuxO48NMCN2K0QrWH3S7uw7VJG-dWxEMJO_7b6Qpl6rrULnaV-garO2ER_s6st0NgQp01PECa9Yc3-HViY" height=123 width=283></td></td> - -<td><td>Compositor Touch Action</td></td> - -<td><td>Finch trial is showing promising <a href="https://uma.googleplex.com/p/chrome/variations?sid=4d04b0905ac90bafd4b63b39754ae20e">early results</a>. ScrollBegin latency improves 5% @50pct and 13% @99pct. ScrollUpdate latency improves 1% @50pct and 3% @99pct.</td></td> - -<td></tr></td> -<td></table></td> - -<td>Off-Main Paint Worklet</td> - -<td>We made good progress by completing implementation of multiple sub-components: <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1426015">rasterization</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1479658">raster-caching logic</a> and <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1497032">lookup</a>. Work is in progress for <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1495445">dispatch logic</a>, and a new approach to share data between blink and cc for paint info (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1497217">1</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1504229">2</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1506653">3</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1506818">4</a>). </td> - -<td>Animation Worklet</td> - -<td>Animation Worklet is now fully <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=791280">asynchronous</a> in CC with proper scheduling in place. With <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=915352">help</a> from Microsoft engineers our tests have been upstreamed to <a href="https://wpt.fyi/results/animation-worklet?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned&q=animation-worklet">web-platform-tests</a> and most critical flakiness issues are resolved. Specification has been updated (<a href="https://github.com/w3c/css-houdini-drafts/commit/3c1cd1b3babc49a92d7a5079f9de77df67d06775#diff-6547a8c38ca0bdc51fd63edeaa4b66b3">1</a>, <a href="https://github.com/w3c/css-houdini-drafts/commit/93ab72f8abee1ac008eb4b5292265633387381fc#diff-6547a8c38ca0bdc51fd63edeaa4b66b3">2</a>, <a href="https://github.com/w3c/css-houdini-drafts/commit/cf1a69a4c9dd165f53df7ba7d68c329287ab2659#diff-6547a8c38ca0bdc51fd63edeaa4b66b3">3</a>) and <a href="https://github.com/w3ctag/design-reviews/issues/349">TAG review</a> requested. Aiming to ship without Scroll Timeline in M75.</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Updates | March 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/march-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/march-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more/index.md deleted file mode 100644 index ca10364d93c..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/march-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more/index.md +++ /dev/null @@ -1,222 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: march-2020---web-animations-scroll-linked-animations-throughput-metrics-and-more -title: March 2020 - Web Animations, Scroll-linked Animations, Throughput Metrics and - more! ---- - -<table> -<tr> - -<td>March 2020</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td>The Animation Festival</td> - -<td>The team made solid progress towards moving Web-Animations forward, as you can see in these demos from Kevin (kevers@) and Hao (haozhes@)!</td> - -<td>A kinder gentler cancel - add support for animationcancel</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/n-dDYATk36izRhk8Cz3rT5xe0LszrOxy-N912z4UE_mNyXXye1zW1yeEqfyi9Ab74tZkNrOPLhkeSXIsMMx5is5yKSy9LxB47Gf2yyNG7dqqCKzS0KNPbGqsVeWaKK3U0VZcDArE" height=132 width=272></td></td> - -<td><td>This example illustrates using a combination of CSS animations and CSS transitions, getAnimations, commitStyles and animationcancel to smoothly reset the state of a cancelled CSS animation.</td></td> - -<td><td>Performing a commit style prior to cancelling the animation prevents the animation from snapping back to the start position.</td></td> - -<td><td>Within the animationcancel listener we can smoothly transition back to the starting point by triggering a CSS transition.</td></td> - -<td><td>#box {</td></td> - -<td><td> transition: transform 0.5s ease-in-out;</td></td> - -<td><td>}</td></td> - -<td><td>.slide {</td></td> - -<td><td> animation: ...</td></td> - -<td><td>}</td></td> - -<td><td>document.addEventListener(</td></td> - -<td><td> 'animationcancel', (evt) => {</td></td> - -<td><td> if(evt.target != box) return;</td></td> - -<td><td> // Smoothly transition back to</td></td> - -<td><td> // starting point.</td></td> - -<td><td> box.style.transform = 'none';</td></td> - -<td><td>});</td></td> - -<td><td>function slide() {</td></td> - -<td><td> box.classList.add('slide');</td></td> - -<td><td>}</td></td> - -<td><td>function reset() {</td></td> - -<td><td> document.getAnimations().</td></td> - -<td><td> forEach(animation => {</td></td> - -<td><td> animation.commitStyles();</td></td> - -<td><td> animation.event.target.</td></td> - -<td><td> classList.remove('slide');</td></td> - -<td><td> });</td></td> - -<td><td>}</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Taking the scenic route - fix CSS transition events after updating the effect</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/h4X1AOZRN5TrzSKcCke98ILTBrzYtCcgQR2XwnDubxcZModEokR37BGkqacpWaFoPNSt7TdWsiDA25l8RgSVEYQsR4_ynoNVOsHPnb4dV3jh4JlywYBgArRAYwju_3xHNqJ8N5ib" height=61 width=265></td></td> - -<td><td>This example demonstrates a means of customizing the path of a transition by replacing the keyframe effect.</td></td> - -<td><td>After changing the effect, events still need to be directed to the original target. Previously, changing the effect resulted in dropping the transitionend or tansitioncancel event, which in turn broke the chain of transitions.</td></td> - -<td><td>document.addEventListener(</td></td> - -<td><td> 'transitionrun', (evt) => {</td></td> - -<td><td> if (evt.propertyName !=='transform')</td></td> - -<td><td> return; </td></td> - -<td><td> const animation = circle.getAniamtions()</td></td> - -<td><td> .find(anim =></td></td> - -<td><td> anim.transitionProperty ===</td></td> - -<td><td> 'transform');</td></td> - -<td><td> animation.effect =</td></td> - -<td><td> new KeyframeEffect(circle,</td></td> - -<td><td> keyframes,</td></td> - -<td><td> options);</td></td> - -<td><td>});</td></td> - -<td><td>document.addEventListener(</td></td> - -<td><td> 'transitionend', (evt) => {</td></td> - -<td><td> circle.style.opacity = 0;</td></td> - -<td><td>});</td></td> - -<td><td>// … wait until rendered … </td></td> - -<td><td>circle.style.transform =</td></td> - -<td><td> 'translateX(200px)';</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Playing nicely together - CSS Animation / Web Animation API interactions</td></td> - -<td><td colspan=2><img alt="image" src="https://lh5.googleusercontent.com/AgXlDRi8AKQKKAxYgJ2SdFhDjIvVYtKe2d00lYtqS88DvxrkUUOP-rq7_X0dU9R6cSKKMgkQxiLA8JypElSTPRY5n35KlS5vP-UeTBEDOeksnGufimjfVM0G0fsMWQUfYybDnOLw" height=119 width=580></td></td> - -<td><td colspan=2>This demo illustrates how AnimationEvent.updateTiming overrides properties set via CSS properties. The updateTiming API may be used to set/override one or more animation properties. A subsequent change via CSS animation properties must not replace values set via the API call. The override behavior is on a per-property basis.</td></td> - -<td><td colspan=2>Resolve animation ordering issues with free vs markup bound animations</td></td> - -<td><td colspan=2><img alt="image" src="https://lh4.googleusercontent.com/HNr4kbgj998Pe7W1MmP8PM7JvWnPhmOaezC3q4F8WJ7oX7F9LjJw2wm_6JCj3L4SNSWEMaipsGlOClXVyIapJJpv35kX8-zPpTuNiaNwScjH-jHxN0SnKbLrOuytmZrtuHadNNzv" height=249 width=453></td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>This example illustrates effect ordering and composite: add. Each rectangle starts with a pair of animations: a web animation (scale), and a CSS animation (rotation). As the CSS Animation has lower composite ordering, the resultant animation is “rotate then scale” which indicates the expected result from before. In the left rectangle, we grab a reference to the CSS Animation before cancelling (clearing the animation property). When the rotate animation is replayed, it is now a “free” animation and the ordering flips to be creation order: i.e. “scale then rotate”. Since scale and rotate operations are not commutative, we can find the end results are different from the left to right.</td></td> - -<td><td colspan=2>--- To be continued ---</td></td> - -<td><td colspan=2>Special thanks to Rob (flackr@) and Majid (majidvp@) who reviewed 40+ non-trivial patches for the excellent work.</td></td> - -<td><td colspan=2>Scroll-linked Animations</td></td> - -<td><td colspan=2>On the standardization front, Majid triaged all outstanding specification issues and identified <a href="https://github.com/w3c/csswg-drafts/milestone/6">12 of them</a> as P1 for the First Public Working Draft (FPWD). Rob proposed <a href="https://github.com/w3c/csswg-drafts/issues/4862">progress-based animations</a> for cleaner developer ergonomic (<a href="https://github.com/w3c/csswg-drafts/pull/4890">pull request</a>) getting rid of the arbitrary duration that is currently needed. And Olga (gerchiko@microsoft.com) drove the discussion on the inactive timeline spec <a href="https://github.com/w3c/csswg-drafts/issues/2066">issue</a> and proposed the timeline state <a href="https://edotor.net/?engine=dot#digraph%20G%20%7B%0A%20%20node%20%5Bfontsize%3D8%5D%3B%0A%20%20%2F%2F%20States%0A%20%20%22Idle%22%20%5Blabel%3D%22Idle%5CnST%20%3D%20null%5CnHT%20%3D%20null%5CnTask%20%3D%20none%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dunresolved%5Cnplay_state%3Didle%22%5D%0A%20%20%20%20subgraph%20cluster_0%20%7B%0A%20%20%20%20%20%20%20%20style%3Dfilled%3B%0A%20%20%20%20%20%20%20%20color%3Dlightgrey%3B%0A%20%20%20%20%20%20%20%20node%20%5Bstyle%3Dfilled%2Ccolor%3Dwhite%5D%3B%0A%20%20%20%20%20%20%20%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20%5Blabel%3D%22Play-pending%20HT%5CnST%20%3D%20null%5CnHT%20%3D%20resolved%5CnTask%20%3D%20play%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Drunning%22%2C%20color%3Dyellow%5D%0A%20%20%20%20%20%20%20%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20%5Blabel%3D%22Play-pending%20ST%5CnST%20%3D%20resolved%5CnHT%20%3D%20null%5CnTask%20%3D%20play%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dnull%5Cnplay_state%3Drunning%22%2C%20color%3Dlightyellow1%5D%0A%20%20%20%20%20%20%20%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20%5Blabel%3D%22Pause-pending%20HT%5CnST%20%3D%20null%5CnHT%20%3D%20resolved%5CnTask%20%3D%20pause%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Dpaused%22%2C%20color%3Dlightskyblue1%5D%0A%20%20%20%20%20%20%20%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20%5Blabel%3D%22Pause-pending%20ST%5CnST%20%3D%20resolved%5CnHT%20%3D%20null%5CnTask%20%3D%20pause%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dnull%5Cnplay_state%3Dpaused%22%2C%20color%3Daquamarine2%5D%0A%20%20%20%20%20%20%20%20%22Running%20(TL%20Inactive)%22%20%5Blabel%3D%22Running%5CnST%20%3D%20resolved%5CnHT%20%3D%20null%5CnTask%20%3D%20none%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dnull%5Cnplay_state%3Drunning%22%2C%20color%3Dlemonchiffon2%5D%0A%20%20%20%20%20%20%20%20%22Paused%20(TL%20Inactive)%22%20%5Blabel%3D%22Paused%5CnST%20%3D%20null%5CnHT%20%3D%20resolved%5CnTask%20%3D%20none%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Dpaused%22%2C%20color%3Dgold1%5D%20%20%20%20%20%20%0A%20%20%20%20%20%20%20%20label%20%3D%20%22Timeline%20Inactive%22%3B%0A%20%20%20%20%7D%0A%0A%20%20%20%20subgraph%20cluster_1%20%7B%0A%20%20%20%20%20%20%20%20node%20%5Bstyle%3Dfilled%20fontsize%3D8%5D%3B%20%20%20%20%20%0A%20%20%20%20%20%20%20%20label%20%3D%20%22Timeline%20Active%22%3B%0A%20%20%20%20%20%20%20%20color%3Dblue%0A%20%20%20%20%20%20%20%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20%5Blabel%3D%22Play-pending%20HT%5CnST%20%3D%20null%5CnHT%20%3D%20resolved%5CnTask%20%3D%20play%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Drunning%22%2C%20color%3Dyellow%5D%0A%20%20%20%20%20%20%20%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20%5Blabel%3D%22Play-pending%20ST%5CnST%20%3D%20resolved%5CnHT%20%3D%20null%5CnTask%20%3D%20play%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Drunning%22%2C%20color%3Dlightyellow1%5D%0A%20%20%20%20%20%20%20%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20%5Blabel%3D%22Pause-pending%20HT%5CnST%20%3D%20null%5CnHT%20%3D%20resolved%5CnTask%20%3D%20pause%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Dpaused%22%2C%20color%3Dlightskyblue1%5D%0A%20%20%20%20%20%20%20%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20%5Blabel%3D%22Pause-pending%20ST%5CnST%20%3D%20resolved%5CnHT%20%3D%20null%5CnTask%20%3D%20pause%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Dpaused%22%2C%20color%3Daquamarine2%5D%0A%20%20%20%20%20%20%20%20%22Running%20(TL%20Active)%22%20%5Blabel%3D%22Running%5CnST%20%3D%20resolved%5CnHT%20%3D%20null%5CnTask%20%3D%20none%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Drunning%22%2C%20color%3Dlemonchiffon2%5D%0A%20%20%20%20%20%20%20%20%22Paused%20(TL%20Active)%22%20%5Blabel%3D%22Paused%5CnST%20%3D%20null%5CnHT%20%3D%20resolved%5CnTask%20%3D%20none%5Cn%3D%3D%3D%3D%3D%3D%3D%5Cncurrent_time%3Dresolved%5Cnplay_state%3Dpaused%22%2C%20color%3Dgold1%5D%0A%0A%20%20%20%20%7D%0A%20%20%0A%20%20%0A%20%20%2F%2F%20Idle%20state%0A%20%20%22Idle%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Idle%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Idle%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Idle%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%0A%20%20%2F%2F%20Play-pending%20(HT%2C%20TL%20Active)%20state%0A%20%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Running%20(TL%20Active)%22%20%5B%20label%3D%22ready%22%20style%3Ddashed%20%5D%0A%20%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22Inactive%22%20color%3D%22gray%22%20%5D%0A%0A%20%20%2F%2F%20Play-pending%20state%20(ST%2C%20TL%20Active)%0A%20%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Running%20(TL%20Active)%22%20%5B%20label%3D%22ready%22%20style%3Ddashed%20%5D%0A%20%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22Inactive%22%20color%3D%22gray%22%20%5D%0A%0A%20%20%2F%2F%20Pause-pending%20(HT%2C%20TL%20Active)%20state%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Paused%20(TL%20Active)%22%20%5B%20label%3D%22ready%22%20style%3Ddashed%20%5D%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20-%3E%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22Inactive%22%20color%3D%22gray%22%20%5D%0A%0A%20%20%2F%2F%20Pause-pending%20(ST%2C%20TL%20Active)%20state%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Paused%20(TL%20Active)%22%20%5B%20label%3D%22ready%22%20style%3Ddashed%20%5D%0A%20%20%2F%2F%20(Following%20is%20the%20aborted%20paused%20behavior)%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22Inactive%22%20color%3D%22gray%22%20%5D%0A%0A%20%20%2F%2F%20Running%20state%0A%20%20%22Running%20(TL%20Active)%22%20-%3E%20%22Running%20(TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Running%20(TL%20Active)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Running%20(TL%20Active)%22%20-%3E%20%22Running%20(TL%20Inactive)%22%20%5B%20label%3D%22Inactive%22%20color%3D%22gray%22%20%5D%0A%0A%20%20%2F%2F%20Paused%20state%0A%20%20%22Paused%20(TL%20Active)%22%20-%3E%20%22Paused%20(TL%20Active)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Paused%20(TL%20Active)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Paused%20(TL%20Active)%22%20-%3E%20%22Paused%20(TL%20Inactive)%22%20%5B%20label%3D%22Inactive%22%20color%3D%22gray%22%20%5D%0A%20%20%0A%20%20%2F%2FPlay-pending%20(HT%2C%20TL%20Inactive)%20state%0A%20%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22Active%22%20color%3D%22black%22%20%5D%0A%20%20%0A%20%20%2F%2FPlay-pending%20(ST%2C%20TL%20Inactive)%0A%20%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22Active%22%20color%3D%22black%22%20%5D%0A%20%20%0A%20%20%2F%2FPause-pending%20(HT%2C%20TL%20Inactive)%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Pause-pending%20(HT%2C%20TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(HT%2C%20TL%20Active)%22%20%5B%20label%3D%22Active%22%20color%3D%22black%22%20%5D%0A%20%20%0A%20%20%2F%2FPause-pending%20(ST%2C%20TL%20Inactive)%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20-%3E%20%22Play-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Active)%22%20%5B%20label%3D%22Active%22%20color%3D%22black%22%20%5D%0A%20%20%0A%20%20%2F%2FTL%20Inactive%0A%20%20%22Running%20(TL%20Inactive)%22%20-%3E%20%22Running%20(TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Running%20(TL%20Inactive)%22%20-%3E%20%22Pause-pending%20(ST%2C%20TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Running%20(TL%20Inactive)%22%20-%3E%20%22Running%20(TL%20Active)%22%20%5B%20label%3D%22Active%22%20color%3D%22black%22%20%5D%0A%20%20%0A%20%20%2F%2FPaused%20(TL%20Inactive)%0A%20%20%22Paused%20(TL%20Inactive)%22%20-%3E%20%22Paused%20(TL%20Inactive)%22%20%5B%20label%3D%22pause()%22%20color%3D%22green%22%20%5D%0A%20%20%22Paused%20(TL%20Inactive)%22%20-%3E%20%22Play-pending%20(HT%2C%20TL%20Inactive)%22%20%5B%20label%3D%22play()%22%20color%3D%22red%22%20%5D%0A%20%20%22Paused%20(TL%20Inactive)%22%20-%3E%20%22Paused%20(TL%20Active)%22%20%5B%20label%3D%22Active%22%20color%3D%22black%22%20%5D%0A%7D%0A">chart</a>.</td></td> - -<td><td colspan=2>On the implementation side, this sprint Yi (yigu@) added support for running scroll-linked animations on the compositor to free them from the <a href="https://codepen.io/yigu/full/ExjJVQr">busy main thread</a>, Majid <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2070673">landed</a> the initial patch IDL changes to support <a href="https://github.com/w3c/csswg-drafts/issues/4337">element-based scroll offset, and</a> Jordan (jortaylo@microsoft.com) added ScrollTimeline.phase which will be used specially to replace the fill mode.</td></td> - -<td><td colspan=2><img alt="image" src="https://lh3.googleusercontent.com/1W1LxJTG6s7Znk7NhC_evWlDBQcxcSC9rAnT3iVPhyMDdFbte5t95MFGv5mjeeYcDgGpmKI40RVm370kDHCKlCKOYfXxtfiiSE5a5umWNf18l88HNyH5x0YvDSXJbww0hb_Jz1Oe" height=258 width=281><img alt="image" src="https://lh4.googleusercontent.com/Xj2XRYqsx2AL-quX7e2OYg3JmhJzzvONhBsZEPSImL_3HnP42tmS1hUn96J1RW1vi8wpDu-IfqAend__rYuE6Ulo1yYKrH0wc5RixwQ8t2USAzj6A3I4iHeyaSDkS4VyX4LfgSMQ" height=259 width=282></td></td> - -<td><td colspan=2>Left: the animation becomes janky after adding artificial jank on the main thread.</td></td> - -<td><td colspan=2>Right: the animation is composited therefore it’s still smooth with artificial jank.</td></td> - -<td><td colspan=2>Finally after sprints of hard work on the rather complex problem, Olga landed the scroll snapshotting <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2005629">work</a> to make the timeline invalidation correct and avoid<a href="https://docs.google.com/presentation/d/12UNGCTJybiL5gEMAGY2f-05WxXARvNz4k-RS02qgNuU/edit#slide=id.g740960215a_1_0"> potential layout cycles</a>. This was a ship-blocker! \\ o /</td></td> - -<td><td colspan=2>Frame Throughput Metrics</td></td> - -<td><td colspan=2>Xida (xidachen@) made solid progress on refining high-level metrics to measure renderer performance this sprint.</td></td> - -<td><td colspan=2>Thread throughput unification</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/C-IASVz_2FBnKTJAeqH9H1PNUdfRq8RQ2QOr_pA0cYTFOcR7lH8-voMoVsXMMVHTsLHyHI32FUJgNHXNpqOS6cUbDJQPfbymI9nkTUBOFz3P7t9HUspopVAOLvUIGYGsHXm0bG_K" height=112 width=187></td></td> - -<td><td>Top: width animation runs on the main thread</td></td> - -<td><td>Bottom: transform animation runs on compositor</td></td> - -<td><td>When we have animations running on both main thread and compositor we used to report the one with worse throughput regardless. e.g. the transform animation’s throughput is ~98%; the width animation starts 3 seconds after and its throughput is ~10%. In the past we reported 10%. Now when we are not expecting to produce a main frame such as the first 3 seconds, we take the compositor throughput therefore the reported throughput is ~65%.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Tracking the last frame</td></td> - -<td><td colspan=2>It’s possible that after a BeginImpl\[Main\]Frame is reported, the tracker is scheduled to terminate. e.g. an impl-frame could have started right before a sequence stops such as the end of a touch scroll. We will completely lose track of it under such circumstances. With Xida’s <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2079134">work</a>, we can now track the last BeginImplFrame and soon the last BeginMainFrame. </td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | March 2020</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/march-2021---fixit-week-new-features-testing-interop-metrics-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/march-2021---fixit-week-new-features-testing-interop-metrics-and-more/index.md deleted file mode 100644 index d953102c434..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/march-2021---fixit-week-new-features-testing-interop-metrics-and-more/index.md +++ /dev/null @@ -1,440 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: march-2021---fixit-week-new-features-testing-interop-metrics-and-more -title: March 2021 - Fixit week, New features, Testing, Interop, Metrics and more! ---- - -<table> -<tr> - -<td>March 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: Updates</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>News and headlines</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/8Rx9baQSC1D5OKFFterOr8Ep4YoxqFThALN73pUPewvq4fUaFUVlOksg2JThWYNqD2QU0BRVezKD9fDNXj0MxRN_zt-N7G4vHYsyjkqd35ob51icSH-87sJV-20hBNTPOAPYrrD2w0Ggrg7eVUtIUmR1reIvSKYemlzjfdfzvl4nysCh" height=140 width=139><img alt="image" src="https://lh4.googleusercontent.com/M_WQs-eMjr2z7Vo1B5MnwO02b2XhJRNzBPsaLddW8yBxbwu7AFSBm-tTfR-T1MBMMsT7gy6SQX95J8YEB_IMV3TJobogfhmBZpmgZS19VQ4UwO1Kr2y0pS162qw9jLAiuMnRdNwqV-8OQfbaXlL5jaue5_GBlUhvfyox1n9X-FQUF3Xg" height=153 width=124></td></td> - -<td><td>The above pictures show:</td></td> - - <td><td>Una’s Chrome blog post: “<a - href="https://developer.chrome.com/blog/hardware-accelerated-animations/">Updates - in hardware-accelerated animation capabilities</a>”</td></td> - - <td><td><a - href="https://twitter.com/ChromiumDev/status/1366422289441566736">Tweet</a> - on Scroll-To...</td></td> - -<td><td>Bug status update</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/baJ0Vl-hujPKzdTypC9eeqvk7ifk30XYovJ4uKFZkJakYRVVlj6OKrwwwWKebHate9YPgSail2_yQQla7zP0lkNl0f9uAALZYQGJpDtD0C0iu6rKr6Dd7wsbnIFj8c1VzybSQThgKefFBNFXRcXStkEohFZvUeCdMipFfADVUw7bT97y" height=77 width=140><img alt="image" src="https://lh5.googleusercontent.com/0nTwbFbyafdWtsV8h2di3l5lOqebkNcmCG6OfwwQi6SLLEsSA3dJCt-l3D_KqAn6cUbawHVyx77DHwvlpuzr7MGfv6ZsSiUR41JUbYVS9R5VRzaetVQ3JatAn-jgUfRRzYk91bQYptKWiD6_CC62pzqT-oF2VEvhy4Nmnq3XuIRMQrpy" height=76 width=140></td></td> - -<td><td>Our team did an awesome work on bug fixing this sprint...and during perf too!</td></td> - -<td><td>This is likely due to our fixit week effort which is proudly introduced in the next chapter...</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Fixit Week!</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td><a href="http://go/interactions-fixit-2021q1">Overall stats</a></td></td> - -<td><td>Our team had a fixit week during Mar 1~5, and the team made tremendous progress!</td></td> - -<td><td>Bugs we closed: <a href="https://bugs.chromium.org/u/2341872843/hotlists/Interactions-FixIt-2021Q1?can=1">40</a> including:</td></td> - - <td><td>P1s fixed: 4</td></td> - - <td><td>P2s fixed: 11</td></td> - - <td><td>P3s fixed: 7</td></td> - - <td><td>Others (WAIs, dups): 18</td></td> - -<td><td>Bugs re-triaged: <a href="https://bugs.chromium.org/u/flackr@chromium.org/hotlists/Interactions-2021-Retriage?can=1">19</a> including:</td></td> - - <td><td>Fixed: 2</td></td> - - <td><td>Closed: 6</td></td> - - <td><td>Assigned to another team: 1</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>De-flake scroll snap tests</td></td> - -<td><td>kevers@ focused on deflaking scroll snap tests during fix it week. Here are some common causes of flakes:</td></td> - - <td><td>Files containing too many subtests triggering timeouts. We cannot - always accelerate the scroll timing. The tests have a 6s budget and can take - 3x longer than expected when machines are under load.</td></td> - - <td><td>Incorrectly detecting the end of an animation. Waits on a gesture or - key event resolve when queued and not when handled. This can result on the - scroll end being detected before it has even started! To address, we now - wait for scroll events.</td></td> - -<td><td>Outcome:</td></td> - - <td><td>Landed 7 CLs</td></td> - - <td><td>Removed 14 lines from test expectations.</td></td> - - <td><td>Fixed 10 test files</td></td> - - <td><td>Closed 8 bugs</td></td> - -<td><td>Fix pointer events flaky tests</td></td> - -<td><td>liviutinta@’s focused on pointer events tests marked in TestExpectations file:</td></td> - - <td><td>Using sendkeys instead of keyDown, keyUp</td></td> - - <td><td>Landed 1 <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2737916">CL</a> - that fixed 4 tests.</td></td> - - <td><td>Marked in TestExpectations:</td></td> - - <td><td>For <a href="http://crbug.com/893480">crbug.com/893480</a> the - remaining 8 tests in Test Expectations need implementation keyUp/keyDown - as it allows for multiple keys pressed at once</td></td> - - <td><td>For <a href="http://crbug.com/1140611">crbug.com/1140611</a> - there’s “Element click intercepted error” thrown from test driver (2 - tests)</td></td> - - <td><td>Few web tests flaky because pointermove coalescing was not taken - into account (1 WIP <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2745276">CL</a>, - 2 tests, 5 related issues)</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Fixing clusterfuzz crashes</td></td> - -<td><td>xidachen@ worked on fixing clusterfuzz crashes:</td></td> - - <td><td>They usually have a minimal test case, easy to diagnose</td></td> - - <td><td>These are crashes can happen in the real world</td></td> - - <td><td>Often times it is due to our coding missing edge cases</td></td> - -<td><td>Outcome: Landed 2 CLs and fixed 2 bugs. In additional to that, xidachen@ also closed a few touch-action related bugs.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Animations in display locked subtrees</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/gXn-G235ngNBZqnmVTdwJK5JsmZSu8eeCwhoRJs4TZQoAwU-F2PgGaOZb_uU8zV18Nifvs8SAWH96eny1NaJPWzhoAl3L2SjJ6kXcV9ZHr-OPGNsroy4-2v1UzenxwYZfrAQ0wBI9GGj2VxR-3oiab8F5vtaM0hd0Psp7ll7fWD0RcbW" height=239 width=283></td></td> - -<td><td>kevers@ is working on this performance optimization, which effectively “pause” CSS animations/transitions that are not rendered due to content-visibility, while direct queries must still produce correct results.</td></td> - -<td><td>The above demo shows that animation events stop firing while content is hidden, which is a direct consequence of not updating hidden animations due to the normal passage of time. Calculations requiring a fresh style update are correctly resolved on demand.</td></td> - -<td><td>Composite background-color animation</td></td> - -<td><td>xidachen@ fixed a crash which is due to missing repaint. He is also working on two known problems in order to restart finch experiment.</td></td> - -<td><td>Scroll to element</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/py8m0A7cqlby60QF-ayhnnAx0D5qNgt5tXjcZch6XaSmea-TKeG4tEscN66ShBCpdiacNSN-mK93HZ0kJEvC4EWD-gPBSd49UjBWh4QkwPkYzK6pQcGXtCZHzNK5ZlvtSGeismWyBhfb4Iy3CDNG3IEk0TFVyqBEGOv6ApprIstxIxp_" height=159 width=283></td></td> - -<td><td>flackr@ developed a <a href="https://chrome.google.com/webstore/detail/scroll-to/hjaaolhckkhdkamciipnogbbiafgbcil">scroll-to extension</a></td></td> - - <td><td><a href="https://github.com/flackr/scroll-to-extension">Source</a> - code is available</td></td> - - <td><td>Scrolls to selected element</td></td> - - <td><td>Rejects <a - href="https://github.com/WICG/scroll-to-text-fragment/blob/main/EXTENSIONS.md#css-selector-restrictions">restricted - CSS selectors</a></td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Google Meet FPS optimization</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/lSNmrAN5LzgMhOS2CppDDmbPza5nWwaPmqI0fgEBEblh7q2FbNV5iij-Kt_UkKQp2qOjt3xqEl5NH_rKGePmxJdxYC7jLFxxRZAqfZ2zmK6QxLjhYyHnpQ8QMSIE__2Ywnn1emJB_RXDBZeEHdw82iS2SCogBXfgZH2GR-qWcE9Ep2Qq" height=405 width=283></td></td> - -<td><td>zmo@ plumbed minimum tick interval of animations, which requires</td></td> - - <td><td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2716656">Calculate - minimum tick interval</a></td></td> - - <td><td><a - href="https://chromium-review.googlesource.com/c/chromium/src/+/2730045">Used - in tick rate heuristic</a></td></td> - -<td><td>After the above change, flackr@ found that meet still wasn’t showing 60fps. More investigation shows that meet had incorrect animation. Specifically 0.6s 3 keyframe animation with steps(18) should be 30fps, but 18 animation-timing-function steps is applied between each pair of keyframes. flackr@ is currently working with meet team to further optimize this.</td></td> - -<td><td>Penetrating context menu image selection</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/3WSJTjHaw94sUraj0T8JhdTWDJwtGtJpEijrluAiFSX1fsZCK4RwhgbVYnTxO5sxJu4oRogVdOo-Q9JDnQoM9Zt_taRYYXV2YBK-WUUcDIDiSbmszSq5EY3AGY4r2-zHhqx5VbT3Z8YwinxWir0Rofi5oDy1QUmsdKYe37T2EsI2yEY5" height=215 width=283></td></td> - -<td><td>The feature is implemented by benwgold@ where flackr@ is an active reviewer. Specifically, this feature allows right click / long press to find images below targeted element.</td></td> - -<td><td>In this <a href="https://output.jsbin.com/rucoyak">demo</a>, an image label element completely covers the image. Without penetrating image selection, one could not save the image without inspecting the page.</td></td> - -<td><td>Disable double tap to zoom</td></td> - -<td><td>liviutinta@ landed <a href="https://chromium-review.googlesource.com/q/bug:1108987">CLs</a> disabling DTZ for meta viewport tags such as:</td></td> - - <td><td><meta name=”viewport” content=”device-width”></td></td> - - <td><td><meta name=”viewport” content=”initial-scale=1”> , for any - initial-scale >=1 we’ll disable DTZ</td></td> - - <td><td><meta name=”viewport” content=”minimum-scale=1”>, - minimum-scale >=1 implies initial-scale >= 1</td></td> - - <td><td>Combinations of the above</td></td> - -<td><td>The <a href="https://groups.google.com/a/chromium.org/g/blink-dev/c/dXztlK096rs/m/6DKc6nhcCQAJ">I2S</a> API owners approved, and we have started finch experiment for 50% canary.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Testing</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Move virtual scroll-snap tests</td></td> - -<td><td>The problem with virtual/threaded is that it doesn’t guarantee that scroll snap tests run on the compositor. Thus kevers@ moved the tests to threaded-prefer-compositing, which ensures that the composited path is being used. This change exposed that we had limited testing of scroll snap with composited scrolling and temporarily introduced 7 new entries in the TestExpectations file. These failures have now been addressed.</td></td> - -<td><td>Automate WPT test using testdriver action API</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/y5VfiIiUaDOm-G9ldk2gNytVwyx9DgTmvVSZZKzqvdkUBQ5JEV5z40t9YfledkhNAgqYpbskH9vTP5VCnryyOJMIRzz0ak45JZmMW29ZedQQGpVYzR7cg8NHxYQfHtJM3J6-C4o9ePXJBXFBszOwpeUxUfvoJh6mH49V_uQwhdBM5Jpe" height=185 width=283></td></td> - -<td><td>lanwei@ kept working on automate WPT test and making good progress.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Stability fixes</td></td> - -<td><td>kevers@ fixed a problem when running user code (Javascript) that can result in the destruction of an execution context. The solution is to double check if the context is used downstream of script execution.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter VI: Interop fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Sticky interop investigation</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/xCplj7tBIokIzfY3bN1pO4H07CEWAZq9qG8C9p8DmlfYfor-6CGO4h9OdyDZsR03gCf5esw4S1xIsIvYiyLRBcxvS1C7k6zIDFvS_111zX_QJjBHotjN4mBbY_Gj7VMV51LgF9b9OkIw1SU2Tld6sb6IpufwOub1V2YeJK-ShNRd0XPB" height=167 width=283></td></td> - -<td><td>flackr@ created <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1185163">meta tracking bug</a> for this. During this sprint, <a href="https://bugs.chromium.org/p/chromium/issues/list?q=commentby%3Aflackr%40chromium.org%20sticky%20closed%3E2021-2-22%20closed%3C2021-3-12&can=1">3 issues</a> were closed. Moreover, a <a href="https://wpt.fyi/results/css/css-position/sticky/position-sticky-scrollIntoView.html?label=experimental&label=master&aligned">WPT test</a> has been landed to track new spec scrollIntoView behavior.</td></td> - -<td><td>Fixed falsely overconstrained stick positioning</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/xtsXFqA5IqyV2xz6JWUDk25Ee5dkse6mUKh_5FTcPYpISbkPWErpJR5k3fMnUMI9qnyzgLJSziuxiFSOPImhoGdqX-fZ4NWry2y1Jivg6v_KZ5E75YtqmMTl-vw8OVl7xAa8VJmY7dVCm6VwrsrmLkbG3vK_A-VH1453sQTMChlYha0U" height=137 width=137><img alt="image" src="https://lh4.googleusercontent.com/BG8InXEt7-3mnsMMdOjt8vPJ_Ff8aexfkJ2xiBSV3JryUb501rzf6JUkU2ELO8H0bUHzSU5zYg_gS8FeLzm0DQsjWUr_WlMZKvOJtfhK4O3KmArm4vROemwz6axHO3l66GcIXtbzKtAA_WHOJZYEPPvUQE-BcoIlh7yun3UZUoXyrMbj" height=136 width=136></td></td> - -<td><td>flackr@ fixed a stick position <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=841432">bug</a>. In the above demo:</td></td> - - <td><td>The left one is the wrong behavior where the bottom constraint is - ignored.</td></td> - - <td><td>The right one shows the correct behavior. Both bottom and top - constraints are used creating reveal and collapse effect.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Overscroll-behavior propagation</td></td> - -<td><td>xidachen@ made some progress towards fixing this <a href="http://crbug.com/954423">bug</a>, which includes</td></td> - - <td><td>Found ~15 google internal sites that might break by the incoming - fix</td></td> - - <td><td>Started this <a - href="https://docs.google.com/document/d/1PGBW3PDWTenS8i6-k6Xsv1_MuKxqEfX8o1jVGmxxnFk/edit#">doc</a>, - which provided guidance on how to change their sites to avoid - breakage.</td></td> - - <td><td>All google internal sites listed in the doc have made - changes.</td></td> - - <td><td>Unfortunately the percentage of sites that might break is not going - down (<a - href="https://uma.googleplex.com/p/chrome/timeline_v2/?sid=29901cc34c7b4b624f5a759bda0b5a34">Beta</a>: - ~2.2%, <a - href="https://uma.googleplex.com/p/chrome/timeline_v2/?sid=706cc2310b84fa2bdb3e87b52b1c052b">Stable</a>: - ~0.5% of page loads)</td></td> - -<td><td>Scroll snap behavior with scrollbar arrow keys</td></td> - -<td><td>Resolved the scroll snap behavior for interactions with the scrollbar arrow keys during the last sprint cycle for main thread scrolling. Fixed for composited scrolling this sprint.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/VJhePxtBeo6Irdt8t9FxdTl8hvkvHcAAGVyxvmtUeehNqlThCATmCB3WWuLXGGfOP-7rg-4uihVZN1VoosN0Tpbq8Iekx1J55WTrQqZp8J-TeZxDq0U6-Iqo2PcM8zT-EudBCQpYRkjXdqlv78FjI_GilXNHHyy1Iu2yen5ZOhsgoywR" height=97 width=283></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter VII: Metrics</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Finch study: Composite relative keyframes</td></td> - -<td><td>kevers@ launched this finch study and collected some meaningful results.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/uyULOys9B0l5Qkk1G8ZDUoqr-ps8pQ1ZpPMkJO4T0S9ipY6aLjCX6IMcuCfceaxBS98cfu3o-Q6OBUUZ0A_owKwozS_ctf0gbXEtUoi3Xru7ghDxCOE4uTYu26aFmclzqbnoh7aLZNAjc-q-kObkIGNXqhTKzRyUyVA1WctLKb8ZPQB0" height=123 width=283></td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/xoghGSmjwTGotF0VxXGa_XGkMHaKNQvIOvSx4CRqVpN900oCWoCYZwmMxbaz7IptN0gLl00CrW0XRgwSbhuOB3PZEjC4n1eDX3OqRybkLOhor4IUKXrFVqsTTyJNjMJmtfPHjIlYGAEtJdgIdluiKurKJJV6DahQdzEaNNQdvAwR1rgl" height=117 width=283></td></td> - -<td><td>Finch study: <a href="https://uma.googleplex.com/p/chrome/variations?sid=950bc8883d9b9c8ce6469b5592a5e81a">Scroll prediction</a></td></td> - -<td><td>flackr@ is launching this finch study on behave of a Microsoft engineer.</td></td> - -<td><td>VisualJitter</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/mT74G-gB6SrpkOE9Psf3G700HUcy0Shav9Q-Z1dFcxJ8XTthGh8iB4p1MWRrcM3KVVG6zm_mEKBR4vMPej_vqBcnp_Qb4RDw9TkRYxLrdNi2yFbva-qai4RJWpwLc9KqVwjee-7UBB06Z7VmNYVo01pASlLvSHqEOKkXkW6feRDIAbtD" height=113 width=283></td></td> - -<td><td>AverageLagPresentation</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/lcCu72bAUBMq3KtAO5_46zwl8GDtC5R9RjnOypXBrRzH-c5iQWzrSbnCnBC9EL-rM4JT02kNe_cCzWOlAHTPiJ2CIM4sbq0XTCzwanEt5PjQjXTndj89sdexYXYLd1I4-EwXg6UVbzlLyD3CO-ksuVCDLhfLvCU7QSodgt4ZSm4O18BV" height=113 width=283></td></td> - -<td><td>Legend (f=# frames): -5ms 0.375f 0.5f 0.625f 1.217ms 3.3ms 5.383ms</td></td> - -<td><td>The data of “VisualJitter” suggests that more prediction means more jitter. The data of “AverageLagPresentation” suggests more prediction increases lag.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Smoothness Metric</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/MKJsf1GYBhT0doAMEpwkenRs76RjwpmXg7qR50gqFH7ntVCI6OUJ3qLoVl_oLfpZ-kl9nN3gMprxubQ4GWQHSvfg_wCAAZ-l8Vfb_Np9HcdrEXuKa-WhcDmyxEy1Gm71f-gGyIvZV6xOFfB1jSrHXeHRxQX8fhlpGN6miqwvOrAqw2fc" height=143 width=283></td></td> - -<td><td>lanwei@ explored in the smoothness metric field and did some data analysis.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter VIII: à la carte</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>PointerEvent spec reviews</td></td> - -<td><td>mustaq@ has almost done reviewing two significant changes from the external spec editor:</td></td> - - <td><td><a - href="https://github.com/w3c/pointerevents/pull/349">Reword/expand - touch-action definition</a></td></td> - - <td><td>Added direct suggestions to clarify that “touch-action: - manipulation” excludes double-tap zoom.</td></td> - - <td><td><a href="https://github.com/w3c/pointerevents/pull/350">Major - refactoring: refer to “direct manipulation” rather than - “touch”</a></td></td> - - <td><td>A long and tricky edit to officially include (some) pen pointers - in touch-action.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | March 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/may-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/may-2019/index.md deleted file mode 100644 index bbd6cc932b8..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/may-2019/index.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: may-2019 -title: May 2019 ---- - -<table> -<tr> - -<td>May 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> -<td><img alt="image" src="https://lh5.googleusercontent.com/y55oEKmeWfBAk_jdj6Q_izzXpBOZT6wuau4DNg6VPlbK-sThHRNyJx-OLWmLi11KVTyFORLWHzUEFaMdOEizHaMLLCyEd60zW6RyGpQP56AVWVuvWjkRQJk6_yvWAC_LMfmW84mr" height=308 width=532></td> - -<td>The slight decrease in 'interface' from Chrome 75 to 76 is due to newly added tests</td> - -<td>Web Animations, road to shipping</td> - -<td>Our investment in interop work for Web Animations continues to produce good results, largely thanks to hard work by Kevin (kevers@). Over the last two Chrome versions our pass rate for the <a href="https://github.com/web-platform-tests/wpt/tree/master/web-animations">Web Platform Tests</a> has increased by 45% (absolute) for the timing-model tests and a massive 70% (absolute) for the interface tests! Improvements like these allow us to continue to ship more of Web Animations - recently we shipped <a href="https://groups.google.com/a/chromium.org/d/msg/blink-dev/lTYK1HT47Qk/hmwmGm1ZBAAJ">Animation.updatePlaybackRate</a> and <a href="https://groups.google.com/a/chromium.org/d/msg/blink-dev/Gstf0GA7cbg/711ymCKKAAAJ">Animation.pending</a>.</td> - -<td><table></td> -<td><tr></td> - -<td><td>Code Health</td></td> - -<td><td>Rob (flackr@) has been focused on improving the composited animations code in the new <a href="http://crbug.com/836884">post-BGPT world</a>. This sprint he landed a series of patches (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1611762">1</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1609672">2</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1610304">3</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1461341">4</a>) to eliminate animation specific ElementId tracking in LayerTree. This simplification makes the architecture easier to understand, improves CPU usage and reduces memory usage - a triple win!</td></td> - -<td><td>Scroll Snap</td></td> - -<td><td>Scroll Snap is continuing to gain traction, with AirBnB being the latest partner to <a href="http://crbug.com/920482#c9">start using the feature</a> and Firefox <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1312165#c6">continuing to implement</a> the new spec. On our side we have shifted into supporting the product: Majid (majidvp@) has been busy triaging bugs, addressing partner requests, and polishing the code.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><a href="https://uma.googleplex.com/p/chrome/histograms?endDate=20190515&dayCount=7&histograms=Blink.Animation.CompositedAnimationFailureReason&fixupData=true&showMax=true&filters=isofficial%2CEQ%2CTrue&implicitFilters=isofficial"><img alt="image" src="https://lh6.googleusercontent.com/IUKoi9dwyyJhEUdaoyDeGdtFoKLI_WO1j-Bkzk1s7RxSaP9ZZYTk6ugL1KHylCTX2IE5K6Vc8zvKUpKocBFDwF48OQJatYnjlXsJSSukICRCRvLKb6q2vVaHw_SM40RBFyXQDBtm" height=113.00000000000003 width=283></a></td></td> - -<td><td>Understanding performance better</td></td> - -<td><td>Stephen (smcgruer@) landed a new <a href="https://uma.googleplex.com/p/chrome/histograms/?endDate=20190519&dayCount=7&histograms=Blink.Animation.CompositedAnimationFailureReason&fixupData=true&showMax=true&filters=isofficial%2CEQ%2CTrue&implicitFilters=isofficial">UMA metric</a> this sprint to track why animations fail to run on the fast path. This allows the team to better understand where effort is needed to speed up existing animations on the web - vital for smoother user experiences.</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/z-ajU372TxKnGgMOwOSQa30PmFdlpv-ZAWn_gZBkcvv91oDDyy9-Bl3W3t3Wz76F7OXc-VG3wxCP9PjyxClhdVKJ_fju9h25ymlvF0X3iSQxTQNEvzGHRYOqClEi9F-tWHW2zBrp" height=237 width=203></td></td> - -<td><td>Smoothly animating Paint Worklets</td></td> - -<td><td>One of the key goals of the <a href="https://docs.google.com/document/d/1USTH2Vd4D2tALsvZvy4B2aWotKWjkCYP5m0g7b90RAU/edit?ts=5bb772e1#heading=h.2zu1g67jbavu">Off-Thread PaintWorklet</a> project is to enable smoothly animating Paint Worklets even when the main thread is busy. Xida (xidachen@) has been working on a <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1601334">prototype</a> of the Animation integration and this sprint was able to show smoothly animating, raster inducing (!) Paint Worklets even as the main thread janked.</td></td> - -<td></tr></td> -<td></table></td> - -<td><img alt="image" src="https://lh6.googleusercontent.com/sRxCDjOAzL3r8SXmttXLNpN6Qv2eHz7ELPwsaSWGcNBfhPr-lYE0vfmMGuUSQh2O6l4vCBAPSKukS8vr5ErGy8AdZLMFNnBmBDhDUHyAXNQCa6ct9JHPukEztHaoy-SOjHR4uFRU" height=389 width=570></td> - -<td>Animation Worklet - Pointer Events proof of concept</td> - -<td>This sprint, Majid (majidvp@) created <a href="https://majido.github.io/houdini-samples/animation-worklet/touch-input/drag.html">a prototype demo</a> showing the power of off-thread input events combined with Animation Worklet. The ability to produce rich interactive effects which can be performance isolated from the main thread is very exciting, and we are continuing to invest in producing a spec for <a href="https://discourse.wicg.io/t/proposal-exposing-input-events-to-worker-threads">event delegation to workers/worklets</a>.</td> - -<td>In other AnimationWorklet news, this sprint Jordan (jortaylo@microsoft.com) began <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1568315">landing support</a> to expose the full <a href="https://drafts.csswg.org/web-animations-1/#the-animationeffect-interface">AnimationEffect</a> interface inside the worklet. This is exciting both in terms of giving developers more power as well as welcoming a new contributor to the team!</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | May 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/may-2021---new-features-testing-stability-fixes-interop-fixes-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/may-2021---new-features-testing-stability-fixes-interop-fixes-and-more/index.md deleted file mode 100644 index 61173c84c30..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/may-2021---new-features-testing-stability-fixes-interop-fixes-and-more/index.md +++ /dev/null @@ -1,220 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: may-2021---new-features-testing-stability-fixes-interop-fixes-and-more -title: May 2021 - New features, Testing, Stability fixes, Interop fixes and more! ---- - -<table> -<tr> - -<td>May 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll Timeline Documentation</td></td> - -<td><td>kevers@ started a <a href="https://docs.google.com/document/d/1AyhFFWKuevKfKQU9uRKMMVMbCKdAwuEPmSBBghbhLFE/edit">doc</a> for I2S and devrel. The doc provides skeleton examples that highlights the use cases of scroll timelines and demonstrate the API.</td></td> - - <td><td>Parallax scrolling (from polyfill demo)</td></td> - - <td><td>Animating elements as they transition into or out of the viewport - (from CSSWG issue)</td></td> - - <td><td>Auto-resizing header (bram.us)</td></td> - - <td><td>Scrollable picture story, which makes use of paint - worklets.</td></td> - -<td><td>Populating Touch click/contextmenu pointer id and pointer type</td></td> - -<td><td>liviutinta@: click/contextmenu event from touch is triggered from GestureManager and there was no way to map a GestureEvents sequence to the corresponding PointerEvents sequence in order to obtain the pointerId associated to the PointerEvents sequence. The solution was to populate the unique touch event id of the first gesture in the GestureEvents sequence as the primary unique touch event id for all the GestureEvents in the sequence. This primary unique touch event id is then mapped to the unique touch event id of the pointerdown pointer event. When handling pointerdown, PointerEventManager would notify GestureManager about pointerdown’s unique touch event id and its pointer id, and in turn GestureManager would keep track of the association until the corresponding GestureEvent (for click or contextmenu) would be handled in order to populate the pointerId of the triggered click/contextmenu event.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Testing</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll-snap: Deflake tests</td></td> - -<td><td>kevers@ deflakes a set of scroll-snap tests:</td></td> - - <td><td>touch-scrolling-on-root-scrollbar-thumb: The problem is scroll - gesture before ready and assert right after gesture. The solution is to use - waitForCompositorCommit and scroll promise.</td></td> - - <td><td>scrollend-event-fired-to-\*: The problems with these tests are - scroll gesture before ready, no cleanup and logic errors in listeners. The - fix is to use waitForCompositorCommit, add cleanup and use scroll - promise.</td></td> - - <td><td>fractional-scroll-height-chaining: The problem here is scroll - gesture before ready, non-deterministic mouse position and rAF based wait. - The solution is to use waitForCompositorCommit, mouseClickOn and - waitForScrollEnd.</td></td> - - <td><td>mousewheel-scroll: The problem is non-deterministic mouse position - and rAF based wait. The solution is to use mouseMove and - waitForScrollEnd.</td></td> - -<td><td>Fix scroll-unification tests</td></td> - -<td><td>kevers@ also fixes some tests with scroll-unification enabled.</td></td> - - <td><td>scrollbar-drag-thumb-with-large-content: the problem is scroll - gesture before ready, and the solution is to use - waitForCompositorCommit.</td></td> - - <td><td>scrollbar-added-during-drag: The problem is scroll gesture before - ready and single rAF before asserts. The solution is to use - waitForCompositorCommit and scroll promise.</td></td> - -<td><td>Fix single-thread mode with scroll-unification</td></td> - -<td><td>skobes@ fixed scheduling in single-thread mode, which is the default mode for web tests.</td></td> - - <td><td>SetNeedsAnimationInput wasn't actually scheduling the animation, - which caused tests with scroll gestures and scroll animations to - hang</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter III: Stability fixes</td></td> - -<td><td><table></td></td> -<td><td><tr></td></td> - -<td><td><td>Fix numeric overflow in CompositorKeyframeModel</td></td></td> - -<td><td><td>kevers@ fixes a numeric overflow problem. The root cause is that AnimationTimeDelta is backed by a double whereas TimeDelta backed by 64-bit signed int. Using unsafe conversion from AnimationTimeDelta to TimeDelta, which can result in a numeric overflow.</td></td></td> - -<td><td><td>The solution is to Update CheckCanStartAnimationOnCompositor to reject compositing an animation if currentTime is too large. Advancing current time by a few hundred years is just fine though.</td></td></td> - -<td><td><td>SVG smil animation in throughput metrics</td></td></td> - -<td><td><td><img alt="image" src="https://lh6.googleusercontent.com/iZk5QFsOzBhO9kf5qQwxRDo_4OgpecDuod7BwMzWZQ5pwFiu9z9n1ef-O8W-7WhKOeHE2iT6tjGsidtKQ3XZ68D4TnTWojdQBZgIijpbIWMrQLuLninU8DQjaL7aoeDifRekLVeHgQ" height=158 width=276></td></td></td> - -<td><td><td>Before</td></td></td> - -<td><td><td><img alt="image" src="https://lh4.googleusercontent.com/gMEwHQQ97x0Jlsqwi66w_eF7AeU0yUjaSZrXPwrdZsYVYOdZ7nx2-98l2WxoWgAr1hJu5B4DCcz8-c7X2-kRJ7caeUbe1-GYGtJ0JTfAC-xOZOJMwskGygBK3VXSVV9kntF-O8lkSw" height=156 width=277></td></td></td> - -<td><td><td>After</td></td></td> - -<td><td><td>xidachen@ <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2863204">fixed</a> an issue where SVG smil animation is not counted as main thread animation in the throughput metrics.</td></td></td> - -<td><td><td>The above demo shows that before the fix, there is no sample detected in Graphics.Smoothness.PercentDroppedFrames.MainThreadAnimations, while it is detected after the fix.</td></td></td> - -<td><td></tr></td></td> -<td><td></table></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Interop fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>flackr@ <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2892623">fixed</a> the metrics for counting overscroll-behavior potential breakage.</td></td> - - <td><td>Before: we will hit a UMA recording whenever the overscroll-behavior - property is different comparing the html and body element.</td></td> - - <td><td>After: we’d hit a UMA recording only if the body is the viewport - defining element, and that the overscroll-behavior property is different - comparing the html and body element.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Bug Updates</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/MHKcz_eBTvaoEMvqtpGDxweELZwCGAEm7xdV4D89dz-1T_asGIKvFg2CL6O7ILhfZ_g6I4KFxpy-nes3cVhiFfAKGgxiQNsPF6lXQ8NOAGO9JjUrGSnuKigT25helY0xJ-PJSA3S-g" height=150 width=273> <img alt="image" src="https://lh6.googleusercontent.com/I7aNfDvFvhYarIPRGEYMVMSkFFNB8yPVjHStk4q9AeYvyrh6TolUXxSAAFZPsYrqHEtwBNvMRwk7a_sbFpg8ky_gGcaUn8jKxymnneXvxmi5UGPZCxSBh_ealFjDY-73bE5RXlb6mA" height=150 width=270></td></td> - -<td><td>Our team closed fewer bugs this sprint, but we did get a <a href="https://youtu.be/m0JrspsaVDk?t=1779">chance</a> to <a href="https://youtu.be/VrEP7SPfQVM?list=PL9ioqAuyl6ULbse3njxmvJgJArp_-pKxY&t=3208">have</a> a <a href="https://youtu.be/VrEP7SPfQVM?list=PL9ioqAuyl6ULbse3njxmvJgJArp_-pKxY&t=3370">bunch</a> of <a href="https://youtu.be/m0JrspsaVDk?t=78">great</a> <a href="https://youtu.be/m0JrspsaVDk?t=201">conversations</a> at Blinkon... The rate of incoming bugs was relatively consistent.</td></td> - - <td><td>Xida Chen <a - href="https://youtu.be/VrEP7SPfQVM?list=PL9ioqAuyl6ULbse3njxmvJgJArp_-pKxY&t=3208">Composite - background-color animation</a></td></td> - - <td><td>Jordan Taylor: <a - href="https://youtu.be/VrEP7SPfQVM?list=PL9ioqAuyl6ULbse3njxmvJgJArp_-pKxY&t=3370">Scroll - Timelines</a></td></td> - - <td><td>Liviu Tinta: <a href="https://youtu.be/m0JrspsaVDk?t=78">Disable - Double Tap to Zoom</a></td></td> - - <td><td>Rob Flack: <a href="https://youtu.be/m0JrspsaVDk?t=201">Scroll To - \*</a></td></td> - - <td><td>Liviu Tinta: <a - href="https://youtu.be/m0JrspsaVDk?t=1779">click/auxclick/contextmentu as - PointerEvents</a></td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | May 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/nov-dec-2019---blinkon-scrollsnap-lottie-hittesting-virtualscroller-websharedlibrary-wpt-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/nov-dec-2019---blinkon-scrollsnap-lottie-hittesting-virtualscroller-websharedlibrary-wpt-and-more/index.md deleted file mode 100644 index 6988127edfd..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/nov-dec-2019---blinkon-scrollsnap-lottie-hittesting-virtualscroller-websharedlibrary-wpt-and-more/index.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: nov-dec-2019---blinkon-scrollsnap-lottie-hittesting-virtualscroller-websharedlibrary-wpt-and-more -title: Nov & Dec 2019 ---- - -<table> -<tr> - -<td>Nov & Dec 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh4.googleusercontent.com/DWJAD7EpLKH2Ac19IePi2JmkPHgV1fsYia0LGCZ3mxpEGU6fJCY2k-1XInFTZj0Whh032Fdw-dIoCDEV0EDs45kwIWlsc2jsfZwt8LXPrRfFMfQZMs_oN6pw5TmeAfou7y53qGgS" height=253 width=270><img alt="image" src="https://lh6.googleusercontent.com/vK6GwgfvzXmjGedJa8KQ6pEW_UmVi7hYNjsk5h1ndge7kIp_oUwZhktXsLxjAtfGL2bpSWdhzSvQBeOgc6vs7Z92V0GqpEdF8zsaSZzVWaY8mumxS9Ldh48MgP_iRhMnHkCiBVAv" height=255 width=312></td> - -<td>Left: the snapped element (white cat) is not preserved after layout changes.</td> - -<td>Right: the resizing triggers re-snap to preserve the snapped element.</td> - -<td>The Pursuit of Snappyness</td> - -<td>Kaan(alsan@), our fantastic intern, made the web more appealing with the “snap after relayout” <a href="https://docs.google.com/presentation/d/1WUa6nFfkzXm2O1V70hr49vPFP4TOAbUh2q8fppkybJs/edit?usp=sharing">project</a>. Previously content or layout changes (e.g. adding, moving, deleting, resizing) did not pay attention to the content’s snap setting. With Kaan’s <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=866127">changes</a> landing in Chrome 81, scroll positions automatically update to keep snapped objects in the correct position. Galleries of kittens never looked so good!</td> - -<td>Another cool use case unlocked by this work is the “Scroll By Clicking” effect shown below:</td> - -<td><img alt="image" src="https://lh6.googleusercontent.com/fRyKl_faF-Bgdceo3OYErRenGuZzKBBs2n2xMKss4-7vRnDP5wvm7Gae0DmktSqdbx5fGwUT_j-ltLPIBeFtDu2NqsN4qr4Ns8p6QI0bhzHND0tFkR7n91LC-Al27tl4J-W96en7" height=233 width=297><img alt="image" src="https://lh3.googleusercontent.com/1nPkrBOk1Dm9i5mkPLt_jEk6uTF7Jhuo_7qKj1cRWZe8xpc9IPTmN8bXuzhSzGUubGyV3QhHTM-UY6-71fRyZnc_MY63zZjkwEdmhX72tBlB1eP6B1rC168XLrdwDA0cuhOxdMm8" height=237 width=280></td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/PZ4-_ZrbNzstAkLHnjWZPkwXGl4b0FZthhuQ8dgR0DVzOdfmXxez2SF3m4GLNN1S_Q2Latry8UZouikJFv3ZW9PUbJQXWjdK0TlbWyNJ3bfC3RvnocOZx3GffHgz44fjh43Esxyj" height=72 width=280></td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/S-nAodiRsv_xyxIngFbN86HJR-7JaCZdX7wzG1olre_TUBLKjKk5np7aJYfrwIltVXB7H8LcLVw1Z7rWEwuzSpKNeHX7C1yHoUqIXNe0MoUVnxmCllgfVHLiAnASux1dNQx89iRp" height=83 width=280></td></td> - -<td><td>Lottie Demo - now more robust</td></td> - -<td><td>Rob’s lottie demo exposed a number of PaintWorklet bugs, such as flashing at the end of the animation, incorrect background color, and flaws in high-dpi rendering (top gif). This month Rob (flackr@) and Xida(xidachen@) fixed some issues (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1841530">high-dpi</a>, <a href="https://github.com/flackr/lottie-web/commit/8cea6ff27b03e6125c00e85d6ff15abff15c6e75">clipping</a>, <a href="https://github.com/flackr/lottie-web/commit/2aee64a69fb74c3c26f7435db9e0a804608e77ae">flashing</a>) in both the demo and the implementation to make it more appealing (bottom gif)!</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/SLQW5VgfbkGLfzMohnaHu0O_51WGPoMDlpIoX-Kzlw0e3kxairHQgkfLkwVtk0w7j6KW9ifGGc3WptW8b328XDsFwou9bWwOKMzbjbetT3OR5ofIG7MGjiQUunL2xPJmuHEQ0ZPD" height=176 width=278></td></td> - -<td><td>Multi-Process Hit Testing Complete</td></td> - -<td><td>Yi (yigu@) drove the viz hit testing v2 project to completion this month. It is now fully launched on all platforms! The new event targeting correctly targets events up to 6 times faster for site isolated configurations on <a href="https://docs.google.com/document/d/1AE02TKBg7NG63SiUbU-EiqlHgqsZY1tb3-Z4L0AZCSk/edit">Windows</a> thanks to the 32% more synchronous event targeting. </td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/NngtlrupseOCRsIOOr-Nn-UZbMX-MIdSiTk_Agpt7cFv-Qd5ieUwlIJXuZ482e_SOeWPip3uFwx6J-WIJ0XStDp4IQXxUhLZ9O6D59k2Q0oFphXTkbGV8AH5-TbAw0Xy2IHnV6jN" height=281 width=280></td></td> - -<td><td>Virtual Scroller</td></td> - -<td><td>Rob made solid progress on the exploration for the new web platform feature - virtual scroller control. He moved chromium virtual-scroller to github <a href="https://github.com/flackr/virtual-scroller">library</a>, added display: none fallback when rendersubtree is not supported and created a nice <a href="https://flackr.github.io/virtual-scroller/demo/">demo</a> with synthetic content and <a href="https://flackr.github.io/virtual-scroller/demo/?test=true">test</a> use cases.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/etS54zUr6juIFudSJaZ_4J0Tlp6Y9qxps7IENSmYxBBNx-5vCFMh9UugkPd9OZFpbvVMNM3seoFxoXe-JUoXQDpO_xfKT-Mu9Cw6FbNgCcBeFm9cpS4w2wqMme6pvg89s92sxvrJ" height=299 width=278></td></td> - -<td><td>Port interpolation test to WPT</td></td> - -<td><td>Our test suite for interpolated values does not work in other browsers. Since we deeply care about interop issues, we have ported as many tests as possible (<a href="https://docs.google.com/spreadsheets/d/1EtUV2IycJTgQSrtxfH0uQ8aUUbhz41-zhYj0tdCrT6A/edit#gid=0">121</a> to be exact!) to wpt. This work helped us to identify 17 new interop bugs in Chrome and Firefox. Thanks to Stephen (smcgruer@), Xida and Hao (haozhes@) for their effort to make this happen! </td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Animations team at BlinkOn 11</td></td> - -<td><td colspan=2>The animations team presented 3 breakout sessions and 4 lighting talks at BlinkOn 11. See below for details.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/mBS6Z_-mXCbDu_mhXaB-ZVvoi3yODetHPxtuNJmgXZrhohvNHMXdqK7rqAUNk9k3cUH0j7dQ7cW_IBrcwhE-A--NIIExJHzFEs0dlqrbCyW3OzUAu_Wk4o0tjb6_qKWURl8kQOvj" height=145 width=280></td></td> - -<td><td>Web Shared Library</td></td> - -<td><td>Web Shared Libraries attempts to improve website loading by sharing cache across sites. Rob’s presentation (<a href="https://docs.google.com/presentation/d/1CTC_BLpBqLf7B82b1ytIm0l84SjK45bk7UaCyRpyu5A/edit#slide=id.p">slides</a>, <a href="https://www.youtube.com/watch?v=cBY3ZcHifXw&list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&index=23&t=0s">video</a>) at BlinkOn, kicked off a lot of constructive feedback. Gene (girard@) and Rob wrote up a <a href="https://docs.google.com/document/d/1lQykm9HgzkPlaKXwpQ9vNc3m2Eq2hF4TY-Vup5wg4qg/edit#heading=h.83t0eq3angjs">discussion pape</a>r capturing the opportunities and challenges involved, along with techniques to address the various concerns and metrics to evaluate impact.</td></td> - -<td><td> <img alt="image" src="https://lh6.googleusercontent.com/1CFPALcatns9GWaoO89Tu2dvl1FraGY1RckXruqf3CaHW8AdyQUqsl47f7I3qWY3h2skZLRZxP2-HE0fiUUrlAgxt34acepBhzpW_yHvstWrlWR1QVChkfp5HuXUUr3PrmAKeKcU" height=200 width=262></td></td> - -<td><td>Scroll-linked Animation</td></td> - -<td><td>Yi and Majid (majidvp@) presented (<a href="https://docs.google.com/presentation/d/12UNGCTJybiL5gEMAGY2f-05WxXARvNz4k-RS02qgNuU/edit?usp=sharing">slides</a>, <a href="https://www.youtube.com/watch?v=nolDnHb_Sjo&list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&index=4">video</a>) the current design for Scroll-linked Animation at BlinkOn. The updated design incorporates feedback on our origin trial from the AMP team. There was a F2F sync between Microsoft and Google to <a href="https://docs.google.com/spreadsheets/d/1tGJeicFqgRXK8MMIqscdwEiIPQN--1aQJ5EwQZ2nXzE/edit?usp=sharing">coordinate</a> future work and find solutions for outstanding spec <a href="https://github.com/w3c/csswg-drafts/issues/2066#issuecomment-557630869">issues</a>.</td></td> - -<td><td>Rob also attached Scroll Timeline into the Paint Worklet Lottie demo for a cool lighting talk (<a href="https://docs.google.com/presentation/d/124zcoxveCQyXVB4-HWCXhQptrnaHDE9JIXyQ8B1N4ig/edit#slide=id.g742aacb70c_9_789">slides</a>, <a href="https://youtu.be/dJmWLQn9g2A?list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&t=423">video</a>)!</td></td> - -<td></tr></td> -<td></table></td> - -<td>Last but not least</td> - -<td>There were several other topics that the animations team presented at BlinkOn. Rob drove a discussion about measuring real world throughput and latency. The team gave several project updates during the Lighting Talks session including Off-thread PaintWorklet (<a href="https://docs.google.com/presentation/d/124zcoxveCQyXVB4-HWCXhQptrnaHDE9JIXyQ8B1N4ig/edit#slide=id.g70a5f3c77e_102_92">slides</a>, <a href="https://youtu.be/FOCHCuGA_MA?list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&t=886">video</a>), Contribute to WPT (<a href="https://docs.google.com/presentation/d/124zcoxveCQyXVB4-HWCXhQptrnaHDE9JIXyQ8B1N4ig/edit#slide=id.g70a5f3c77e_102_0">slides</a>, <a href="https://youtu.be/FOCHCuGA_MA?list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&t=1021">video</a>), Throughput Metrics (<a href="https://docs.google.com/presentation/d/124zcoxveCQyXVB4-HWCXhQptrnaHDE9JIXyQ8B1N4ig/edit#slide=id.g742aacb70c_289_204">slides</a>, <a href="https://youtu.be/FOCHCuGA_MA?list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&t=1442">video</a>) and GroupEffect (<a href="https://docs.google.com/presentation/d/124zcoxveCQyXVB4-HWCXhQptrnaHDE9JIXyQ8B1N4ig/edit#slide=id.g742aacb70c_9_417">slides</a>, <a href="https://www.youtube.com/watch?v=z3EjkpvEWC4&feature=youtu.be&list=PL9ioqAuyl6UI6MmaMnRWHl2jHzflPcmA6&t=1455">video</a>).</td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | Nov & Dec 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/november-2021-highlights/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/november-2021-highlights/index.md deleted file mode 100644 index 1c87b4a6d7a..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/november-2021-highlights/index.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: november-2021-highlights -title: November 2021 highlights ---- - -<table> -<tr> - -<td>November 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td colspan=2>Resolved major spec issues with user activation</td></td> - -<td><td colspan=2>The HTML definition for “activation triggering events” has been incomplete since its inception, and that led to <a href="https://docs.google.com/spreadsheets/d/1DGXjhQ6D3yZXIePOMo0dsd2agz0t5W7rYH1NwJ-QGJo/edit?usp=sharing">significant inconsistencies</a> between browsers and redundancies in other specs that relied on HTML’s wording (e.g. in <a href="https://github.com/w3c/pointerlock/pull/70">PointerLock</a>).</td></td> - -<td><td colspan=2>mustaq@ recently resolved the long-standing <a href="https://github.com/whatwg/html/issues/3849">HTML issue</a> by securing consensus on removing high-level events, adding missing keyboard events, and fine-tuning all low-level events.</td></td> - -<td><td colspan=2><table></td></td> -<td><td colspan=2><tr></td></td> - -<td><td colspan=2><td> Before</td></td></td> - -<td><td colspan=2><td>After</td></td></td> - -<td><td colspan=2></tr></td></td> -<td><td colspan=2><tr></td></td> - -<td><td colspan=2><td><img alt="image" src="https://lh6.googleusercontent.com/9_UKpmUyXhKiMJNiMe1lmziVqYp1nMnyR3KdQI0e_d6Tj0eVKxD_fl6A8cIqVEUwADu8HatizK53sRGk865RY7YfjVtzBesDDZrhhIWlUiwHq5vDRrdFNriqz8wTV5RapstzSiXkk0rnINrw6aGXyov4KcwTOtFC7cVdCSskzy-BX6da" height=185 width=234></td></td></td> - -<td><td colspan=2><td><img alt="image" src="https://lh3.googleusercontent.com/7QumKLInjQCBAW1rqLpYRWK3qmqNYlZoshE9QdoB-ngXO3npKJFmSP8VchRBcnLZURYCytTtX2EQWil3Gurp7M3TGhtJ1QdI3wZNYiZNu4E9oXlaPWEb-qaZEv9_EnSxoDUXqtL4s7_hmzGSUdAIj8Ei_hNtWYbq1PNCNvp5FA0YSU_H" height=118 width=324.82328482328484></td></td></td> - -<td><td colspan=2></tr></td></td> -<td><td colspan=2></table></td></td> - -<td><td colspan=2>The HTML spec is now clear and precise, and it is supported by 5 automated web-platform-tests (html/user-activation/<a href="https://github.com/web-platform-tests/wpt/tree/master/html/user-activation">activation-trigger-\*</a>). </td></td> - -<td><td colspan=2>This HTML update immediately led to a <a href="https://github.com/w3c/pointerlock/pull/76">cleanup</a> in the PointerLock spec. Any other spec that had to patch over the past HTML gaps can now be fixed too.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Scripted smooth scroll adjustments</td></td> - -<td><td colspan=2>skobes@ has landed a patch that fixes scripted smooth scroll adjustments. A user smooth scroll now continues with adjustment when interrupted by an instant programmatic scroll. <a href="https://crbug.com/1264266">crbug/1264266</a></td></td> - -<td><td colspan=2><table></td></td> -<td><td colspan=2><tr></td></td> - -<td><td colspan=2><td>Before (Text is jumpy) </td></td></td> - -<td><td colspan=2><td>After (Text scrolls smoothly)</td></td></td> - -<td><td colspan=2></tr></td></td> -<td><td colspan=2><tr></td></td> - -<td><td colspan=2><td><img alt="image" src="https://lh3.googleusercontent.com/142qKkDoajLbtfL7yzPbGqEZN8pAlIWWepdc8Qqf1c208pStk9I_1T45qniqs5FQOgBVhKSqxC_b9PLLW1GZIwmFijBGNIgCNc4POaH46e3wNBoeZaXu7PXnUlB1i3RtSCvxfUVxKOUhGiKk0Gb019QxHLBarfq0BQh5DtJsgaWaN9Ky" height=257 width=274></td></td></td> - -<td><td colspan=2><td><img alt="image" src="https://lh6.googleusercontent.com/3fc4T-On-cu71DKzwB7nhKkEKv13d3KauaMyZ6u87W85J0vihxiYTasCBUY_tJJzyjvIjQyruC4hW4DU4phu93HEHYNFHaxgYYmebC0JDHxgnLMmlXEubR_yhLyjkyhymob2h8n6CbY-YMM4da4N7SomFBEXiCItXoceFsk30WUECQt7" height=257 width=274></td></td></td> - -<td><td colspan=2></tr></td></td> -<td><td colspan=2></table></td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Main thread scrolling reasons</td></td> - -<td><td colspan=2><img alt="image" src="https://lh3.googleusercontent.com/eQgY9T3BlD0XhA5IFVBydHJTeyPH_KGqkUDgk0OM0wJzgwMZ1F95a5vxvqKep4XCZX3Me0Ttl1ADeo-PAvrVMfiSREfDPFtbb-PjPPSSX8fy56kPS5-LcWnbsN97Y_JwKGh27FjNuK4PnlZ1Y83myXTdkTYueB005g07du6VYfKCagVx" height=287 width=576></td></td> - -<td><td colspan=2>skobes@ has landed a patch that changes reporting "main thread scrolling reasons" in a way that makes sense post <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=476553">Scroll Unification</a>. <a href="http://crbug.com/1082590">crbug/1082590</a></td></td> - -<td></tr></td> -<td><tr></td> - -<td><td rowspan=2>Fix Flaky animation tests</td></td> - -<td><td rowspan=2>Kevers addressed a number of flaky animation tests. In one batch of tests, the underlying problem was actually an infrastructure failure since results from one test were being compared with expectations for a different test. Nonetheless, some of these non-WPT tests lacked equivalent test coverage in WPT, and the failures presented a golden opportunity to migrate them to WPT. As part of the migration effort, tests were updated to make full use of the web-animations API.</td></td> - -<td><td rowspan=2><a href="https://chromium-review.googlesource.com/c/chromium/src/+/3269980">CL 1</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3270068">CL 2</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3272694">CL 3</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3273014">CL 4</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3275545">CL 5</a></td></td> - -<td><td rowspan=2>Numerical precision reared its ugly head again. </td></td> - -<td><td rowspan=2><img alt="image" src="https://lh5.googleusercontent.com/_IwuC55nDhhuQW4SRNqh14TCkIAWlReVyej8SdzZkjy3w4yGXSCtgnFKSv0v3KW8aBY9sEuN2mGfkCbRc2nNt_bkipKrsEahHare2VVHPr-17y1BPBmKdQjwbWfiCNEFUvJLGb0dFfqLJq-c859RNCYaJzd1zt6Hiuli604Rz0oHCb7I" height=17 width=279></td></td> - -<td><td rowspan=2>Fortunately, the web-animations-1 spec is clear on the required precision for animation timing, and this was an easy fix by simply changing to the already supported assert_times_equal, which has the specced 1 microsecond of slack (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3270992">CL</a>).</td></td> - -<td><td>Animation Construction</td></td> - -<td><td>Kevers resolved a crash on Android that was triggered by calling an animation constructor with a missing or destroyed execution context. It should be perfectly fine to trigger an animation in such cases. We simply can’t run script (e.g. event handlers or promise resolution code). The issue was fixed by conditionally setting the execution context (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3278735">CL</a>).</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>ScrollTimeline</td></td> - -<td><td>Kevers added support for progress based animations in our ScrollTimeline Polyfill (<a href="https://github.com/flackr/scroll-timeline/pull/37">PR</a>). Doing so required adding a polyfill for several sub-components since in the web-animations-1 spec, all timing is in ms, whereas in web-animations-2 timing may be in ms or expressed as a percentage. Polyfills to AnimationEffect and AnimationPlaybackEvent now support percentages. With the fix, the WPT tests now have a 94% pass rate!!</td></td> - -<td><td>The Blink implementation of ScrollTimeline was out of sync with the spec in regard to one of the timeline property names. The deprecated property scrollSource was replaced with the updated property name, source (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3261899">CL</a>). Though largely a mechanical change, it required updating 41 WPT tests. Landed this change unblocked a third party contributor from landing the equivalent fix to the Polyfill (<a href="https://github.com/flackr/scroll-timeline/pull/35">PR</a>). Thanks Bramus for diving in and contributing.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>CSS Selector Fragments</td></td> - -<td><td colspan=2>mehdika@ has landed a <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3172857">CL</a> that implements <a href="https://github.com/WICG/scroll-to-text-fragment/blob/main/EXTENSIONS.md#proposed-solution">CSS Selector fragments</a> behind this flag blink::features::kCssSelectorFragmentAnchor.</td></td> - -<td><td colspan=2><a href="https://en.wikipedia.org/wiki/Cat#:~:selector(type=CssSelector,value=img%5Bsrc$=%E2%80%9Dwhiskers_cat.jpg%E2%80%9D%5D)">https://en.wikipedia.org/wiki/Cat#:~:selector(type=CssSelector,value=img\[src$=”whiskers_cat.jpg”\])</a></td></td> - -<td><td colspan=2><img alt="image" src="https://lh6.googleusercontent.com/M5w0K4JhTXJPKC5sjZgDSmT-wQUEKXadYT4_pGWiTepxGhSnHsWdWFqI4r7u4m99W8pQVWucGAyccRXyS8Ul0_VgJYNdR4VMcVGiAgqEddlc2gmAjjaMcbcwkFWUjmkWXvMsTNePIrHBTUkqRWktJuMKviTmTDTOFrdhBGDCi-DBklm_" height=225 width=447></td></td> - -<td><td colspan=2>At this point the element is scrolled into the middle of the viewport. In the next step the element will be highlighted as well.</td></td> - -<td></tr></td> -<td></table></td> - -<td>Bug Status Update</td> - -<td><img alt="image" src="https://lh6.googleusercontent.com/yK_7AqZ_uk5AjVjn86eSaBZ04rGF7E6ZN50DubuNIkOatP7y0CyDmliuJeYIgaJyLMYWrInbCXOQ2SPXo-GxCsudLGxuIPil8BjmL5jASvbVTMs-77EpXUBKTG3jbVlDjSP37vI1jF6rh5dXCBhM1-MpYktBoMpxjRNB5XQy8awrInN_" height=279 width=505></td> - -<td><img alt="image" src="https://lh5.googleusercontent.com/8nkguJhKYxlkdIAAZo2yRzwDbvv4t8GEn5DGLwECoSD-TXqSwfXy268QOc0Sr7Vj5rlv5bpJgDnW_VTtyPDqf1QhBjYW91TUJQRR6PR5M7urHt6mKLitYzuXX2qBkWfh4MO0fCpANCYejBMRm7zYXtYUfeChGXw7wu5glhR7p4wzBzCr" height=264 width=479></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | November 2021</td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/october-2019/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/october-2019/index.md deleted file mode 100644 index 5acdbe02ab0..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/october-2019/index.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: october-2019 -title: October 2019 ---- - -<table> -<tr> - -<td>Oct 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Before</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/t8_ODuCgZ_gNvLhDkOp43QFiXky2FxOciZsXyORhVlUvvrv1fpoM33qc_89HOeHGuKx0-7rNd2zcHT8nM5AqUuL9bOenugdtekgjic5HeY4zcCGHWzjwkuATrUQHn83MWrvhYMr6" height=120 width=582></td></td> - -<td><td>October Update</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/yfD26OsVLnxH-_ToJy499nhllsQK1mdpYjQLFSugK2i3WxdL6c4X6hzZtstBE4L4hax21uM0wULmw39zdiWRjQ3dB9WNnwjs6S5Isxz1ye4Ap56Z9ft2SV1AvAVtLai5c58bm2Nn" height=108 width=582></td></td> - -<td><td>Goal</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/Vbaqe3mFSBV7_VEY0g0v0WI7Ah2xafMSGGsK3CvOr3G9vYpk500fPNpqBRLq-E2K8C1RTB2Oaf6mG-a0_gFseXL3c9U-Z5uqSPIegh4Rmj96RqKVyjABnQ9tqU1YFeO7dMyo6nzl" height=123 width=582></td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/BpYL2k0L7gpATooCPKgGPelqLnVlj6LEsY1lGXz0tgvjmN1n3zFuUTWdy-Z45B4-3UDUhoT-bF8gWysNjlSDnGkjxZXgW5s98KQFM_NDth-_lPzxCY7VVZhCG9PHtSNg6FYaD11l" height=20 width=208></td></td> - -<td></tr></td> -<td></table></td> - -<td> Figure. Refactoring Blink animation logic to align with specification model.</td> - -<td>Web Animations Microtasking</td> - -<td>Kevin (kevers@) has made lots of progress in landing a major refactor of Blink animation logic to match the web-animation processing model. Main changes include:</td> - - <td>Now using microtasks for finished promises / events.</td> - - <td>No more lazy update of variables affecting current time.</td> - - <td>Improved handling of edge cases (e.g. zero playback rate).</td> - - <td>Lots of changes in the works to align with the spec.</td> - -<td>Stephen (smcgruer@) <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=788440">implemented</a> accumulate composite for <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1829355">transform</a> and <a href="https://chromium.googlesource.com/chromium/src.git/+/cc208c1adc376fa59aaa07897ed0555cebece58e">filter</a> properties bringing us one step closer to feature parity with Gecko.</td> - -<td><table></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/IzZLxwrwIoPRBF9ygS4puJajKlGLO9P7BX0Y5TSvcQw-DKVye-NF3V28hLL1Fob9EBldzn3ierpk5elJYbFe5rjgmjwjBu96bvvdFmrViEpjaok-QoehyxOehllq5OIvEtHbGyOj" height=141 width=282></td></td> - -<td><td>Frame Throughput Metric</td></td> - -<td><td>The initial version of the <a href="https://uma.googleplex.com/p/chrome/histograms?sid=85974f925706cadddcae47f545d649f7">Frame Throughput</a> metric has landed. We have already made a few rounds of bug fixing and corrections.</td></td> - -<td><td>Gene (girard@) and Xida (xidachen@) have been <a href="https://docs.google.com/spreadsheets/d/1-KJDVN60XQNrMtMRTv_9GldGMEwMkCpdlBfWyqgdtOQ/edit#gid=0">evaluating</a> the metric to guide such refinements. </td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/2xiBdb-GDi7wBgSupyAy5TbFazbC4jt9a9Sm-Uviorw2PczfEA-gdObOhsM82bt_5biaQ__py9lhwpa3yCqnegvFAkIWiv4R301k7CzcWrpJ2WLm1PvFVS1liH3ogRLIXWdYLRqp" height=140 width=291>Group Effect Polyfilled</td></td> - -<td><td><a href="https://yi-gu.github.io/group_effect/">Group Effect</a> proposal has now a new functional<a href="https://yi-gu.github.io/group_effect/polyfill/"> polyfill</a> thanks to Yi (yigu@). He has been using this polyfill to experiments with richer API for stagger effects (e.g., 2d staggering and delay easing) and creating cool demos.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Scroll Timeline & Animation Worklet</td></td> - -<td><td>We (Majid, Yi from Chrome with Olga, Jordan from Edge team) have completed the <a href="https://docs.google.com/document/d/1laATsw0V4bibsADvps5vV2oVEyZgjXzs_LLxo7pzn00/edit?usp=sharing">design document</a> for the Scroll Timeline. We also worked on preparing a <a href="https://docs.google.com/presentation/d/12UNGCTJybiL5gEMAGY2f-05WxXARvNz4k-RS02qgNuU/edit">presentation</a> on it for BlinkOn to share its current status.</td></td> - -<td><td>Majid continued on improving Animation Worklet specifications (<a href="https://github.com/w3c/css-houdini-drafts/commit/ed84d19b90c459cf405bfb0fc98e6bbfe9ee5ea8">1</a>, <a href="https://github.com/w3c/css-houdini-drafts/commit/69d3ab9f72b76b5517227d8dd859efbea057f510">2</a>, <a href="https://github.com/w3c/css-houdini-drafts/commit/8448e9812d93c959b26f73197d91c7295f6bbad7">3</a>).</td></td> - -<td><td>Investing in Code Health</td></td> - -<td><td>George (gtsteel@) made progress toward removing the <a href="https://docs.google.com/document/d/1khxyBn8PIhDWZUen3GIH0sW-qTeyKB8qHO-bJZdAGOs/edit#heading=h.z1k0oapk1qmm">CSSPseudo element</a> which is also important for launching web-animations.</td></td> - -<td><td>Yi (yigu@) fixed an issue so we <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1825720">no longer</a> auto-composite scroll-linked animations.</td></td> - -<td><td>Majid (majidvp@) worked on <a href="https://docs.google.com/document/d/1isnrFwAqTjBYi5YnHI_GbQ33Q79Kq6nwae-9HJoBUyc/edit">figuring out</a> why scroll animations takeover logic got broken without us finding out and proposed a fix.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Snap, Harder Better Faster Stronger</td></td> - -<td><td>Kaan (alsan@) has been making many improvements (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1865048">1</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1865048">2</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1865048">3</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1902008">4</a>) to our scroll snap code resulting in fixes of long-standing bugs and enables landing additional features. He also implemented <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1845673">tracking snapped elements</a> which is the first part of snap-after-layout.</td></td> - -<td><td>Majid has reached out to our contact at Safari to help improve Scroll Snap interop. He worked to improve our wpt tests: upstreaming input driven scroll snap tests to wpt (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1893142">keyboard</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1922950">touch</a>), <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1003055">fixing</a> an issue to have 8 tests pass on Chrome.</td></td> - -<td><td>OT Paint Worklets Launch-ish </td></td> - -<td><td>This cycle Paint Worklet was launched briefly but had to be reverted due to <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1020238">unforeseen interactions</a> with OOP-R. In preparation for this launch Xida added necessary <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1827246">metrics</a> and improved stability (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/1838674">\[1\]</a> <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1789828">\[2\]</a>). We are now working to fix the newly discovered issue, improve test coverage, and relaunch.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | Oct 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table> - -<table> -<tr> -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/october-2020---code-health-scroll-timelines-synthetic-user-activation-scroll-unification-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/october-2020---code-health-scroll-timelines-synthetic-user-activation-scroll-unification-and-more/index.md deleted file mode 100644 index ecef49e12ee..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/october-2020---code-health-scroll-timelines-synthetic-user-activation-scroll-unification-and-more/index.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: october-2020---code-health-scroll-timelines-synthetic-user-activation-scroll-unification-and-more -title: October 2020 - Code Health, Scroll Timelines, Synthetic User Activation, Scroll - Unification and more! ---- - -<table> -<tr> - -<td>October 2020</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Code health</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/xJwdlxgVeI_5sRA_9M84xtpBFGxhvbM3k5rh8WkY1amz0En2FzMyDTzkbees703Q1p3NI8CCXvPeZKa3d6sws_iBMp_ghQCabFfO8UNZhaAIbfy0RyaOyHAdm24N6UZInFfdN-d4Xw" height=156 width=280></td></td> - -<td><td>The graph shows our latest bug fixing efforts in this sprint:</td></td> - - <td><td>We made steady progress on bug fixes.</td></td> - - <td><td>We held steady on P0s and P1s.</td></td> - - <td><td>Nearly held steady on P2s, which is awesome!</td></td> - -<td><td>Scroll timeline</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/ZbP3FFl7dRFLp2GGpe3p8KczY5F8HvAf8MZ1u3Qtg6WCfEUFazVxKtu1Gx3eD549C0XrFdj56u0_-JMEieRwgxJ03l7FgQc20XXdQ91LQYCJ6WI5ienDXocT5akvryNMG9r6ZKnnhA" height=173 width=280></td></td> - -<td><td>flackr@ made tremendous progress on scroll timeline polyfill:</td></td> - - <td><td>Landed 13 patches.</td></td> - - <td><td>Discovered two bugs.</td></td> - - <td><td><a - href="https://bugs.chromium.org/p/chromium/issues/detail?id=1136516">Wrong - error thrown</a>.</td></td> - - <td><td><a - href="https://github.com/w3c/csswg-drafts/issues/5599">rootMargin - missing in spec</a>.</td></td> - - <td><td>215 new passing tests out of 354 total tests. The above graph shows - the number of passing tests when each patch landed.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Synthetic user activation</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/c6IkBfhps0LESw400Jqxdjjpj7XsHgR2b6t-XUN9lfxnFPr90s_6w52JVkEwfmDhXopgnIkZr_7e8oog5hKmSNCSNxxuZ2LOtQZjpfsQzCZZT5DbbIyDk47-tCqnTwjRy6nFdSG8fg" height=61 width=280></td></td> - -<td><td>TriggerForConsuming</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/JjVgSv_R4_qqTxquFfOongu6_TRaLH6OFw5UMoL7mORq0-dTwwQgdk9rct47sueeDvMVmO9xuXPCfRDc_td0pjyhGgEpYGScfCY6L12DwPKLnw-TPfNfzonohCE378LwS9AEWv0gzA" height=73 width=280></td></td> - -<td><td>TriggerForTrasient</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/sh5326ffsVwtpQokg4bUu_7WDewdbY7pGXuf_KmzMREI4LJSqSbCWzGy4Zh4mtiYzaQaYp18zmM_JNWYOjagj8uRfAu-Fxr3c_5ObfCVeMhjiYHT7W4z4KweHJxSevTeWuvGcI9YDg" height=73 width=280></td></td> - -<td><td>TriggerForSticky</td></td> - -<td><td>mustaq@ has done with UMA for synthetic triggers.</td></td> - - <td><td>Seeing expected results for non-extensions, but not expected for - extensions!</td></td> - -<td><td>Scroll unification</td></td> - -<td><td>liviutinta@ organized the remaining work on scroll unification, and splits the work between Q4 2020 and Q1 2021. This <a href="https://docs.google.com/document/d/1O4vOub0CuXSbO-wAmDU1qe9D0wbdKT0y6sXIWTV67kY/edit">doc</a> captures the work nicely.</td></td> - -<td><td>Click/Auxclick as pointer event</td></td> - -<td><td>mustaq@ is working on a finch experiment on this feature..</td></td> - - <td><td>Ran finch experiment at 25% on Canary and Dev channels.</td></td> - - <td><td>Expanded finch experiment to 50% Canary and Dev - (08-Oct-2020)</td></td> - - <td><td>Currently in progress of moving to 50% on Canary, Dev and Beta - channels.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Composite transform animations containing percents</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/nQK5QSx3LIfliPdWvIqzLwi6DnDQfUoeKfI1WhQVbbsrxkk1ia7ArlTZJv4gTLWRWOkmcJgfEHYBu_i3RTYsBxVEm7boLhw_uMefaacgKyx9Nbdpgv4_FRD3-xwrLYIywp6GxOWhUg" height=152 width=280></td></td> - -<td><td>gtsteel@ has landed a complete implementation for animations targeting CSS boxes. The above <a href="https://codepen.io/george-steel/pen/PozWObd">demo</a> shows the difference of running the animation on the main vs the compositor thread (with artificial jank).</td></td> - - <td><td>This makes ~10% of transform animations potentially less - janky.</td></td> - -<td><td>Devtool input protocol</td></td> - -<td><td>lanwei@ has merged the spec change of adding pointerevent’s additional properties to Webdriver Action API and added these properties to Devtool Input Protocol.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/RQny9ZhNN2UyqoAqjiwuXqdTyl37qRD1F-nz_QzO0Ek9C8SfAi0NDPVJ2u98y_4sOnKitQoTKZLgNhavYFMXEltcjdwWsZlFSoECxfDXjNvfdpYja9lEUuIuUuT7o8xRO5aKKU3D8w" height=138 width=131><img alt="image" src="https://lh4.googleusercontent.com/kHpOsjzL05GfwKCnwHLX2ADNBpz5Cd4KiARdKGms-JT1T6ZTfgMcjet25TebhGV1D4w6gSH7wClwo9ZhvVhkpr0MbgYhbSc1WXfu1ZBITGep1yYN1X3_lMNlMHUOgbpFFHWwLbAYmA" height=132 width=144></td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | October 2020</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/october-2021---2-sprints-worth-of-highlights/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/october-2021---2-sprints-worth-of-highlights/index.md deleted file mode 100644 index c6a11d79139..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/october-2021---2-sprints-worth-of-highlights/index.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: october-2021---2-sprints-worth-of-highlights -title: October 2021 - 2 sprint's worth of highlights ---- - -<table> -<tr> - -<td>October 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>CompositeBGColorAnimation finch </td></td> - -<td><td>xidachen@ launched finch on the stable channel for 1% of the population (detailed <a href="https://docs.google.com/document/d/1Fkp7udbCgYqVtNf4gn-NXGVYamPrd_n0qKqalruTq6E/edit#heading=h.u1s0gwal1np6">result</a>). Overall, we got very good results on throughput metrics, but slightly more memory consumption on Windows (~1.5%). The increase in memory is explained by how garbage collection is scheduled. Most importantly, there was no regression on the first or large contentful paint.</td></td> - -<td><td>A crash was discovered owing to the fact that not all colors are handled the same way. System colors behave more like references. For example, the “Field” color refers to the default background color for an input field. The correct color is resolved later in the pipeline, and cannot presently be used with a composited background color animation. These animations are now deferred to the main thread (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3216109">link</a>).</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/HHMbn-fB8tWKPra3VxfAvEBGErp-QAtbBAmzeyoyRMtvaB_5Ga_Tlz0ncKLQR5LTZYE7OnyH8zUTpyWlL-aKxrPJvMZtuZjVLLkrSh9j6fGyvcDzjh_9eoOV93pzuO5yVGIdVX3WKg" height=83 width=283></td></td> - -<td><td>With this final known issue fixed, we’re ready to review performance metrics for launch.</td></td> - -<td><td>Scroll timeline</td></td> - -<td><td>kevers@ landed a number of spec changes to <a href="https://drafts4.csswg.org/web-animations-2/">web-animations-2</a> in support of <a href="https://css-tricks.com/practical-use-cases-for-scroll-linked-animations-in-css-with-scroll-timelines/">scroll-linked animations</a>. These spec changes largely address issues with timing in the API. Previously all timing was recorded in milliseconds. With progress-based animations, times are reported as CSSNumericValue percentages. The spec changes also address some edge cases for scroll-linked animations that are in the paused state as well as the effect phase when at limits of the scroll range.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/JacSGMav-KYulzw-o2qSwjnhif87ENbCnnElh-BoGEiXTArgrBbnlOaqgMOTfL0OLaCLcx46xUG0WqIU2Q4OGu2WAcl5sX1Gt6VuLD5kosGyilUdvC-EkzaLpk750h0LRMhdOizI3g" height=80 width=251></td></td> -<td><td>Pull request links: <a href="https://github.com/w3c/csswg-drafts/pull/6656">PR6656</a>, <a href="https://github.com/w3c/csswg-drafts/pull/6655">PR6655</a>, <a href="https://github.com/w3c/csswg-drafts/pull/6508">PR6508</a>, <a href="https://github.com/w3c/csswg-drafts/pull/6479">PR6479</a>. <a href="https://github.com/w3c/csswg-drafts/pull/6702">PR6702</a>, <a href="https://github.com/w3c/csswg-drafts/pull/6712">PR6712</a>.</td></td> - -<td><td>kevers@ fixed some flaky scroll animation tests (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3169158">link</a>). One source of flakes was caused by slight platform dependencies combined with floating point rounding errors. By tweaking the tests to not depend on scrollbar width and to have nice integer expected values, these tests no longer flake. The flakiness was discovered while working on a <a href="https://github.com/flackr/scroll-timeline">polyfill</a> implementation of scroll timelines. Another source of flakes was due to improper assumptions when making a style change before an animation frame (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3226725">link</a>).</td></td> - -<td><td>kevers@ fixed 2 clusterfuzz failures. Both were caused by unexpected input: malformed scrollOffsets (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3244932">link</a>), and unsupported effect delays (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3245202">link</a>).</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>\[Scroll Unification\] Web test burn-down</td></td> - -<td><td>Scroll unification is an important code health project to streamline the scrolling process. Currently, there are multiple code paths, which need to be considered when addressing a bug or updating scroll behavior. This cycle, skobes@ has focused on burning down the number of test failures.</td></td> - - <td><td>lock-renderer-for-middle-click-autoscroll.html (<a - href="http://crrev.com/925854">r925854</a>)</td></td> - - <td><td>scrollbar-double-click.html (<a - href="http://crrev.com/925896">r925896</a>)</td></td> - <td><td>background-attachment-local-scrolling.htm</td></td> - <td><td>plugin-overlay-scrollbar-mouse-capture.html</td></td> - - <td><td>reset-scroll-in-onscroll.html (<a - href="http://crrev.com/927008">r927008</a>)</td></td> - -<td></tr></td> -<td></table></td> - -<td> This reduced the number of outstanding web test regressions by 16%.</td> - -<td><table></td> -<td><tr></td> - -<td><td>Responsive composited animations</td></td> - -<td><td>kevers@ fixed the responsiveness of composited animations to changes in the animation environment (<a href="https://chromium-review.googlesource.com/c/chromium/src/+/3205715">link</a>). For main thread animations, ConversionCheckers detect changes that would affect interpolations of properties during an animation. These changes now trigger an invalidation of the compositor keyframe snapshots. Some further tweaks were required to defer updating the compositor snapshots until after the ConversionCheckers have run.</td></td> - -<td><td><table></td></td> -<td><td><tr></td></td> - -<td><td><td>@keyframes spin {</td></td></td> -<td><td><td> 0% { transform:</td></td></td> -<td><td><td> scaleX(var(--scale))</td></td></td> -<td><td><td> rotate(0deg); </td></td></td> -<td><td><td> }</td></td></td> -<td><td><td> 100% { transform:</td></td></td> -<td><td><td> scaleX(var(--scale))</td></td></td> -<td><td><td> rotate(180deg); </td></td></td> -<td><td><td> }</td></td></td> -<td><td><td>}</td></td></td> - -<td><td><td><img alt="image" src="https://lh6.googleusercontent.com/kInX8dX9QmbDrsLHGKAq0YXiT0CHnAr5ts0ud3AGUmYFsZsGsnCN3-9YzX353drQBISBBdkLQi8KcHb528Fi6frBU9uP_PiO_McqXVB6qMeV0iZlc_suQ1_C6MzmWHCv_JsnSPr4sQ" height=181 width=123></td></td></td> - -<td><td></tr></td></td> -<td><td></table></td></td> - -<td><td>Infinite user activation by extensions (mustaq@)</td></td> - -<td><td>Extension messaging API needs to trigger an artificial <a href="https://html.spec.whatwg.org/multipage/interaction.html#tracking-user-activation">user activation</a> in background scripts to allow access to user-activation-gated APIs like Permissions and popup. This trigger caused a challenging <a href="https://crbug.com/957553">P1 security bug</a> reported by a user 2+ years ago (internally we knew it even before that).</td></td> - -<td><td>The problem here is that a malicious site or extension can craft a delayed message-reply sequence to effectively extend the lifespan of the original user activation, and even repeat the sequence indefinitely to secure a “forever-active” state. That means, a single user click in one webpage could allow infinite popups from any tabs!</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/l0vhMbMctf57poYsl-uh5sgv7seC1o8DYejptY9Br5oTMupHsqEDh9DC7D-pKwr4USj280259hc2LKLByAhs2ZKnuex3hx1Qy4O7-Ueq1slSvvpjtbxdQ-dXGlhJTR9ByR1FcQ54zQ" height=220 width=208></td></td> - -<td><td>In addition to being a challenging problem by itself, the bug “worsened” two other security bugs (on leaking autofill <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=966562">966562</a> and bypassing sandbox restriction <a href="https://crbug.com/1035315">1035315</a>) in the last two years!</td></td> - -<td><td>After a long brainstorming through unactionable whiteboard drawings, <a href="https://uma.googleplex.com/p/chrome/histograms?sid=c4e21a8aa954807b89df16f4d2d8e9be">misleading UMA</a> discovery and stalled <a href="https://docs.google.com/document/d/1TKjjwFlQGh2LLm0_mOW6FJdmmwyOBMj_fdWJyAJ_Q50/edit?usp=sharing">design discussion</a>, we were able to find and <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3154195">land</a> a fix in Q3, yayy!</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Fixed overscroll glow position (flackr@)</td></td> - -<td><td>Overscroll glow on android <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1253617">could appear in the wrong position</a>.</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/eoyR3w60Cqa8PVbrNBA_9-jTOKg4on6uc6MSmCn4lAxrDCNlyY1H4Z59BVPs_fEwg6m7vJMCmylEAq3CF6UVFuxvOQQH-_4Lb5zis14Ox1erYLJLiP0gUd0G3Jx_44DhKMIVdRwO8g" height=153 width=283></td></td> - -<td><td>The scrollable viewport bounds didn’t include the current bounds delta from active touch dragging. Fixed <a href="https://chromium-review.googlesource.com/c/chromium/src/+/3188708">using ScrollTree::container_bounds</a>.</td></td> - -<td><td>Smooth scroll vs. JS scroll (skobes@)</td></td> - -<td><td>Achievements: Learned a lot about how to handle JS scrolls in the middle of a user-triggered smooth scroll (wheel, keyboard). Both the main thread and the compositor thread were handling this improperly in different ways. A <a href="http://crbug.com/1264266">new proposal</a> enables "adjustment" behavior in virtual scrollers.</td></td> - -<td><td><img alt="easeinout.png" src="https://lh4.googleusercontent.com/yGrqbqHLvUia7IuId5eOlAJfQBx_nDnxaIoHd3zkYY81tyIbm70sr05msy4z1E1VKMayvR5eN_AK49mDMAfUfmlpLmHKlgqOCYiNpw9GoSwuUkq6hmFltMGkvFXk4ybC-MZphtoMMA" height=145 width=148></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Bug status update</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/cvdKwm9SlfBYA9JJ7ZCu8HW2mH09w6K4DA8E0G-dSw8KEZyzgZv3n7BYQcJ-Aw1RRTxbI4NyFCmhlqQa7_IbwDMZFVCBjYTgPTYbTOAm3KWGwJSiRpIxKiRoeDdD8DTvQBHzSnnJ8Q" height=283 width=582></td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/E4JvRCP-MkjTLdZviSF1JP0GoQKf6eOo-EcjNwffwl9vb2xC1vurMJlK5P_xKXDSm21Act6-psqYt5c-R75tUc52VFLpa3OMvI9F18-OVU1md4y51HlQ5AhVdqbF17xYGf7KNn4O8Q" height=283 width=582></td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | October 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/september-2020---code-heath-animation-timelines-smoothness-metrics-animation-event-handlers-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/september-2020---code-heath-animation-timelines-smoothness-metrics-animation-event-handlers-and-more/index.md deleted file mode 100644 index 08f4a72cb27..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/september-2020---code-heath-animation-timelines-smoothness-metrics-animation-event-handlers-and-more/index.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: september-2020---code-heath-animation-timelines-smoothness-metrics-animation-event-handlers-and-more -title: September 2020 - Code Heath, Animation Timelines, Smoothness Metrics, Animation - event handlers and more! ---- - -<table> -<tr> - -<td>September 2020</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Code health</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/0HrjwnQsCSygr54-qmbiNzfVBw1RqBieD343JVyXPbrhYBqGlnv50ir3q4le1GU1buG2e-8iKD_UaD3I3Te7_4eIjCvj-1I9mtl7KRt453N_CEkU9jP7E6yT9v-DTuebsgckqmSJHQ" height=153 width=280></td></td> - -<td><td>kevers@ presented a graph to show the progress of bug fixing.</td></td> - - <td><td>In this sprint we closed a lot of bugs, but more were opened than - closed.</td></td> - - <td><td>We now have breakdowns by priority. Nice to see that we did not lose - ground on P0s or P1s.</td></td> - -<td><td>xidachen@ removed the usage of setTimeout in animations layout test, and replaced them with rAF.</td></td> - - <td><td>setTimeout can easily cause flakiness, especially on debug - bots.</td></td> - - <td><td>Animations are driven by animation frames, using rAF leads to more - robust tests.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/02ubEg_i85VG8_GcBTpvZdboNqtTJc85Q0f-ZaSo5QFTjU7_PEGRpiYSKHQ7XnZ1cr3ioGu3F87MfJWBh3NYtfF9zonWHQfhQ0OMxTyuyo4JK6byuDzTPP3B2wUuFTgh4zNKtnmeug" height=224 width=280></td></td> - -<td><td>Mutable timelines</td></td> - -<td><td>kevers@ has been working on scroll timelines and the above <a href="https://codepen.io/kevers-google/pen/VweomWY">demo</a> showcases mutable timelines, which are required for supporting css animation-timeline.</td></td> - - <td><td>The demo illustrates updating the animation timeline via the - web-animation API.</td></td> - - <td><td>Presently it is behind the scroll-timeline feature flag.</td></td> - -<td><td>kevers@ showed another fun <a href="https://codepen.io/kevers-google/full/YzqaLKQ">demo</a> for scroll timelines, which uses scroll position to drive a paint worklet animation..</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/XdD8nBBUsBXIe8J93a7ntjcLK2u30rEa-HahPlPUqLJoa30tSCebdA5oisoQCfrF4E7xkkqn7epvzJfX66TSyC9jPmq9AexhaIjBt7FWhKLEAo3HzfCbTHKA8DN9wedehK1sq_Vogg" height=133 width=280></td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Smoothness metrics</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/UOyYLsJ4A5m-FFWw5T2q6owRPLZloZXc-WO9zGJvAZ-RUXhQp5zj8rvZ5O7caDnbScfIIgHkEoHfj9n_7Ct9jVzjlvqk5apzJzV6_KhLmu5yBndzQR2VdzINsEgJjXT32c9VpvPfGg" height=217 width=280></td></td> - -<td><td>xidachen@ improved fps meter by making it account for page loading.</td></td> - - <td><td>The fps meter will reset itself at first contentful paint (which is - regarded as loading completed).</td></td> - - <td><td>The stats before first contentful paint will be discarded when we - report to UMA.</td></td> - -<td><td>Animation event handlers</td></td> - -<td><td>gtsteel@ landed the implementation for ontrasition\* event handler properties. Along with that, gtsteel@ also fixed animationcancel event so that it doesn’t fire after animationend.</td></td> - -<td><td>Zooming no longer breaks transitions</td></td> - -<td><td>gtsteel@ fixed a bug where zooming would cause transition event listeners to fire.</td></td> - - <td><td>Previously, we compared zoomed values when starting transitions, - then transitionend based on computed value.</td></td> - - <td><td>Now we calculate and compare computed values (as per spec) if zoom - changed.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Web tests ⇒ WPT</td></td> - -<td><td>liviutinta@ shared a <a href="https://docs.google.com/spreadsheets/d/1WCg_odYm124kf4Se5SLYq0nCk4yRQU3O6aFV7cWi2DI/edit#gid=0">sheet</a> that lists input related layout tests that we would like to move to wpt/. The spreadsheet also tracks the progress. </td></td> - -<td><td>WebDriver Actions API Spec</td></td> - -<td><td>lanwei@ has landed <a href="https://github.com/w3c/webdriver/pull/1522">spec change</a> that adds wheel input to the webdriver action API.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | September 2020</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/september-2020-vol-2---code-health-logical-property-animation-off-thread-paintworklet-capability-delegation-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/september-2020-vol-2---code-health-logical-property-animation-off-thread-paintworklet-capability-delegation-and-more/index.md deleted file mode 100644 index 0bd935d59c4..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/september-2020-vol-2---code-health-logical-property-animation-off-thread-paintworklet-capability-delegation-and-more/index.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: september-2020-vol-2---code-health-logical-property-animation-off-thread-paintworklet-capability-delegation-and-more -title: September 2020 (Vol. 2) - Code Health, Logical Property Animation, Off-thread - PaintWorklet, Capability Delegation and more! ---- - -<table> -<tr> - -<td>September 2020 (Vol 2)</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Code health</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/Ux83vqp9MnKpYUaJ908wGb3hTCOBEja8SrjjHF6iWiUkrPoB4VN24rnjkJH95Did60R5tZch82shQjpZOCiq2Q1yGjzK7f-7Ndes6IB0R_GdWeO3RJhoNg3r0iAAnARjJxiaidFWZQ" height=156 width=280></td></td> - -<td><td>kevers@ presented our bug fixing effort for the sprint. We closed a fairly large number of bugs and kept the number of P1 bugs fairly steady. Overall the number of bugs has increased.</td></td> - -<td><td rowspan=2>Logic clearly dictates…<img alt="image" src="https://lh6.googleusercontent.com/jJoZEGRrSbXcZ-3L4zcBHdorNiKa7ubKF14bTirLSh4vjhqZS16DOkKRue12sCHBVds5tpeJILUDWT_XkH703_TGCE0M_doid4HTeXbH6VVIinP8dj6ln4CmHWkSYRIbX0ZH-dBRbQ" height=228 width=217></td></td> - -<td><td rowspan=2>kevers@ implemented support for animating logical properties in CSS and programmatic animations. Logical properties depend on the writing mode and text direction. As these animation types have different rules for keyframe construction and reporting, resolving property values when there are potential collisions in longhand property names presented some interesting challenges. </td></td> - -<td><td rowspan=2>As a bonus, CSS animations now report computed values when fetching keyframes, fixing an issue with the resolution of variable references.</td></td> - -<td><td rowspan=2>The above <a href="https://codepen.io/kevers-google/full/wvGNBoL">demo</a> programmatically creates an animated overlay on the insert-inline-start property, which in turn maps to the physical property left, top or right depending on the writing system. Upwards of 60 logical properties can now be animated. </td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Off-thread PaintWorklet</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/Tz4cZdN5QEhQBj5vVeVoiHliFj9_8G2Sw7VqlOT6i_Nd-_Y_ZWRHcKZ-AvP38LygMWT6Iyl_vvndRt1To3_XJOpJ9Z3yg_w1HDqSAuZBPAPUmZ8NO0CRcAoCv28Tm4Odox7bwbOTIA" height=127 width=280></td></td> - -<td><td>xidachen@ has been improving the off-thread paint worklet.</td></td> - - <td><td>Previously, it was required to have ‘will-change: transform’ to - composite a paint worklet animation.</td></td> - - <td><td>With this improvement, that requirement is no longer needed and we - save some memory because there is no longer any composited layer for running - the paint worklet animation.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/ORNcx8zCjjHrDtuq4C2KwtJyV1AhaWjpkDAWUG54x7ubD1y8c2BWFQPqz2YgeQkehuonh5m3-fRePBQyU98lskx3TZ2uzKlN6ArNRRoPtAGE8_UhLVeqqZxlmof4giGq3BNcaZOYkw" height=156 width=280></td></td> - -<td><td>Wheel WPT infrastructure tests</td></td> - -<td><td>lanwei@ has been working on adding the Wheel input to the Webdriver Action API, writing a WPT infrastructure test and making some wheel WPT tests running automatically on WPT dashboard.</td></td> - -<td><td>Capability delegation</td></td> - -<td><td>mustaq@ now has an <a href="https://github.com/mustaqahmed/capability-delegation">explainer</a> and a WICG <a href="https://discourse.wicg.io/t/capability-delegation/4821">discussion</a> thread ready for wider review.</td></td> - -<td><td>Scroll unification</td></td> - -<td><td>liviutinta@ communicated with bokan@ on the scroll unification project, and</td></td> - - <td><td>Started this <a - href="https://docs.google.com/document/d/1O4vOub0CuXSbO-wAmDU1qe9D0wbdKT0y6sXIWTV67kY/edit">doc</a> - that captures the remaining work on scroll unification.</td></td> - - <td><td>Added a virtual test suite for scroll unification.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | Sept. 2020 (Vol 2)</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/september-2021---new-features-testing-code-health-interop-fixes-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/september-2021---new-features-testing-code-health-interop-fixes-and-more/index.md deleted file mode 100644 index 097da59c3b0..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/september-2021---new-features-testing-code-health-interop-fixes-and-more/index.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: september-2021---new-features-testing-code-health-interop-fixes-and-more -title: September 2021 - New features, testing, code health, interop fixes and more! ---- - -<table> -<tr> - -<td>September 2021</td> - -<td>Chrome Interactions Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/interactions-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter I: New features</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Capability Delegation</td></td> - -<td><td><img alt="image" src="https://lh3.googleusercontent.com/MG0xgExux0IXLJhml1xYx4KnCibC4LI9_Q9qW04jIjlFaEkh7MKOdMe49olq5XfTKyiYwb8rEeOE6n-Y8G0LXu-6T_42-4vnwi4aRXHtxGyJKJCV_CImQrLO9C-fdDg3g0RuPSnQog=s0" height=221.4676 width=124.0124> <img alt="image" src="https://lh6.googleusercontent.com/0HyrhEBh-ZWRaAxhrkkA5U4LFwor0Zsy7J1U4MpsXJv3GLxZgDSOtThkHBPlAQvvQQDZmZ9-nTX3O_2eLElAIq0hlRS9mG1sS3FvlyiBO-Sv_EsITp7NfaRqOrVzV4tNq64F40EeVg=s0" height=126 width=126></td></td> - -<td><td>mustaq@ has been working on the spec proposal for the capability delegation.</td></td> - - <td><td>We got official signal from Mozilla (annevk@): <a - href="https://github.com/mozilla/standards-positions/issues/565#issuecomment-918137857">useful/reasonable</a>.</td></td> - - <td><td>Mozilla also <a - href="https://github.com/WICG/capability-delegation/issues?q=is%3Aissue+author%3Aannevk+">started - bugs & enhancements</a> discussions.</td></td> - -<td><td>For payment capability delegation, the origin trial is now <a href="https://developer.chrome.com/origintrials/#/view_trial/640637046993453057">ready</a> for partners.</td></td> - -<td><td>Composite BG-color animation</td></td> - -<td><td>xidachen@ <a href="https://critique-ng.corp.google.com/cl/395582428">launched</a> the finch study for the feature CompositeBGColorAnimation on Beta channel, with 50% control vs 50% enabled. The preliminary <a href="https://uma.googleplex.com/p/chrome/variations?sid=15e5e4da675df567f60a113eb822ccde">result</a> looks very positive (Note that currently we have < 7 days of data). Here are some highlights of the result:</td></td> - - <td><td>We do see performance improvement on Animations Smoothness - metrics.</td></td> - - <td><td>There is no memory regression on Android</td></td> - - <td><td>There is no regression on FirstContentfulPaint and - LargestContenfulPaint.</td></td> - -<td><td>Elastic Overscroll</td></td> - -<td><td>flackr@ made great progress on launching elastic overscroll.</td></td> - - <td><td>The feature is now <a - href="https://chromium-review.googlesource.com/c/chromium/src/+/3150217">on - by default on tip of tree</a>.</td></td> - - <td><td>Merged <a href="https://crbug.com/1240789">reduce stretch amount</a> - and <a href="https://crbug.com/1232154">prefers-reduce-motion</a> behavior - back to M93.</td></td> - - <td><td>Finch <a href="https://critique-ng.corp.google.com/cl/396373932">min - version updated</a> to include two recent merges and <a - href="https://critique-ng.corp.google.com/cl/396395915">launched to 1% - stable</a>.</td></td> - - <td><td>Launch to 100% <a - href="https://critique-ng.corp.google.com/cl/396900469">out for - review</a>.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter II: Testing</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Composite BG-color animation</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/yxjOLd0Oe3UdEwcVc0hKOxt85oJgTV_DpzaLzp910D8YinzafDO8M4I_O4Ju7mr2j2vxAryh6lGXu1qSqog61i6D3_LlmxsT0dlvEM20IoOZqORNugQEOgHin-EHoaqKb9NC_MsZFw=s0" height=49 width=283></td></td> - -<td><td>xidachen@ fixed some very flaky paint worklet tests.</td></td> - - <td><td>Given that these are flaky tests, the auto bisect tool doesn’t work. - We have to manually bisect it to find out that it is due to the launch of <a - href="http://navigationthreadingoptimizations">this new feature</a> that - makes navigation faster.</td></td> - - <td><td>With many times of try and error, it seems that the combination of - paint worklet test + a simple div in ref.html somehow caused the crash. The - root cause is unknown yet.</td></td> - -<td><td>Cross-platform scroll-timeline tests</td></td> - -<td><td>kevers@fixed some scroll-timeline tests. The issues are:</td></td> - - <td><td>Error tolerances were too tight.</td></td> - - <td><td>Sensitive to scrollbar width (platform specific)</td></td> - - <td><td>Magic numbers in tests (tough to infer correctness at a - glance)</td></td> - - <td><td>Misleading calculations (e.g. scrollheight - clientHeight to compute - scroll range in both directions)</td></td> - - <td><td>Mixup of logical units in RTL tests.</td></td> - -<td><td>The issues were discovered when testing via polyfill implementation. A significant number of near misses in test failures.</td></td> - -<td><td>The solutions are:</td></td> - - <td><td>Compute error tolerance for percentage calculations based on a half - pixel error in the scroll position.</td></td> - - <td><td>Hide scrollbars to ensure that scroll-range is consistent across - platforms.</td></td> - -<td></tr></td> -<td></table></td> - -<td>Chapter III: Code Health</td> - -<td><table></td> -<td><tr></td> - -<td><td>Triage scroll unification failing web tests</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/84j_rIrI0nOqe3JLW1dWNKILLWEg5r8mwaWkxzSwjW5VkZihaJQFPCDfnU0VK1_eyYQ_mQ26CGWRmiSTDE8FW6LqoAKWV3in60STJOVorEcjsDJrjG-bzWrYw-y-WpS8_PA0o9gi1w=s0" height=231 width=582></td></td> - -<td><td>skobes@ triaged failing web tests for scroll unification and the details are captured <a href="http://go/su-web-tests">here</a>. At this moment, there are 30 failing tests</td></td> - - <td><td>13 failures from 4 functional regressions (3 P1s, 1 P2), bugs - filed</td></td> - - <td><td>Cannot touch-drag custom scrollbars, resize corners</td></td> - - <td><td>Re-latch when scroller removed from DOM</td></td> - - <td><td>Scollbar arrow click scrolls by only 1px</td></td> - - <td><td>12 failures from bad test (waitForCompositorCommit, rebaseline, - etc)</td></td> - - <td><td>5 requiring more investigation (3 plugin related)</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter IV: Interop fixes</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll-timeline polyfill</td></td> - -<td><td>kevers@ made more progress on scroll-timeline polyfill.</td></td> - - <td><td>Proxied AnimationEffect to override timing calculations</td></td> - - <td><td>Custom AnimationPlaybackEvents to report percentage based - times</td></td> - - <td><td>Removed time-range from scroll timeline proxy</td></td> - - <td><td>Conversion between percents for API and times for internal - use</td></td> - -<td><td>Two problematic tests remain with high failure rates, reminder average over 90% pass rate.</td></td> - -<td><td>The remaining work includes update timing and event phase.</td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td><td>Chapter V: Bug Updates</td></td> - -<td><td><img alt="image" src="https://lh5.googleusercontent.com/O41TurQq6k183Wi1Bg7WiqMm86Zyryrh2N4SBe26qOI9tehJiGOXVrrYn0OhPZWadxhcnCfjoAhVAFFsa9SKIz1Kj0o_63_YoYv3yK2An9kUMzhUUHkUY4-jqP6HRq49mtpro0N6QA=s0" height=153 width=275><img alt="image" src="https://lh4.googleusercontent.com/AiPQ4O6ynfCIoBuYCEXeEWtQ9bQIKTE25lLZ9ilCJZ3wsgcDb4qFIHvMrRJyxwBxL6iL83ROQUgrREMKi3I7SRDcDH4f2AknTHPEpU1w9bLmOTrzabJDweeJK4bMwumGcJUOk-qbdQ=s0" height=152 width=279></td></td> - -<td><td>Our team lost a bit of ground in P2s && P3s, but kept the P1s in check.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Interactions Highlights | September 2021</td> - -<td><a href="http://go/interactions-team">go/interactions-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/september-update/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/september-update/index.md deleted file mode 100644 index 07a8706195e..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/september-update/index.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: september-update -title: September 2019 ---- - -<table> -<tr> - -<td>September 2019</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh6.googleusercontent.com/sXy9qEAKUpZOSAjFMLPicre5Zj4uUdiukK-uBgf7lHbvH3comIpZuE30nOlH3Mmga03rJGC6Ctcjbg6K0KTjrrV37ALqs3-Cf0wnh0Sr9JuLwxPKaF_hChJuLsUJ--x95zyU725_" height=245 width=596></td> - -<td>TPAC - Technical Plenary And Cookies</td> - -<td>Several members of the team attended TPAC to make progress on key specifications. We did <a href="https://docs.google.com/document/d/1-y6rEBbOi3jXUtiuBW2ecmQSBKatCQu_ZC_N8yLY3DI/edit">pre-planning</a> ensuring key issues are filed and discussed with the right people. Full trip-report is <a href="https://docs.google.com/document/d/1S49ZrTaCV1KMkFK4hdtMwheM9Sjdd_eiyDqH0A-3q48/edit?usp=sharing">here</a> but some highlights from TPAC are:</td> - - <td>Agreements on deferring some small features (<a - href="https://github.com/w3c/csswg-drafts/issues/4300">1</a>, <a - href="https://github.com/w3c/csswg-drafts/issues/4299">2</a>, <a - href="https://github.com/w3c/csswg-drafts/issues/4301">3</a>) to web - animations level 2 paving the path for shipping level 1.</td> - - <td>Moving ScrollTimeline out of incubation with <a - href="https://github.com/w3c/csswg-drafts/issues/4337#issuecomment-532120609">agreements</a> - on remaining key issues.</td> - - <td>Progress on issues related to Group Effect and Matrix transforms.</td> - - <td>Kevin (kevers@) learned a lot about WPT and how we can use it more - effectively which he <a - href="https://docs.google.com/presentation/d/1hlweg5L2V6gyxtXnj6MeCTXqNHRMnvAILNDIPS8dnOc/edit?usp=sharing">shared</a> - with the team.</td> - -<td>All of these were a result of constructive discussions with collaborators from Microsoft, Mozilla and Apple.</td> - -<td><table></td> -<td><tr></td> - -<td><td>Scroll Timeline Polyfilled</td></td> - -<td><td>As part of TPAC preparation Majid (majidvp@) proposed <a href="https://github.com/w3c/csswg-drafts/issues/4337">element-based targeting</a> for ScrollTimeline. Rob (flackr@) wrote a full fidelity polyfill for ScrollTimeline which implements the proposal. He used the polyfill to create a compelling <a href="https://flackr.github.io/scroll-timeline/demo/parallax/">demo</a> of key usecases. The demo clearly shows the improved ergonomics which greatly helped in <a href="https://github.com/w3c/csswg-drafts/issues/4334">convincing</a> CSSWG on merits of the proposal. It also helped us validate the proposal and find several awkward parts of the current API <a href="https://github.com/w3c/csswg-drafts/issues/4324">\[1\]</a> <a href="https://github.com/w3c/csswg-drafts/issues/4325">\[2\]</a> <a href="https://github.com/w3c/csswg-drafts/issues/4327">\[3\]</a> <a href="https://github.com/w3c/csswg-drafts/issues/4336">\[4\]</a> <a href="https://github.com/w3c/csswg-drafts/issues/4323">\[5\]</a>.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/LSLhqQDlrowYd1CDTj-9Yy_6eCEW3TaIVeb_RnZb_5EnHqK09s6jVoIALIqsDPjMA7RsRQ7MCckZylwQ_vZd8wkV9wS_0UUoGx6bRQPANzz9culKlBGkKYBzJIaTCRDVPezZnXD8" height=504 width=283></td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Excellent Scroll Snap</td></td> - -<td><td>We continue to invest in making scroll snapping excellent. Kaan (alsan@) has made sure more wpt test pass in chrome <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1799387">\[1\]</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1799387">\[2\]</a> and pay some <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1801745">technical debts</a> while Majid worked on improving wheel scroll snapping <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1835012">\[1\]</a> <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1769044">\[2\]</a>. We also triaged and prioritized our bugs around interop after discussions with other browser vendors. </td></td> - -<td><td>Web Animation Progress</td></td> - -<td><td>Stephen (smcgruer@) spend time to <a href="https://docs.google.com/document/d/1YPgb85q9w3HGKuMb4YCgTNaUTcF9mkjcMmfb2AeD64I/edit#heading=h.luhqvvzi99ac">categorize</a> and file bugs for all remaining failures. Stephen also made <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=788440#c9">progress</a> on implementation of ‘composite: accumulate’ and several timing bugs <a href="https://chromium.googlesource.com/chromium/src.git/+/c004564dcd80e078136866d21ab942e78a93753a">\[1\]</a>, <a href="https://chromium.googlesource.com/chromium/src.git/+/73b9e0f4905111da5034767d7956eca0940aaac0">\[2\]</a>, <a href="https://chromium.googlesource.com/chromium/src.git/+/108ec45b194b5e9a16d91e1ef0cd4dd145b00ae6">\[3\]</a>.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/F6s9bCRSGPI3ox1LoaVo_us5MdXRLJ5gCkqrzeF20F_go4G9UT5eZonbRBwF1y0gE9MLmVF2jv1O25KOU24O9HJnq4JjRZdVJn8G09zur5yGrefzXV4GQy4oraN7LHK4Xht_yoHc" height=143 width=283></td></td> - -<td><td>Off-Thread Paint Worklet 3..2..1..🚀</td></td> - -<td><td>"If the intersection between weird and usable is your thing, you’ll feel right at home with paint worklets!" </td></td> - -<td><td>This is a quote from the <a href="http://cssconfbp.rocks/speakers/jeremy/">Paint Worklet presentation</a> in CSSConf Budapest which comes with some neat <a href="https://paintlets.herokuapp.com">demos</a>. All the demos works flawlessly off the main thread (with --enable-blink-features=OffMainThreadCSSPaint). This sprint Xida (xidachen@) ensured Off-thread Paint Worklet has a <a href="https://docs.google.com/document/d/1XzfgvEE7B-RZId7vKPO3a7jzcCYqoc_0D80ggotAiQo/edit#">launch plan</a> as we get very close on enabling it on ToT. He also landed <a href="https://chromium.googlesource.com/chromium/src.git/+/80da06275c6afa7b54e8bac39e138b823538c7a1">metrics</a> and fixed multiple crashes <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1828063">\[1\]</a> <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1831790">\[2\]</a> <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1789828">\[3\]</a>.</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/64I_PDKy4pCiACJrwKM_0GJSrxwaH3brwuyujUBCIajbcEoxb765OQ-8AG99o-7-d51IKaIVnPS85H5uPOnl289GVIehkgk09fsXebobI6s9KGOU-8IxTHt3UeK4kzGH5O0euSju" height=139 width=283></td></td> - -<td><td>Viz-HitTesting launched 1% on Stable</td></td> - -<td><td>This sprint Viz hit-testing V2 was launched 1% on Stable for non-CrOS. This was a boring launch thanks to many bug-fixes landed beforehand. On <a href="https://docs.google.com/document/d/1BJK_lcOnY6W5_Gjex44dVxc-sKDBpw4YU0zJlKQlkao/edit#heading=h.1ba74q72laoc">Windows</a> it shows that we are 32% better than the existing behavior on how many hit tests are handled synchronously.</td></td> - -<td><td>The performance on CrOS in 78 beta is fascinating. <a href="https://docs.google.com/document/d/1YZ6NsxiiC3g6D6TTBcoKlCAgttoH2TA2PNX9R_Cxrkw/edit#heading=h.vlq2ywuvza4d">96%</a> hit tests are synchronous. \\o/</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td>Code Health and Interop</td></td> - -<td><td>Stephen (smcgruer@) worked on improving web interoperability and compatibility by <a href="https://groups.google.com/a/chromium.org/d/msg/blink-dev/dxDGBFKvO3A/A2gajDMjAwAJ">shipping</a> ontransition event handlers. He spent time understanding webkit-prefixed versions usage and devised a plan for removal or standardization (<a href="https://github.com/whatwg/compat/issues/118">whatwg</a>, <a href="https://chromium.googlesource.com/chromium/src.git/+/85c09dce313fac83a250fd035b85fa7606f8b080">code</a>). George (gtsteel@) <a href="https://github.com/w3c/csswg-drafts/pull/4306">improved</a> css transitions specification and added new and cleaned up existing relevant tests <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1807297">\[1\]</a>, <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1809508">\[2\]</a>. Yi (yigu@) <a href="https://chromium-review.googlesource.com/c/chromium/src/+/1825720">removed</a> special compositing logic for ScrollTimeline making it simpler and more general.</td></td> - -<td><td>Team Changes</td></td> - -<td><td>Sadly our amazing Stephen (smcgruer@) is leaving the Animations team to join Ecosystem infrastructure team. While we are sad to see him leaving our team, we are happy that his passion, skills and leadership are going to have a large impact on the Web making it more interoperable. To ensure a smooth transition we have marked all bugs assigned to him as Hotlist-Interop ;). On the good news front, we have a new intern Kaan (alsan@) who is going to make Scroll Snapping more excellent, and noogler Haozhe (haozhes@) joining the team.</td></td> - -<td></tr></td> -<td><tr></td> -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | September 2019</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/highlights-archive/web-animation-scroll-linked-animation-snap-after-layout-throughput-metrics-and-more/index.md b/chromium/docs/website/site/teams/animations/highlights-archive/web-animation-scroll-linked-animation-snap-after-layout-throughput-metrics-and-more/index.md deleted file mode 100644 index 8c9f9251edb..00000000000 --- a/chromium/docs/website/site/teams/animations/highlights-archive/web-animation-scroll-linked-animation-snap-after-layout-throughput-metrics-and-more/index.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -- - /teams/animations/highlights-archive - - Highlights Archive -page_name: web-animation-scroll-linked-animation-snap-after-layout-throughput-metrics-and-more -title: Web Animation, Scroll-linked Animation, Snap after layout, throughput metrics - and more! ---- - -<table> -<tr> - -<td>February 2020</td> - -<td>Chrome Animations Highlights</td> - -<td>Archives: <a href="http://go/animations-team-highlights">go/animations-team-highlights</a></td> - -</tr> -</table> - -<table> -<tr> - -<td><img alt="image" src="https://lh6.googleusercontent.com/Duuu09yTSsJWnz8tD3LTf_8Efkat2mPX-57vvznGOi2ztEqT4jaREe0m6l_HTxhef-ztUn4IM2QsVA5VRpqu1DAQuJF2IMnuzkgnY1pXx5UneEIkdF88GxKN6LhRkMB1_9WfN48Q" height=360 width=254><img alt="image" src="https://lh5.googleusercontent.com/Pq6YWdKed4hu4OrROqEtMyda4ULyRcRr_Vvf6OAs2OMibUkmCQrZ7khiug4QjV2pEEAwpmaKAMQjdUQLaNrKvHS3z5VvNQ0s0s-KbOTJ9Ww1FwFlcK1-RY_ff41-jU-zirkVrgWD" height=359 width=329></td> - -<td>A further step of scroll-snap after layout</td> - -<td>In January we turned on the feature by default in Chrome 81. To better communicate with developers to deliver the feature to users, Yi (yigu@) worked with Adam (argyle@) and Kayce (kayce@) from the Web DevRel team and published a <a href="https://web.dev/snap-after-layout/">blog post</a> on <a href="http://web.dev">web.dev</a> with fresh demos. As Rick (rbyers@) <a href="https://twitter.com/RickByers/status/1235318530565984257">pointed out</a>, for years web developers have been asking how to keep the scroller from a chat app reliably stuck at the bottom. With scroll-snap after layout, developers can easily implement it with pure CSS (left gif). Moreover, they no longer need to add event listeners to force resnapping after layout changes such as rotating a device or resizing a window (right gif)!</td> - -<td><table></td> -<td><tr></td> - -<td><td>function flip() {</td></td> - -<td><td> anim.playbackRate = -anim.playbackRate;</td></td> - -<td><td>}</td></td> - -<td><td>Updating playbackRate caused unwanted jumping back and forwards, as an animation was not marked as outdated when resuming from a finished state.</td></td> - -<td><td><img alt="image" src="https://lh4.googleusercontent.com/qwecDRWN-ff5APjwvnBG-lmKnBTblQKFibqIJ5yQYJHSSRfZ63ccR-CfQqoLbl65JRktpUKHNl56OtALLB5C7vaGrRKnfotZxaxwCPpfe58vxam0XFKjTDCiKlBz1gXOjMWWbnuO" height=147 width=265></td></td> - -<td></tr></td> -<td></table></td> - -<td><table></td> -<td><tr></td> - -<td></tr></td> -<td><tr></td> -<td></tr></td> -<td><tr></td> - -<td><td>document.body.addEventListener(</td></td> - -<td><td> 'mousemove', evt => {</td></td> - -<td><td> const animation = circle.animate(</td></td> - -<td><td> { transform : 'translate(...)' },</td></td> - -<td><td> { duration: 500, fill: 'forwards' }</td></td> - -<td><td> );</td></td> - -<td><td> animation.finished.then(() => {</td></td> - -<td><td> animation.commitStyles();</td></td> - -<td><td> animation.cancel();</td></td> - -<td><td> });</td></td> - -<td><td>});</td></td> - -<td><td><img alt="image" src="https://lh6.googleusercontent.com/z5MCQctf8obsWW1sjlgqFKVR3vS4cvO9hnmJ3ORHu-uxuQ4gNeW7zFmIcMfLcXDUrERJdXJRn6ZWz7sO8rB7dGd_7R1qqRcLVnh4jSyYikPLrFqVHMsbVL3r_28KYcHMpCJuPiJv" height=133 width=248></td></td> - -<td><td>Require layout object when resolving style since style could be box size dependent.</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2># Animation.commitStyles did not correctly handle transforms</td></td> - -<td></tr></td> -<td><tr></td> - -<td><td colspan=2>Web Animation on the way</td></td> - -<td><td colspan=2>The team has made solid progress on new features and bug fixes. Kevin fixed the two regressions above. George (gtsteel@) completed the work on pseudo-element animations on both <a href="https://github.com/w3c/csswg-drafts/pull/4616">specification</a> and <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2031986">implementation</a> sides. As usual, Hao (haozhes@) made our implementation more interoperable by passing more wpt tests!</td></td> - -<td><td colspan=2><img alt="image" src="https://lh4.googleusercontent.com/qUQHx8YY3PrU0F3X-9OfErZR9IwlHsKsCElzfR8h0v9xGR824m708ECrqY_z6gvJHTRSIQWJH1pol7Sshj9rd2BkRqU0Q3jH8H8RSXVTZcXyO5NgXO4zigsDSUzncj_vUbXVvJAj" height=248 width=555></td></td> - -<td><td colspan=2><img alt="image" src="https://lh4.googleusercontent.com/tg1Bvj-WJkkw_QW8zVhsgu5AEO-blW-gYIZZL_l-nqcDPxQO89L0l3JIREtJ0-XMhXmEMIy-xDC36QbWsi-LsbHRpy8-7p57ppOCoyI922ZnUvkn64INt1hyGlg_J9HbZzCkov1a" height=251 width=555></td></td> - -<td><td colspan=2>A new path of throughput metrics</td></td> - -<td><td colspan=2>Frame throughput measures the smoothness of Chrome renderer. i.e. higher is better. However, it makes the UMA timeline hard to read. e.g. usually 90th percentile represents the 90% users with better results but it’s opposite in the throughput metrics. To better align with the UMA timeline, Xida (xidachen@) inverted the metrics Throughput with PercentDroppedFrames which still measures the performance but in a more readable way. For example, the graph in the above shows that at 90th percentile we have ~80% frames dropped.</td></td> - -<td><td colspan=2>Scroll-linked animations</td></td> - -<td><td colspan=2>We have been collaborating with Microsoft engineers towards shipping scroll-linked animations. Both Majid (majidvp@) and Olga (<a href="mailto:gerchiko@microsoft.com">gerchiko@microsoft.com</a>) became the <a href="https://drafts.csswg.org/scroll-animations/">specification editors</a> which helps with driving specification discussions and updates. This month, Majid wrote a <a href="https://github.com/w3c/csswg-drafts/pull/4751">PR</a> for css syntax and reviewed <a href="https://github.com/w3c/csswg-drafts/pull/4750">PR</a> to remove ScrollTimeline.fill. Gene (girard@) and Rob (flackr@) helped with reviewing all the outstanding spec issues and prioritized them. On the implementation side, Olga made solid progress on implementing scroll offset <a href="https://wicg.github.io/scroll-animations/#avoiding-cycles">snapshotting</a>; Majid started to prototype <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2070673">element based scroll offset</a> and Yi started to add support for <a href="https://chromium-review.googlesource.com/c/chromium/src/+/2084088">composited scroll-linked animations</a>.</td></td> - -<td></tr></td> -<td></table></td> - -</tr> -</table> - -<table> -<tr> - -<td>Chrome Animations Highlights | February 2020</td> - -<td><a href="http://go/animations-team">go/animations-team</a></td> - -</tr> -</table>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/index.md b/chromium/docs/website/site/teams/animations/index.md deleted file mode 100644 index 7a09e18f89e..00000000000 --- a/chromium/docs/website/site/teams/animations/index.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: animations -title: Animations Team ---- - -The animations team is an engineering team that aims to enable web developers to -deliver a smoother more responsive web. - -The team is responsible for maintaining and improving the animations -infrastructure, correctly effecting threaded scrolling and related effects -(fixed/sticky position, scroll snapping, etc) in the composited property trees, -and ensuring that sufficient targeting and hit testing information is generated -from Blink. - -See also our concrete [quarterly -objectives](/teams/animations/animation-objectives). - -## Goals - -* Performance - Smooth user interaction and animations (reliable 60fps - on today's hardware, 120 fps on tomorrow's) -* Predictability - Interoperable animations APIs on the 4 major - browser engines. -* Capabilities - Enable rich scroll and input linked effects popular - on mobile applications. - -## Activities - -The animations team is driving several ongoing efforts. - -* Houdini - * [Animation Worklet](/teams/animations/animation-worklet) - * [Paint Worklet](/teams/animations/paint-worklet) -* Optimized hit testing -* CSS Scroll Snap -* Web Animations -* [Scroll-linked Animations (Scroll - Timeline)](https://drafts.csswg.org/scroll-animations) - -We send out an ~monthly newsletter with our activities; feel free to [check out -our archives](/teams/animations/highlights-archive). - -## Organization - -### Mailing lists - -The team uses a public mailing list for technical discussions, questions, and -announcements. - -Email address: [animations-dev@chromium.org](mailto:animations-dev@chromium.org) - -Web archives: -[animations-dev](https://groups.google.com/a/chromium.org/forum/#!forum/animations-dev) - -We are also available in #animations on the [Chromium -Slack](https://docs.google.com/document/d/1nCqDQEF2pW5cUMNBBZPP20DZ7TVCu58ylhCk_Q8LqU4/edit). - -### Weekly Meeting - -There are two tri-weekly (once every three weeks) meeting held over video -conference on Tuesdays and another on Fridays for planning and going over -results. If you're interested in participating please reach out on the mailing -list or slack and we can share instructions. - -The meetings follow the following schedule: - -* Week 1: Planning meeting on Tuesday 2:30pm EST, [meeting - notes](http://bit.ly/animations-team-planning) -* Week 3: Demo meeting on Friday 11:00am EST, [meeting - notes](https://docs.google.com/document/d/15SH-FgMd0jPtUcPs_3A_JI9sOwmA1JrEZOHvIM8wIm0/edit?usp=sharing) - -Highlights from the demo meetings are shared in our ~monthly newsletter, see -Activities above. - -## Bug Triage - -The animations team is responsible for bugs filed in the -[Blink>Animation](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ABlink%3EAnimation+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids), -[Internals>Compositing>Animation](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AInternals%3ECompositing%3EAnimation&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids), -[Internals>Compositing>Scroll](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AInternals%3ECompositing%3EScroll&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids) -components. - -The team has a daily triage to confirm, triage, and categorize incoming bugs in -these components. - -## Related teams - -[Input](/teams/input-dev) - -[Rendering](/teams/rendering)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/animations/paint-worklet/index.md b/chromium/docs/website/site/teams/animations/paint-worklet/index.md deleted file mode 100644 index 30006a4d825..00000000000 --- a/chromium/docs/website/site/teams/animations/paint-worklet/index.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/animations - - Animations Team -page_name: paint-worklet -title: Paint Worklet ---- - -Paint Worklet, also known as the [CSS Paint -API](https://developers.google.com/web/updates/2018/01/paintapi), is an effort -to enable web developers deeper control of how elements on their page are -painted. More details can be found in the -[spec](https://www.w3.org/TR/css-paint-api-1/), but in short the API allows -developers to specify a custom JavaScript function for any CSS attribute that -can take a CSS -[<image>](https://developer.mozilla.org/en-US/docs/Web/CSS/image) type. -When the particular part needs to be painted, the JavaScript function is called -with a -[PaintRenderingContext2D](https://www.w3.org/TR/css-paint-api-1/#paintrenderingcontext2d) -that can be drawn into: - -paint(ctx, size) { ctx.fillStyle = 'green'; ctx.fillRect(0, 0, size.width, -size.height); } - -This functionality first shipped in [Chrome -M65](https://developers.google.com/web/updates/2018/03/nic65). - -Off-Thread Paint Worklet - -Off-Thread Paint Worklet ([design -doc](https://docs.google.com/document/d/1USTH2Vd4D2tALsvZvy4B2aWotKWjkCYP5m0g7b90RAU/edit?ts=5bb772e1#heading=h.2zu1g67jbavu)) -is an ongoing effort (as of 2019/01) to run the developer-provided paint -functions on a different thread than the main rendering loop, and asynchronously -from the standard document lifecycle. The goal is performance isolation, to -allow smooth animation of Paint Worklet-painted elements even when the main -thread is busy. This is considered an architectural improvement project and -should not be visible to web developers (other than in improved performance of -pages that use Paint Worklets).
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/binding-team/index.md b/chromium/docs/website/site/teams/binding-team/index.md deleted file mode 100644 index 258b7e160e9..00000000000 --- a/chromium/docs/website/site/teams/binding-team/index.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: binding-team -title: Binding Team ---- - -## Goals - -* [Binding team - OKRs](https://easyokrs.googleplex.com/edit/binding-dev/) - (Google-internal only) - -## Projects - - Make Window objects interoperable - ([Overview](https://docs.google.com/presentation/d/18Ap_EKEBu7nzDrlFM7FbCR4EgrNd3ryLabJUh-YvEwM/edit?disco=AAAAARwFnJ0&pli=1#slide=id.g2480feb0_1_0)) - - Script-disabled rendering - ([Overview](https://docs.google.com/document/d/1p0yHAhx_DLOlP94LzcuGcr5KS0rGBEPhyLeVa6KZs7k/edit)) - -We're sending weekly snippets to -[blink-dev@](https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev) -(Search "binding team snippet"). - -## Members - -haraken@chromium.org (TL) - -yukishiino@chromium.org - -bashi@chromium.org (mostly spending time on memory team) - -tasak@chromium.org (mostly spending time on memory team) - -jl@opera.com (mostly spending time on other stuff) - -Contact blink-reviews-bindings@chromium.org if you have any feedback or -questions.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/device-team/index.md b/chromium/docs/website/site/teams/device-team/index.md deleted file mode 100644 index 8c157e13bec..00000000000 --- a/chromium/docs/website/site/teams/device-team/index.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: device-team -title: Device Team ---- - -The device team works on increasing Web App capabilities by exposing device -features. - -Components: - -* Blink>Bluetooth -* Blink>HID -* Blink>GamepadAPI -* Blink>Geolocation -* Blink>NFC -* Blink>Sensor -* Blink>Serial -* Blink>USB -* Blink>WakeLock -* IO>Bluetooth -* IO>HID -* IO>Gamepad -* IO>USB - -## Communication - -* device-dev@chromium.org [email - group](https://groups.google.com/a/chromium.org/forum/#!forum/device-dev). -* [#fugu channel on Chromium - Slack](https://app.slack.com/client/T039UTRBS/CGJU5JZAS)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/devtools/index.md b/chromium/docs/website/site/teams/devtools/index.md deleted file mode 100644 index b45f18125fd..00000000000 --- a/chromium/docs/website/site/teams/devtools/index.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: devtools -title: DevTools ---- - -The DevTools team mission is to - -> Make Chrome DevTools the web development tool of choice, - -> and help web developers adopt web platform’s best - -> features and practices in support of their success. - -Please also see our concrete [Chrome DevTools team -OKRs](https://easyokrs.googleplex.com/view/chrome-devtools) (Google-internal -only). - -**Design Documents** - -For proposing contributions, please refer to our [design -guidelines](https://chromium.googlesource.com/devtools/devtools-frontend/+/HEAD/docs/design_guidelines.md). - -**Contact** - -The team uses a public mailing list for technical discussions, questions, and -announcements. - -Email address: [devtools-dev@chromium.org](mailto:devtools-dev@chromium.org) - -Web archives: -[devtools-dev](https://groups.google.com/a/chromium.org/forum/#!forum/devtools-dev) - -**Bug Triage** - -The DevTools team is responsible for bugs filed for the -[Platform>DevTools](https://bugs.chromium.org/p/chromium/issues/list?q=component%3APlatform%3EDevTools) -component. - -**Members** - -* yangguo@chromium.org (EngM) -* hablich@chromium.org (TPM) -* bmeurer@chromium.org (TL) -* sawallner@chromium.org (PM) -* petermueller@chromium.org (UX) -* jec@chromium.org (DevRel) -* aerotwist@chromium.org -* alexrudenko@chromium.org -* andoli@chromium.org -* changhaohan@chromium.org -* jacktfranklin@chromium.org -* janscheffler@chromium.org -* kimanh@chromium.org -* leese@chromium.org -* mathias@chromium.org -* petermarshall@chromium.org -* pfaffe@chromium.org -* sadym@chromium.org -* sigurds@chromium.org -* szuend@chromium.org -* tvanderlippe@chromium.org -* wolfi@chromium.org
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/dom-team/index.md b/chromium/docs/website/site/teams/dom-team/index.md deleted file mode 100644 index 94b0cb07500..00000000000 --- a/chromium/docs/website/site/teams/dom-team/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: dom-team -title: DOM Team ---- - -The DOM team is (as of spring 2019) now part of the -[rendering](/teams/rendering) super-team. More information will be added here -soon. - -**Contact:** - -* dom-dev@chromium.org -* masonfreed@chromium.org -* yuzhehan@chromium.org -* jarhar@chromium.org
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/ecosystem-infra/index.md b/chromium/docs/website/site/teams/ecosystem-infra/index.md deleted file mode 100644 index 23f11bd2038..00000000000 --- a/chromium/docs/website/site/teams/ecosystem-infra/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: ecosystem-infra -title: Ecosystem infra ---- - -*Last updated: July 2019* - -"Establish the infrastructure and culture of testing for the web ecosystem to -ensure a predictable experience." - -Our vision is for the web platform to be engineered as a single, cohesive -product. As a natural outcome of our engineering practices and norms, a change -to any one part of the ecosystem reliably propagates to all others, with minimal -friction. The top priority is real-world interoperability of implementations; -standards and tests are important means to that end. - -[Team Charter](https://bit.ly/ecosystem-infra)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/index.md b/chromium/docs/website/site/teams/index.md deleted file mode 100644 index c9d1061e99e..00000000000 --- a/chromium/docs/website/site/teams/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -breadcrumbs: [] -page_name: teams -title: Teams ---- - -{% subpages collections.all %} diff --git a/chromium/docs/website/site/teams/input-dev/index.md b/chromium/docs/website/site/teams/input-dev/index.md deleted file mode 100644 index 428d6a95f54..00000000000 --- a/chromium/docs/website/site/teams/input-dev/index.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: input-dev -title: Input Team ---- - -*The Chromium Input team (aka input-dev)* is a web platform team focused on -making touch (P1) and other forms of input (P2) awesome on the web. High-level -goals: - -* Measure & improve input-to-paint latency. Web pages should stick to - your finger! -* Reduce web-developer pain points around input and scrolling, - including improving interoperability between browser engines, - predictability, simplicity and consistency between chromium - platforms. -* Enable high-performance rich touch interactions (such as - pull-to-refresh) on the web. -* Ensure Chrome UI features driven by input over the contents area - provide a great experience to both end-users and web developers. -* Enable the productivity of any chromium developer working with - input-related code through effective code ownership and code health - initiatives. - -See also our concrete [quarterly objectives](/teams/input-dev/input-objectives). - -**Contacts** - -[input-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/input-dev) -is our mailing list, and we also use the #input-dev channel on [Chromium -Slack](https://chromium.slack.com). - -**Useful bug queries** - -* [Blink>input, - Blink>scroll](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ABlink%3EInput%2CBlink%3EScroll&sort=-id+-modified+-opened&colspec=ID+Pri+Summary+Modified+Opened&x=m&y=releaseblock&cells=ids) - - all (or most) bugs we're tracking -* We triage the bugs almost daily with [this - process](https://docs.google.com/document/d/1IDjoUbe8_1lbhM10EVHwvMi0g9EUXImy0ufxtfvJqe0/edit). -* [Available - bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ABlink%3EInput%2CBlink%3EScroll+status%3AAvailable+&sort=-id+-modified+-opened&colspec=ID+Pri+Summary+Modified+Opened&x=m&y=releaseblock&cells=ids) -* [Code cleanup - ideas](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ABlink%3EInput%2CBlink%3EScroll+Hotlist%3DCodeHealth+&sort=-id+-modified+-opened&colspec=ID+Pri+Summary+Modified+Opened&x=m&y=releaseblock&cells=ids) - -**Related specifications & Working Groups** - -If you want to get involved with any of the specifications or just get all the -updates make sure to join their public mailing lists as well. - -* [W3C UI Events](https://w3c.github.io/uievents/) -* [W3C Pointer Events](https://w3c.github.io/pointerevents/) -* [W3C Pointer Lock](https://w3c.github.io/pointerlock/) -* [W3C Touch Events](https://w3c.github.io/touch-events/) -* [W3C CSS](https://drafts.csswg.org/) -* [WHATWG DOM](https://dom.spec.whatwg.org/) -* [WHATWG HTML](https://html.spec.whatwg.org/) - -**Presentations & Talks** - -* [Overscroll - Customization](https://www.youtube.com/watch?v=sp1R-0dd7qg&t=18m54s) - lightning talk -* [Scroll into - text](https://www.youtube.com/watch?v=sp1R-0dd7qg&t=15m50s) - lightning talk -* [Event Delegation to - Workers](https://docs.google.com/presentation/d/1BCEbLCg-o_Ko65byel5QGnO7Cwf5aPZPjqnnMNbbA5E/edit#slide=id.g5636de1525_0_0) -* [Fling On - Browser](https://docs.google.com/presentation/d/1miFAvKuz7tRT4IX_nCwZshFkUDX8bDYqfPlTOm2LS8U/) -* [Scroll & Input - Prediction](https://docs.google.com/presentation/d/18Dv2KBJxHnNezrTCzz29IyczhJwSIs8kTzwl2FuvGq0/edit#slide=id.p) -* [WPT - Automation](https://drive.google.com/file/d/1eBa7OvO6O9UefK-AYkclFz46ArGZ5iyH/view) -* [Browserside User - Activation](https://docs.google.com/presentation/d/1sEBwQZJ8w47OC7m2LexiJor8nUWPhqDaXqP5aWhYK60/) -* [Root - Scroller](https://docs.google.com/presentation/d/1nfM4jjQt9pijIThK8KSwavdZtWgifDjo6odHNg-ThvM/) -* Extensible Scrolling - BlinkOn 3 (Nov 2014): - [slides](https://docs.google.com/a/chromium.org/presentation/d/1P5LYe-jqC0mSFJoBDz8gfJZMDwj6aGeFYLx_AD6LHVU/edit#slide=id.p), - [video](https://www.youtube.com/watch?v=L8aTuoQWI8A) -* [Smooth to the touch: chromium's challenges in input on - mobile](https://docs.google.com/a/chromium.org/presentation/d/1VYfCKye4TM-QiR_hiLvwYxhci_xc5YcA4oZxtrp2qes/edit#slide=id.p) - - BlinkOn 2 (May 2014) -* [Input - BlinkOn - 1](https://docs.google.com/a/chromium.org/presentation/d/1J1jG0XF6k42PA4s-otHFXZxrou7aKwYKYF90xPOe9bQ/edit#slide=id.p) - (Sept 2013) -* [Point, click, tap, touch - Building multi-device web - interfaces](https://developers.google.com/events/io/sessions/361772634) - - Google I/O 2013 - -**Design Docs** - -* [Scroll - Unification](https://docs.google.com/document/d/1op5USoxDnN6yxB8EiFHYcGHacrZZRVKVqu4mSXFd6Ns/edit) -* [Chromium input latency - tracking](https://docs.google.com/a/chromium.org/document/d/1NUYMVyUJSU2NYrpGhKNfjSmmVZyPYoqbrPs7tbdY9PY/edit) -* [Scroll-blocks-on: scrolling performance vs. richness - tradeoff](https://docs.google.com/a/chromium.org/document/d/1aOQRw76C0enLBd0mCG_-IM6bso7DxXwvqTiRWgNdTn8/edit) -* [Chromium throttled async touchmove - scrolling](https://docs.google.com/a/chromium.org/document/d/1sfUup3nsJG3zJTf0YR0s2C5vgFTYEmfEqZs01VVj8tE/edit) -* [Gesture - Recognition](http://www.chromium.org/developers/design-documents/aura/gesture-recognizer) -* [Vsync-aligned buffered - input](https://docs.google.com/document/d/1L2JTgYMksmXgujKxxhyV45xL8jNhbCh60NQHoueKyS4/edit?usp=sharing) -* [Touchpad and Wheel - Latching](https://docs.google.com/document/d/1BizkQyW_FDU98sGxbHOZsAQWGYIA3xxXoFQZ3_XNo1o/edit) -* [Touchpad pinch - zoom](https://docs.google.com/document/d/1cYdt9r9stHLA2lbJ2I-Ucl_djhdSyngYFbmufZaLRHE/edit?usp=sharing) -* User Activation v2 - * [How Chrome uses user - gestures](https://docs.google.com/document/d/1mcxB5J_u370juJhSsmK0XQONG2CIE3mvu827O-Knw_Y/edit?usp=sharing) - (May 2017) - * [Case study: Popup with user-activation across - browsers](https://docs.google.com/document/d/1hYRTEkfWDl-KO4Y6cG469FBC3nyBy9_SYItZ1EEsXUA/edit?usp=sharing) - (May 2017) - * [User Activation v2: Main - design](https://docs.google.com/document/d/1erpl1yqJlc1pH0QvVVmi1s3WzqQLsEXTLLh6VuYp228/edit?usp=sharing) - (May 2017) - * [User Activation v2 with site - isolation](https://docs.google.com/document/d/1XL3vCedkqL65ueaGVD-kfB5RnnrnTaxLc7kmU91oerg/edit?usp=sharing) - (May 2018) -* Input for Worker: - * Initial design discussion: [Low-latency Event Handling in - Worker](https://docs.google.com/document/d/165f85uAKlknlQHwPkmpqLVq0O50XVkxzgTkO4utAsds/edit?usp=sharing) - (July 2017) - * JS API proposals for [Routing Worker Events through the - Compositor - Thread](https://docs.google.com/a/chromium.org/document/d/1Ah3-O7Emp7cURyh-TINME0fId9laU0ctMCwjmlArgqU/edit?usp=sharing) - (July 2017) -* [Plumbing mouse as mouse on - Android](https://docs.google.com/document/d/1mpBR7J7kgTXvp0QACVjhxtwNJ7bgGoTMmxfxN2dupGg/edit?usp=sharing) - (October 2016) -* [Coalesced - Events](https://docs.google.com/document/d/1x-e8fH3I0DBrmrNufPQwRJHMYnW5q9CYZVEHe7BsfpI/edit?usp=sharing) - (October 2016) - -# **Learning Resources** - -* [Chromium touch pipeline - overview](https://docs.google.com/a/chromium.org/presentation/d/10oIOTWFKIHArnfk8ZZx-9evvDpWC9EwRjDrZIz83Dz0/edit) -* [Scrolling in blink](http://bit.ly/blink-scrolling) -* [Android tracing cheat - sheet](https://docs.google.com/presentation/u/1/d/1poMF7AEu5vd21BzUTIYfm2SXurEMlv2OVDlzs6JNRfg/edit?usp=sharing) -* [Blink coordinate - spaces](/developers/design-documents/blink-coordinate-spaces) -* [Touch event behavior details across - browsers](https://docs.google.com/a/chromium.org/document/d/12k_LL_Ot9GjF8zGWP9eI_3IMbSizD72susba0frg44Y/edit#heading=h.nxfgrfmqhzn7) -* [Issues with touch - events](https://docs.google.com/a/chromium.org/document/d/12-HPlSIF7-ISY8TQHtuQ3IqDi-isZVI0Yzv5zwl90VU/edit#heading=h.spopy4jje82p) -* [Debugging common website touch - issues](https://docs.google.com/a/chromium.org/document/d/1iQtI4f47_gBTCDRALcA4l9HL_h-yZLOdvWLUi2xqJXQ/edit)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/input-dev/input-objectives/2015-okrs/index.md b/chromium/docs/website/site/teams/input-dev/input-objectives/2015-okrs/index.md deleted file mode 100644 index 853a090eeb9..00000000000 --- a/chromium/docs/website/site/teams/input-dev/input-objectives/2015-okrs/index.md +++ /dev/null @@ -1,428 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/input-dev - - Input Team -- - /teams/input-dev/input-objectives - - Input Objectives -page_name: 2015-okrs -title: 2015 OKRs ---- - -## 2015 Q4 0.54 - -### Improve input latency and smoothness 0.40 - -## Ensure mean_input_event_latency time remains under 12ms on N5/One for 90% of -key_mobile_sites_smooth at least 90% of the time P2 1.00 - -## Get EventListenerOptions into official DOM event spec P1 0.70 - -## Implement and ship EventListenerOptions to support registering passive event -listeners. P1 0.30 - -## Ship UX (hung renderer dialog) for unresponsive sites on Android P4 0.00 - -## VSync-aligned touch input working with unified BeginFrame on Aura P4 0.00 - -## Reduce smoothness.pathological_mobile_sites.first_gesture_scroll_update on -the Nexus 5 by 20% P4 0.00 - -## Impl side hit-testing against property-tree and display lists. P4 0.00 - -### Improve understanding of real-world input performance 0.40 - -## Expose hardware input timestamps to the web P1 0.95 - -## Implement experimental input latency web API in M49 P1 0.00 - -## Expose scroll latency in DevTools somehow P1 0.30 - -## Concrete scroll latency API presented to web-perf WG at TPAC P1 0.10 - -## All touch latency UMA regressions have appropriate owners within 3 weeks. P3 -1.00 - -## Add UMA metrics for determining potential benefit of passive event listeners -P2 1.00 - -## Add touch latency metric measuring until estimated vsync time. P2 0.00 - -## Better measure blink hit-test performance P4 0.00 - -## Use input-related perf insights data to drive performance investigations, 12 -associated Hotlist-Jank bugs P4 0.10 - -### Eliminate key developer pain points around input 0.56 - -## Fix at least 150 Hotlist-Input-Dev bugs P1 0.60 - -## Implement root-layer-replacement mechanism for fullscreen and non-body root -scrollers P1 0.30 - -## Ship more rational mode of top control resizes P1 0.60 - -## Triage any new Blink-Input, Blink-Scroll bug within 7 days P1 1.00 - -## Spec and land API to control Chrome pull-to-refresh nav gesture behind a flag -P2 0.10 - -## Drive adoption of history Scroll Restoration API P2 1.00 - -## Implement unified OSK viewport behavior between Android and CrOS for M49 -behind a flag P3 0.50 - -## \[STRETCH\] Allow "non-scrolling" apps to interact well with top controls -(behind a flag) P4 0.00 - -## \[STRETCH\] Implement new input modality media queries P4 0.00 - -## \[STRETCH\] Implement position: device-fixed behind a flag P4 0.00 - -### Improve interoperability between major browser engines 0.55 - -## Enable automated input testing on Chrome for W3C web-platform-tests P1 0.50 - -## Ship spec-correct body scroll API behavior P1 0.20 - -## Make all position-related APIs relative to Layout Viewport P1 1.00 - -## Make Chromium reliably send MouseLeave events to blink P1 0.60 - -## Ship KeyboardEvent.key in M48 P1 0.20 - -## Identify and fix 3 interop bugs with mouse events. P1 1.00 - -## Triage all Hotlist-Interop bugs and find appropriate owners every week P2 -0.60 - -## Fix international keyboard events P3 0.20 - -## Ship HTMLSelect.open API P3 0.00 - -### Enable rich scroll effects 0.45 - -## Prototype snap-points implementation in M47 P1 0.40 - -## Enable scroll customization on UIWorker thread P1 0.50 - -## Ship scroll latching for touchpad behind a flag for one platform P4 0.10 - -## Smooth scrolling for wheel and keyboard scrolls in Win/Linux enabled on trunk -P2 0.90 - -## STRETCH: Ship scroll latching for touchpad on all platforms P4 0.00 - -## Prototype sticky implementation in M48 P1 0.40 - -### Continue PointerEvent API implementation 0.73 - -## Fire pointer events for all mouse events P1 1.00 - -## Add chorded button transformation to mouse->pointer event generation logic -P1 1.00 - -## Update MouseEvent (and so PointerEvent) to support fractional co-ordinates P3 -0.20 - -## Extend WebMouseEvent to become a pointer event API P3 0.00 - -## Implement pointer-id ranges for all pointer types P2 1.00 - -## Make PointerEvents work for stylus in CrOS & Android. P2 0.70 - -## Force pointercancel firing with mouse off the page. P3 0.00 - -## Add pointer event handler tracking P3 0.00 - -## STRETCH: Explore design choices for explicit pointer capture support P4 - -### Evolve touch platform UI 0.56 - -## Ship unified touch text selection for native Aura UI P1 0.10 - -## Make check boxes and radio buttons touch friendly without depending on touch -adjustment P1 0.60 - -## Support trackpad pinch-zoom on CrOS P2 0.80 - -## Show touch selection handles when scrolling on CrOS P3 0.00 - -## Close 10 text selection bugs P1 1.00 - -### Improve UI Events spec and tests 0.69 - -## Migrate UIEvent (and old Dom3Event) issues from Bugzilla to github P1 1.00 - -## Reduce spec issue count down to less than 10 P1 0.40 - -## Implement basic keyboard and mouse event tests in UIEvent repo P1 1.00 - -## Merge UIEvent tests into main W3C tests P2 0.00 - -### Improve code health - -## \[Stretch\] Plan for reducing at least one abstraction layer from input -events P4 0.10 - -## 2015 Q3 0.63 - -### Improve input latency and smoothness 0.55 - -## Ensure mean_input_event_latency time is under 12ms on Nexus 4 for 90% of -key_mobile_sites at least 90% of the time P1 0.80 - -## Get consensus on non-blocking event listener API P1 0.70 - -## Implement non-blocking event listener API behind a flag in M46 P1 0.10 - -## Approved UX design for unresponsive sites P1 0.60 - -## Ship hit-test-cache eliminating redundant hit tests in GestureTap and PEP -shadow DOM P1 1.00 - -## Drive investigation of regressions in touch latency UMA data P1 0.80 - -## File 30 concrete Hotlist-Jank bugs (eg. from "perf parties") P1 0.30 - -## Concrete plan for forced non-blocking event listeners P2 0.20 - -## Better measure and improve blink hit-test performance P2 0.20 - -## Reduce smoothness.pathological_mobile_sites.first_gesture_scroll_update on -the Nexus 4 by 25% P2 0.60 - -## STRETCH: Ship experiment for validity-rect based hit-test caching P3 0.00 - -## Expose hardware input timestamps to the web 0.85 - -## Concrete plan for input latency API on the web 0.30 - -### Improve interoperability between major browser engines 0.63 - -## Enable automated input testing on Chrome for W3C web-platform-tests P1 0.70 - -## Ship Event.isTrusted P1 1.00 - -## Ship viewport scroll behavior matching IE in M46 P1 0.90 - -## Ship spec-correct body scroll API behavior in M46 P1 0.40 - -## Share interoperability tracking plan with blink-dev and other vendors P1 0.60 - -## Triage all Hotlist-Interop bugs and find appropriate owners every week P1 -0.40 - -## Ship interoperable mouse-drag behavior across iframes P2 0.10 - -## Make Chromium reliably send MouseLeave events to blink P2 0.40 - -## Ship KeyboardEvent.code in M47 0.90 - -## Finish implementing KeyboardEvent.key behind a flag 0.75 - -### Eliminate key developer pain points around input 0.68 - -## Fix at least 100 Hotlist-Input-Dev bugs P1 1.00 - -## Ship history scroll state customization API in m46 P1 1.00 - -## Ship InputDevice and sourceDevice API in M46 P1 0.90 - -## Implement top-control hiding for full-page scrollable divs behind a flag P1 -0.20 - -## Reduce untriaged Cr-Blink-Input and Cr-Blink-Scroll bugs to ~0 P2 0.90 - -## File and investigate concrete bugs for accessibility issues around full-page -scrollable divs P4 - -## Allow "non-scrolling" apps to interact well with top controls (behind a flag) -P2 0.20 - -## Full-featured mouse support on Android (text selection, context menu's, -etc...) P2 - -## STRETCH: Dynamic support for interaction media queries P4 0.00 - -## STRETCH: Implement unified OSK viewport behavior between Android and CrOS for -M46 behind a flag P4 0.00 - -### Evolve touch platform UI 0.79 - -## Ship remaining M input features (stylus zoom, floating toolbars, perf test -for smart select) P1 1.00 - -## Ship unified touch text selection in M46 for web contents in Aura P1 1.00 - -## Ship unified touch text selection for native Aura UI P3 0.10 - -## Make check boxes and radio buttons touch friendly without depending on touch -adjustment P2 0.75 - -## (STRETCH) Fix cross-site navigation GestureNav issue P4 0.00 - -## Support trackpad pinch-zoom on CrOS P2 0.70 - -## (STRETCH) Show touch selection handles when scrolling on CrOS P4 0.00 - -### Continue PointerEvent API implementation 0.67 - -## Measure multi-touch pointer event dispatch overhead P1 0.90 - -## Fire pointer events for all mouse events P1 0.65 - -## Update MouseEvent (and so PointerEvent) to support fractional co-ordinates P2 -0.20 - -## Add chorded button transformation to mouse->pointer event generation logic -P2 0.20 - -## Start extending WebMouseEvent to become a pointer event API P1 0.70 - -## Add stylus support for Android P2 0.75 - -## Finish pointercancel support for touch P2 1.00 - -### Enable rich scroll effects 0.65 - -## Prototype snap-points implementation in M46 P1 0.50 - -## Enable scroll customization on UIWorker thread P1 0.50 - -## Enable main-thread scroll customization driven by touch input - behind a flag -P2 0.90 - -## Ship scroll latching for touch in M47 P2 1.00 - -## 2015 Q2 0.53 - -### Improve focus on reducing user pain around input on the web 0.60 - -## Reduce untriaged Cr-Blink-Input and Cr-Blink-Scroll bugs to 0 0.20 - -## Fix at least 80 Hotlist-Input-Dev bugs 1.00 - -### Improve touch web platform rationality 0.64 - -## Ship history scroll state customization API in m44 P1 0.60 - -## Implement sourceDevice.firesTouchevents for MouseEvent and TouchEvent behind -a flag in M44 P1 0.85 - -## Ship spec-correct body scroll API behavior in M45 P1 0.50 - -## Get consensus in w3c on InputDevice api spec P1 0.60 - -## Enable (and fix) mouseenter / mouseleave behavior for touch in M44 P1 1.00 - -## Ship async touchmove event coalescing in M44 P1 0.90 - -## Full-featured mouse support on Android (text selection, context menu's, -etc..., potentially behind a flag) P2 0.20 - -## Finish implementing UIEvent.sourceDevice for all scenarios in M45 (behind a -flag) P1 0.50 - -## Enable dynamic support for interaction media queries in X11 and Android in -M45 P3 0.00 - -## STRETCH: Ship InputDevice and sourceDevice API in M45 P4 0.00 - -### Rationalize viewport behvior 0.50 - -## Mature Virtual Viewport 0.80 - -## Ship viewport scroll behavior matching IE in M44. 0.60 - -## Allow "non-scrolling" apps to interact well with top controls (behind a flag) -0.00 - -## Implement unified OSK viewport behavior between Android and CrOS for M45 -behind a flag 0.00 - -### Improve input latency and smoothness 0.65 - -## Ensure mean_input_event_latency time is under 12ms on Nexus 4 for 80% of -key_mobile_sites at least 80% of the time P1 0.80 - -## Avoid sending touchmove's to Blink when unnecessary, with associated metrics -to track efficacy P3 0.20 - -## Reduce mean_input_event_latency on Nexus 4 for -sync_scroll.key_mobile_sites_smooth by 10%, with blame analysis for current -pathological cases P2 0.60 - -## VSync-aligned touch input behind a flag for Aura P3 0.20 - -## Drive investigation of regressions in touch latency UMA data P2 0.70 - -## Ship hit-test-cache in M45 eliminating redundant hit tests in GestureTap and -PEP shadow DOM scenarios P2 0.40 - -## Stop sending mousemove events during scroll on desktop and add relevant perf -tests in M44 P1 0.85 - -### Enable scroll-synchronized effects (behind a flag) 0.20 - -## Approved design for unified scrolling, with prototype for compositor -scrolling P1 0.30 - -## Implement scroll-snap-points for impl-thread scrolling behind a flag in M45 -P1 0.30 - -## Consensus within chrome team on initial design for sync-scroll jank -mitigation P1 0.20 - -## sync-scroll fully implemented (with jank mitigation on Android) behind a flag -in M45 P2 0.00 - -## Ship main-thread fractional scrolling in M44 P2 0.00 - -### Enable scroll customization (main thread only, behind a flag) 0.45 - -## Enable main-thread scroll customization driven by touch input - behind a flag -in M44 0.50 - -## Enable main-thread scroll customization driven by JS triggered scrolls - ship -behind a flag in M45 0.00 - -## Publish high quality demos, add telemetry perf tests 0.40 - -## STRETCH: Enable scroll customization on UIWorker thread 0.10 - -## STRETCH: Enable scroll customization driven by all input modalities - ship -behind a flag in M4? 0.00 - -### Begin Implementing pointer events API 0.60 - -## Fire pointer events for all touch input 1.00 - -## Add telemetry tests for multi-touch pointer event dispatch 0.00 - -## WG consensus on concrete plans for avoiding hit tests 0.00 - -## Support sending pointercancel on touch scroll/pinch 0.70 - -## Add devtools support for pointer event types 1.00 - -## Spec and implement new touch-action options behind a flag in M45 1.00 - -## (STRETCH) Fire pointer events for all mouse events 0.00 - -### Evolve touch platform UI 0.52 - -## Ship Android M text selection features (smart select, long press and drag, -floating action bar) P1 0.90 - -## Ship unified touch text selection in M44 for web contents in Aura P1 0.60 - -## Ship unified touch text selection in M45 for native Aura UI P2 0.10 - -## Make check boxes and radio buttons touch friendly without depending on touch -adjustment P2 0.00 - -## (STRETCH) Fix cross-site navigation GestureNav issue P4 - -## (STRETCH) Support trackpad pinch-zoom on CrOS P4
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/input-dev/input-objectives/2016-okrs/index.md b/chromium/docs/website/site/teams/input-dev/input-objectives/2016-okrs/index.md deleted file mode 100644 index d1730480c42..00000000000 --- a/chromium/docs/website/site/teams/input-dev/input-objectives/2016-okrs/index.md +++ /dev/null @@ -1,603 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/input-dev - - Input Team -- - /teams/input-dev/input-objectives - - Input Objectives -page_name: 2016-okrs -title: 2016 OKRs ---- - -## 2016 Q4 0.57 - -### Improve Input Performance 0.46 - -## Hold the line on input performance P1 0.70 - -## Intervene on the user’s behalf to improve scrolling performance -#wp-interventions P1 0.45 - -## Drive adoption of passive event listeners P2 0.20 - -## Improve Wheel Scroll Performance P2 0.40 - -## Improve timing of Event Signaling P3 0.50 - -## Find and Fix Low-Hanging Performance Issues P3 0.10 - -### Improve understanding of real-world input performance 0.21 - -## Prototype Input Progressive Web Metrics P1 0.20 - -## Improve automated input performance testing infrastructure P2 0.00 - -## Use RAPPOR to collect realtime input performance based on websites P2 0.50 - -## Measure Impact of Extensions on Input Performance P4 0.00 - -### Eliminate key developer pain points around input 0.56 - -## Layout-inert URL bar P1 1.00 - -## Provide the tools for it to be easier to deal with keyboard input P1 0.50 - -## Ship ViewportAPI P4 0.00 - -## Ship CSSOM Smooth Scroll P2 0.30 - -## document.rootScroller P2 0.50 - -## Implement overscroll-action API P2 0.80 - -## Implement ScrollCustomization API P2 0.30 - -## Drive the Adoption of history.scrollRestoration P4 0.00 - -## Touch Adjustment - Investigate and propose a solution P4 0.00 - -### Improve Interoperability of Input Events amongst major browser engines 0.86 - -## PointerEvents: Successful launch in M55 stable. P1 1.00 - -## PointerEvents: W3C Spec & Tests P2 1.00 - -## Test and address interoperability issues in the UI Event Spec P2 0.50 - -## Historical Points API P3 0.60 - -## Successfuly Ship auxclick in M55 P3 1.00 - -### Product Excellence 0.72 - -## Ship Material Design “overlay” scrollbars P1 0.70 - -## Be responsive to our users concerns P1 0.90 - -## Ship Scroll anchoring P1 1.00 - -## Enable input automation of individual pointers P1 0.70 - -## Using WebDriver for automated testing with input P1 0.30 - -## Quantify causes of Hung Renderer Crashes when it is completely idle P1 1.00 - -## Ignore clicks on recently-moved iframes (crbug.com/603193) P2 0.40 - -## PointerEvents: Reduce bug backlog for mouse & touch P2 0.85 - -## PointerEvents: Improve stylus support P2 0.50 - -## Ship unified OSK viewport behavior between Android and CrOS P4 0.00 - -### Improve Input Code Health 0.29 - -## Remove Artificial Layering in the Input Pipeline P2 0.60 - -## Consolidate pointer-type events in Chromium P2 0.00 - -## Overhaul Chrome Autoscroll P2 0.00 - -## Mojoifcation Architecture (Salamander) P3 0.00 - -## Make Keyboard scroll events to be gesture based events P4 0.00 - -## Use Proper Time Types for Events P2 0.80 - -## 2016 Q3 0.65 - -### Improve input performance 0.74 - -## No regressions in key metrics that last more than a single milestone P1 0.80 - -## Force touchstart event listeners to be passive during fling by M54 (behind -finch trial) P1 1.00 - -## Launch root scroller intervention behind a finch trial in M54 P1 1.00 - -## Ratchet up root scroller intervention to 100% before end of quarter P4 0.20 - -## Add intervention forcing event listeners to be passive for unresponsive main -thread (Finch trial in M54) P2 0.40 - -## Eliminate multiple queuing points for mouse and touch events and deliver most -up to date information P1 1.00 - -## Implement RAF aligned input on the main thread as an runtime enabled feature -P2 1.00 - -## Draft design doc for VSync aligned compositor input handling P1 1.00 - -## Implement VSync aligned input for compositor gesture scroll and pinch behind -finch trial P1 0.50 - -## Analyze VSync aligned compositor input performance metrics from finch trial -data P2 0.00 - -## Reduce the 99'th percentile of first gesture scroll update latency on Nexus 5 -by 30% on the best finch trial P2 1.00 - -## Find owners for 5 issues discovered through current input latency perf report -P3 0.00 - -## Ship scroll latching for touchpad behind a flag on all platforms P1 0.40 - -### Improve understanding of real-world input performance 0.63 - -## Author document precisely describing Progressive Web Metric for estimated -input latency P1 0.70 - -## Progressive Web Metric for estimated input latency landed in at least 1 form. -P2 0.80 - -## Share data on the realism / reproducibility tradeoff in telemetry input -tests. P2 0.00 - -## Run all of the current touch event latency reports on Chrome Trace Processor -P3 0.00 - -## Implement TBMv2 versions of touch input telemetry metrics P3 0.80 - -## Get touchpad scroll latency regressions as actionable as touch scroll -regressions P3 1.00 - -## Progressive Web Metric for time to interactive landed in at least 1 form. P2 -1.00 - -### Eliminate key developer pain points around input 0.45 - -## Complete Root Scrollers implementation behind a flag in M54 P1 0.80 - -## Create compelling demo showing benefit of RootScroller API and publish it -with devrel P3 0.50 - -## Ship API to expose visual viewport information to developers in M54 P1 0.60 - -## Investigate touch adjustment and find a solution to coordinate touch events -and click event P2 0.00 - -## Implement position:device-fixed behind a flag for M55 P4 0.00 - -## Ship non-layout affecting URL bar in M55 P2 0.00 - -## Draft spec on method for developers to control which virtual keyboard is -shown P2 0.70 - -## Ship API to control Chrome pull-to-refresh nav gesture behind a flag in M55 -P2 0.30 - -## \[Stretch\] Contribute history.scrollRestoration patch to Webkit P4 0.00 - -### Improve Interoperability of Input Events amongst major browser engines 0.78 - -## Ship non-primary button click event in M54 P2 0.90 - -## Update InputEvent implementation and design doc based on the currently -published specification by M54 P2 0.80 - -## Continue implementing the simple rich text editor using ContentEditable and -InputEvent P2 0.80 - -## Remove keyIdentifier from Blink in M54 P2 1.00 - -## Remove coordinates from TouchEvent \[WebKit\] P3 0.00 - -### Product Excellence 0.76 - -## Maintain Burndown of Hotlist-Input-Dev by closing 15 more issues than were -incoming rate P1 0.90 - -## End quarter with no P0,P1 issues that we started the quarter with P1 1.00 - -## Input-Dev PE FixIt Week in August P2 1.00 - -## Triage all new Blink>Input, Blink>Scroll issues within 7 days P1 1.00 - -## Scroll anchoring - shippable prototype and WICG spec with initial round of -feedback P1 0.65 - -## Conduct analysis and add necessary information to drive resolution to -Renderer Hung Crashes P1 0.40 - -## Improve touchpad user experience on Windows devices P3 0.00 - -## Ship unified OSK viewport behavior between Android and CrOS for M55 P2 0.60 - -### Improve Input Code Health 0.55 - -## Combine PlatformEvent and WebInputEvent P2 0.30 - -## WebMouseEvent becoming a pointer event API: design doc on an incremental impl -plan, land initial patches P3 1.00 - -## Improve TouchEventQueue sync with renderer P4 0.00 - -## Create & minimally plumb PlatformPointerEvent P4 0.20 - -## Refactor mouse code out of EventHandler & its submodules into -MouseEventManager P3 1.00 - -## Make PointerEvents the driver for mouse code in EventHandler P3 0.90 - -## Use better types for time for Events in blink P4 0.00 - -### PointerEvent API is ready to ship 0.91 - -## Analyze compatibility with Edge for 25 sites using pointer events 1.00 - -## Run a Finch trial with PointerEvents enabled P1 1.00 - -## Hackathon@MS P1 1.00 - -## Share implicit pointer capture compat data and our proposed plan with PEWG P1 -1.00 - -## Consensus in PEWG on the precise design Chrome should try shipping (covered -by open PRs) P2 1.00 - -## Drive committing fixes for 20 PEWG spec issues via participation in github -and regular calls P2 1.00 - -## Resolve all P0 and P1 launch blocking bugs P2 1.00 - -## W3C PointerEvent Tests: Complete automation through script injection P1 1.00 - -## W3C PointerEvent Tests: Run on all platforms with all pointer types, report -the outcome to PEWG P2 0.99 - -## W3C PointerEvent Tests: land 10 pull requests in github to improve test -coverage/quality P3 1.00 - -## PointerEvents fully automatable without the use of event sender P1 0.90 - -## Support fractional co-ordinates in PointerEvents, update Blink MouseEvent as -needed P3 0.10 - -## Stylus low level events: all events received in Blink for Mac, Windows and -CrOS P2 0.20 - -## Stylus properties: complete plumbing of tilt & pressure for Windows, CrOS, -Android and Mac P3 0.60 - -## Create a doc on consistent stylus interactions P4 0.00 - -## STRETCH: Turn pointer events on by default on trunk P4 1.00 - -### Drive adoption of passive event listeners 0.36 - -## Reduce fraction of touch events unnecessarily blocking scroll from 43% to 35% -P1 0.00 - -## Add ability to discover scroll blocking event handlers easy in devtools P2 -0.00 - -## 2016 Q2 0.66 - -### Improve scroll latency and smoothness 0.50 - -## No regressions in key metrics that last more than a single milestone P1 1.00 - -## Reach (data-driven) consensus on plan for touch scrolling intervention -(replacing touch ACK timeout) P1 0.70 - -## Ship initial conservative touch scrolling intervention via Finch by M53 P1 -0.20 - -## Make touchstart events during fling nonblocking by M53 (behind finch trial) -P2 0.00 - -## Reduce the 99'th percentile of first gesture scroll update latency on Nexus 5 -by 30% P2 0.20 - -## Add DevTools Support for Passive Event Listeners by M53 P2 0.90 - -## Fix 3 smooth scroll performance bugs by M53 P2 0.70 - -## Implement vsync aligned gestures in M53 P2 0.00 - -## Implement vsync aligned touch input in M53 \[Stretch\] P4 0.00 - -### Improve understanding of real-world input performance 0.73 - -## Measure efficiency gain and breakage caused by 5 possible touch scrolling -intervention approaches. P1 0.65 - -## Expose touch scroll latency information through devtools by M53 P1 1.00 - -## Add non-scrolling input performance metrics by M53 P2 1.00 - -## Improve on the current touch event latency reports P2 0.80 - -## Evaluate and Implement strategy for not calculating event path, and -dispatching event if no listeners P2 0.00 - -### Eliminate key developer pain points around input 0.35 - -## non-Document root scrollers implementation complete (behind a flag) in M52 P1 -0.30 - -## Ship non-layout-affecting top control resizes in M53 P3 0.00 - -## Ship API to expose visual viewport information to developers in M52 P2 0.70 - -## Ship unified OSK viewport behavior between Android and CrOS for M53 P3 0.00 - -## Draft spec on method for developers to control which virtual keyboard is -shown P2 0.00 - -## Design for ignoring clicks on iframes that have moved recently P2 0.60 - -## Implement position:device-fixed (behind a flag) as a way to attach elements -to the visual viewport P3 0.00 - -## Draft spec an API to control Chrome pull-to-refresh nav gesture behind a flag -P2 0.80 - -## Contribute history.scrollRestoration patch to Webkit P4 0.00 - -### Improve Interoperability of Input Events amongst major browser engines 0.81 - -## Implement InputEvent beforeinput (behind a flag) based on the provisional -specification in M52 P1 0.90 - -## Implement InputEvent input (behind a flag) based on the provisional -specification in M53 P1 0.80 - -## Make pointer event tests automatically run on Chrome on all platforms P1 0.80 - -## Add low level touch event API to Chromedriver in M53 P2 0.70 - -## Fix 8 Keyboard related interop bugs in backlog P2 0.60 - -## Make sure the order of composition events and input events matches spec in -M52 P2 0.90 - -## Contribute WebPlatform Tests for Editing beforeinput/input and composition -events P2 0.80 - -## Implement HTMLSelect ability to programmatically open in M52 behind a flag P4 -0.00 - -## Enable non-manual uievents and domevents webplatform tests P2 1.00 - -## Investigate in re-using Touch instances as Safari does P3 1.00 - -## Deprecate executing default action on Untrusted events P2 1.00 - -## Implement a simple rich text editor using ContentEditable and InputEvent P2 -0.60 - -### Product Excellence 0.85 - -## End quarter with no P0,P1's older than 90 days P1 0.80 - -## Triage all new Blink-Input, Blink-Scroll bugs within 7 days P1 1.00 - -## Scroll anchoring - shippable prototype and WICG spec with initial round of -feedback P1 0.50 - -## Increase burndown of issues. Close 10 more hotlist input dev bugs than the -incoming rate. P1 1.00 - -## Ship stricter user gestures for touch intervention in M52 P1 0.90 - -## All Hotlist=Input-Dev bugs with >= 15 stars have an OWNER P1 0.90 - -### Improve Input Code Health 0.55 - -## Refactor EditorCommand to use an enum class in M52 P2 1.00 - -## Propose and Implement removal of WebInputEvent <--> PlaformEvent -conversion P2 0.30 - -## Refactor IME keyboard event generation code to be common across all platforms -P4 0.00 - -## Improve situation around Blink scroll offset type P4 0.00 - -## Refactor main thread touch and wheel scrolling paths to use scroll -customization machinery P2 1.00 - -## Improve usage of time unit types for event timestamp P2 1.00 - -## Consensus on a plan for WebMouseEvent to become a pointer event API. P2 0.00 - -## Improve TouchEventQueue sync with renderer P2 0.00 - -## Design a modular EventHandler P2 1.00 - -## Update MouseEvent (and so PointerEvent) to support fractional co-ordinates. -P3 0.25 - -### PointerEvent API is feature-complete with major developers' concerns addressed. 0.80 - -## Fix redundant pointercancel bug with touch-action in M51. P0 0.90 - -## Enable developers’ testing of PointerEvent in M52, address community -feedback. P0 1.00 - -## Fix interaction issues between PE's explicit capture & TE's implicit capture. -P1 1.00 - -## Analyze compatibility with Edge for top 20 sites using pointer events P1 0.80 - -## Drive the open PEWG spec issues down from 21 to 10 via participation in -github and regular calls. P2 0.70 - -## Share implicit pointer capture compat data and our proposed plan with WG. P2 -0.25 - -## Improve test infrastructure & coverage P2 0.60 - -## Create a doc on consistent stylus interactions. P2 0.20 - -## Blink is receiving all stylus events on 2 platforms by EOQ P3 0.40 - -### Drive adoption of passive event listeners 0.51 - -## Reduce fraction of touch events unnecessarily blocking scroll from 47% to 30% -P0 0.15 - -## Publish usage guidance with assistance from DevRel in time for M51 stable -release P1 1.00 - -## Get 4 major partners to make their touch listeners passive P0 0.20 - -## Land the EventListenerOptions feature detect in Modernizr P2 1.00 - -## Passive touch listeners are promoted at Google I/O P2 1.00 - -## Add chrome://flags entry forcing all touch listeners (or all page-wide touch -listeners) to be passive P2 1.00 - -## Publish comparison of real world scroll start performance with passive -listeners and blocking listeners P3 1.00 - -## 2016 Q1 0.60 - -### Improve scroll latency and smoothness 0.65 - -## Ship Passive Event Listeners in M50 P0 0.90 - -## Land passive event listener interop tests in web-platform-test P2 0.00 - -## 4 important external partners actively experimenting with passive event -listeners P2 0.20 - -## Reach (data-driven) consensus on plan for touch scrolling intervention -(replacing touch ACK timeout) P2 0.20 - -## Get consensus on TouchEvents spec change for async touchmove and passive -listeners P2 1.00 - -## Land performance optimization for passive wheel listeners P3 1.00 - -### Improve understanding of real-world input performance 0.62 - -## Add non-scrolling input performance metrics P1 0.60 - -## Use slow reports to measure efficiency gain and breakage caused by possible -touch ack timeout approaches. P1 0.20 - -## Expose touch scroll latency information through devtools P1 0.20 - -## Quantify our objective of fixing scroll blocking P1 1.00 - -## Expose hardware input timestamps to the web P1 1.00 - -## Use slow reports to generate initial breakdown of where input handling logic -spends time P2 1.00 - -## Add touch scroll latency metric measuring until estimated vsync time -(STRETCH) P4 0.00 - -### Eliminate key developer pain points around input 0.61 - -## Fix at least 100 Hotlist-InputDev bugs P1 1.00 - -## Triage any new Blink-Input, Blink-Scroll bug within 7 days P1 1.00 - -## Solution to non-document root scroller problem landed behind a flag in M51 P1 -0.25 - -## Implement unified OSK viewport behavior between Android and CrOS for M50 -behind a flag P2 0.80 - -## Provide a way for developers to attach elements to the visual viewport P2 -0.20 - -## Land change to top control resizes to be more user friendly and Safari -compatible in M50 P2 0.25 - -## \[STRETCH\] Spec an API to control Chrome pull-to-refresh nav gesture behind -a flag P4 0.00 - -## Spec an API to expose visual viewport information to developers P2 0.50 - -### Improve input interoperability between major browser engines 0.65 - -## Enable automated input testing on Chrome for W3C web-platform-tests P1 0.35 - -## Ship KeyboardEvent.key P1 1.00 - -## Reduce UI Events spec bug count to under 25 P2 - -## Reach consensus across vendors on an updated plan for ScrollTopLeftInterop P4 -0.00 - -## Triage all Hotlist-Interop bugs and find appropriate owners every week P2 -0.70 - -## Land scroll restoration interop tests in web-platform-test P2 1.00 - -## Update HTMLSelectElement.open proposal and get buy in from other vendors. P3 -0.00 - -### PointerEvent API implementation is feature-complete 0.53 - -## Fix redundant pointercancel bug with touch-action. P1 0.65 - -## Enable developers’ testing of PointerEvent, address community feedback. P2 -0.20 - -## Implement explicit pointer capture support. P1 0.75 - -## Report to WG the outcome of all w3c tests except the ones for pointer -capture. P2 0.80 - -## Measure compatibility with Edge for top 20 sites using pointer events P2 0.10 - -## Share implicit pointer capture compat data and our proposed plan with WG. P3 -0.20 - -## Update MouseEvent (and so PointerEvent) to support fractional co-ordinates P3 -0.00 - -## Add pointer event handler tracking P3 1.00 - -### Improve support for text input via IMEs 0.40 - -## Implement and ship InputEvent P2 0.60 - -## Complete specification for input and beforeinput events P2 - -## Implement beforeInput (behind a flag) for Linux P2 0.30 - -## Contribute WebPlatform Tests for Editing beforeinput/input and composition -events P2 0.30 - -### Improve input code health 0.50 - -## Refactor MouseWheel scroll events to be gesture based events P2 1.00 - -## Extend WebMouseEvent to become a pointer event API P2 0.00 - -## Remove logic for touch scroll chaining P3 0.20 - -## Complete both outstanding viewport refactorings P3 0.00 - -## Refactor necessary code for input to actually send InputEvent from Editing -specification P2 0.40 - -## Refactor Event.dispatchEvent to return an enumeration P2 1.00
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/input-dev/input-objectives/2017-okrs/index.md b/chromium/docs/website/site/teams/input-dev/input-objectives/2017-okrs/index.md deleted file mode 100644 index 0dcfc74a077..00000000000 --- a/chromium/docs/website/site/teams/input-dev/input-objectives/2017-okrs/index.md +++ /dev/null @@ -1,965 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/input-dev - - Input Team -- - /teams/input-dev/input-objectives - - Input Objectives -page_name: 2017-okrs -title: 2017 OKRS ---- - -## ==2017 Q4== - -**Eventing Sub-team** - -### Improve Smoothness and Predictability of Events 0.25 - -### Resampled Events P1 0.30 - -### Early ACK touch events when we have a touch-action but all passive event -listeners P3 0.20 - -### Predictive Points P3 0.10 - -### Add Richness to Web Platform 0.63 - -### Low latency input mode for main screen canvas P1 1.00 - -### Prototype input events dispatched to Worker P1 0.15 - -### Spec for input for Workers P4 0.00 - -### Finalize Simple User Activation model P1 0.50 - -### Expose fractional coordinates for mouse P1 1.00 - -### Ship scroll options in focus P2 1.00 - -### Input Mode P2 0.75 - -### Pointerevent Spec V2: pass 10 failing tests P4 0.00 - -### InputDeviceCapabilities is Chrome-only P3 0.50 - -### Autofill focus spec P3 0.10 - -### Mouse Events forward/back buttons P3 0.80 - -### Get drag and drop on Android to work within a page P3 0.60 - -### Clarify screenX/Y and movementX/Y definitions P4 0.00 - -### Performance 0.86 - -### Hold the line on Input Performance P1 1.00 - -### Push other parties to fix the performance bugs P1 0.70 - -### Updating the existing metrics in UKM P2 1.00 - -### UKM Dashboard for input metrics or equivalent P2 1.00 - -### Rappor analysis and scripts P4 0.00 - -### Product Excellence 0.65 - -### Be responsive to our users P1 0.50 - -### Fix 8 regression bugs in Blink>Input P2 1.00 - -### Fix 6 starred > 10 bugs P2 1.00 - -### Touch Adjustment crbug.com/625198 P3 0.40 - -### Fix ARC++ trackpad events for the web. P3 0.50 - -### Remove legacy Touch detection P3 0.50 - -### Fix ordering of focus events P4 0.10 - -### Code Health 0.78 - -### Mojo Input P1 0.80 - -### Transform all WebTouchEvents to WebPointerEvent in Blink P2 0.90 - -### Support mus team in shiping new input routing mechanism. P2 1.00 - -### Latency info cleanup P2 0.40 - -### Nuke EventDispatchMediator P3 1.00 - -### Get rid of null initialization of UGIs P4 0.00 - -### Remove Legacy Touch Event Queue P4 1.00 - -## Scrolling Sub-team - -### Performance 0.87 - -Wheel scroll latching and async wheel events P1 0.80 - -Implement phase information from ChromeOS P2 1.00 - -### Improve Interop 1.00 - -Publish “spec” how viewports and APIs work/should work 1.00 - -### Add Richness to Web Platform 0.51 - -Plan a path to shipping for document.rootScroller P1 0.70 - -Produce a draft spec for document.rootScroller P4 0.00 - -Make document.rootScroller work with OOPIF P3 0.40 - -Propose “resize-mode” API for OSK P4 0.00 - -Scroll Customization P3 0.35 - -### Code Health 0.60 - -Remove duplication between frame and layer scrolling P1 0.70 - -Browser side fling P2 0.40 - -Use scroll gestures for keyboard scrolling P2 0.20 - -Correct telemetry gestures P2 1.00 - -### Product Excellence 0.48 - -Windows precision trackpad implemented behind a flag P1 0.40 - -Enable subpixel precision scrolling in Blink P4 0.00 - -Scroll boundary behaviour P2 1.00 - -Close out remaining overlay scrollbar polish issues P3 0.30 - -Fix important/curated bugs P3 0.20 - -## ==2017 Q3== - -**Eventing Sub-team** - -### Improve Smoothness and Predictability of Events 0.63 - -### Align Events with Appropriate Lifecycle P2 0.80 - -### Resample input events on main thread and compositor P2 0.20 - -### Dispatch Mouse Events when hover changes due to DOM modifications P2 1.00 - -### Predicted points P3 0.20 - -### Make hover states and boundary events consistent across all the cases P4 -1.00 - -### Add Richness to Web Platform 0.40 - -### Implement a simple user activation model that is good for cross-browser -implementation P1 0.45 - -### Define input events for Workers P1 0.40 - -### Support low latency stylus P1 0.20 - -### Move Pointer Event spec to CR P3 0.60 - -### Add Richness to Editing events P3 0.70 - -### Enable Input Automation in WPT P4 0.50 - -### Performance 0.86 - -### Hold the line on Input Performance P1 1.00 - -### Rappor and UKM metrics P1 0.50 - -### Ship Direct Manipulation Stylus on Windows P1 1.00 - -### Analyze 120Hz Hardware P2 1.00 - -### Product Excellence 0.52 - -### Be Responsive to our Users P1 0.80 - -### Solve non-consistent target issues with Touch Adjustment P1 0.20 - -### Take over ownership of Blink>Input>PointerLock issues P2 0.60 - -### Mus Input Routing P2 0.50 - -### Code Health 0.37 - -### Complete mojofication of input pipeline P1 0.70 - -### Complete switch to pointer events input flow in Blink Code P1 0.20 - -### Latency Info Cleanup P2 0.20 - -### Fix 5 low-hanging input-dev issues with Hotlist-CodeHealth P3 0.10 - -### Fractional Mouse Coordinates P3 0.60 - -## Scrolling Sub-team - -### Add Richness to Web Platform 0.63 - -Smooth ViewportAPI/Inert Viewport Launch P1 0.90 - -Prepare rootScroller for standardization P1 0.30 - -Unify ChromeOS and Android On-Screen Keyboard P2 0.00 - -Ship ScrollBoundaryBehavior P2 1.00 - -Ensure ScrollLeft/Top interop launch is a success P2 1.00 - -### Performance 0.60 - -Wheel scroll latching and async wheel events P1 0.60 - -### Improve Scrolling UX 0.60 - -Windows Precision Touchpad Support P1 0.40 - -Support Overlay Scrollbar Launch P1 0.80 - -### Improve Product Polish 0.40 - -Fix 6 important/long-standing user or developer-facing bugs P3 0.40 - -### Improve Code-Health 0.22 - -Progress Scroll Unification P2 0.00 - -Fling on Browser Side P2 0.50 - -Keyboard Gesture Scrolling \[stretch\] P4 0.00 - -**Threaded Rendering Sub-team** - -### Enable rich custom effects 0.49 - -Finish implementation of PaintWorklet on main thread P1 0.90 - -Finish implementation of Snap Points P1 0.10 - -Start a origin trial Main-Thread Scroll Customization P3 0.40 - -### Make compositing excellent 0.53 - -Promote opaque fixed/sticky position elements into composited layers. -#wp-performance P1 0.00 - -Finish touch action implementation && measure performance impact P1 0.50 - -Close 25 non-feature bugs. P2 1.00 - -Finish the experiment of not compositing small scrollers P2 1.00 - -Analyze main thread scrolling reasons P4 0.00 - -Finish upstreaming position:sticky tests to WPT P2 0.80 - -Wheel listener rects P4 0.00 - -Reduce number of composited layers created for correctness. P1 0.60 - -### Improve metrics and code health 0.61 - -Fix regression bugs caused by composited border-radius scrolling P1 0.90 - -Identify / define metrics to monitor continued threaded rendering performance -excellence. P4 0.00 - -Improve documentation of the animation code P2 1.00 - -Measure metrics without compositing thread. P4 0.00 - -Remove all uses of layer ids or layer references in cc/animations P1 0.50 - -Progress or regression of bug open/close rate is visible to the team. P2 0.00 - -New issues are triaged within seven days. P3 0.90 - -### Enable performance isolated effects on the web 0.44 - -Animation Worklet - Draft specification for API #wp-ergonomics P1 0.70 - -AnimationWorklet - Land Milestone 1 P1 0.80 - -Prototype raster-inducing scroll (https://crbug.com/715106) P1 0.20 - -AnimationWorklet - Land Milestone 2 P2 0.20 - -Animation Worklet - Schedule and give animations a deadline to avoid janking -compositor thread. #wp-ergonomics #wp-performance P2 0.10 - -\[stretch\] Ship Animation Worklet origin trial P4 0.00 - -\[stretch\] Ship PaintWorklet off thread P4 0.00 - -## ==2017 Q2== - -## Eventing Related 0.52 - -### Improve Smoothness and Predictability of Events 0.38 - -## Align Events with Appropriate Lifecycle P1 0.65\[0.3\] Ship rAF aligned mouse -events \[0.4\] Address regressions with vsync aligned gestures 100 \[0.3\] Ship -Vsync aligned gestures 100 - -## Teach scheduler about non-blocking input events P1 0.10\[0.5\] Simplify -notification of input events to render scheduler \[0.5\] Notify scheduler to -adjust user model based on non-blocking event - -## \[Punted\] Resample input events on main thread and compositor P2 eirage@ -will take over. \[0.3\] Draft design doc for resampling algorithm and matrix -\[0.3\] Implement resampling behind a flag \[0.2\] Launch Finch Trial and -analysis data \[0.2\] Ship input resampling - -### Product Excellence 0.67 - -## Be Responsive to our Users P1 0.85\[0.5\] Triage all new issues within 7 days -\[0.2\] Triage all open issues that have not been modified in 180 days \[0.3\] -Fix 7 top starred > 10 stars issues - -## Drive down regression bugs P1 0.70Close 33% (9 bugs) of our open regressions. - -## Solve non-consistent target issues with Touch Adjustment P1 0.40\[0.1\] Write -touch/pointer tests to expose interop issues \[0.3\] Propose a solution and -draft design doc \[0.4\] Implement behind a flag \[0.2\] Ship new Touch -Adjustment <https://crbug.com/625198> - -## Take over ownership of IO>PointerLock issues P2 0.50\[0.5\] Fix 5 -IO>PointerLock issues \[0.5\] Triage and prioritize all issues. - -## Study & design a sensible hover/active solution for touch+mouse P2 -1.00\[0.4\] Write a doc describing and comparing hover behavior on major -browsers. \[0.4\] Propose a design based on (possibly) decoupled active & hover -states (no new APIs) \[0.2\] Implement a prototype based on the design - -## Fix Chrome’s non-standard/interop APIs related to input. P2 -0.60<https://bugs.chromium.org/p/chromium/issues/list?can=1&q=summary%3Astandardize%2Cremove+Hotlist%3DInput-Dev+opened<2017-03-31+modified>2017-03-31+reporter%3Afoolip%2Clunalu> -\[1.0\] Finalize standardize/remove decision for 5 non-standard web APIs. - -### Add Richness to Web Platform 0.42 - -## Experiment with a simple user activation indicator that is good for -cross-browser implementation P1 0.50\[0.3\] Prototype a simple bit-per-frame -user activation and perform lab-test. -[crbug.com/696617](http://crbug.com/696617) \[0.2\] Propose a detailed design -for implementation. \[0.3\] Implement the design behind a flag, covering all -user activation clients. \[0.2\] Experimentally switch away from current -UserGestureIndicator in M59/60 beta. \[stretch\] \[PUNTED\] Publish a report on -observed regressions and next steps. - -## Define input events for animation worklet P1 0.20\[0.3\] Create a -polyfill-based touch-drag prototype to aid design discussion. \[0.4\] Design doc -on event model for animation worklet, reach consensus on final design goals. -\[0.3\] \[PUNTED\] Complete an experimental plumbing to route input events to a -worker thread. - -## Enable Input Automation APIs in WPT P1 0.20\[0.3\] \[PUNTED\] Add key -injection APIs in GPU Benchmarking (blocked on -[crbug.com/722921](http://crbug.com/722921)) \[0.3\] Add input injecting input -API with consensus from other vendors \[0.2\] Plumb the input injecting API to -enable the manual tests to run on Chrome bots \[0.2\] Update at least 3 manual -tests to use the new input injection API - -## Expose fractional co-ordinates for PointerEvents of mouse type P2 0.00\[0.2\] -Plumb fractional mouse co-ordinates in Windows (browser side) \[0.1\] Plumb -fractional mouse co-ordinates in Android (browser side) \[0.1\] Plumb fractional -mouse co-ordinates in Mac (browser side) \[0.2\] Plumb fractional mouse -co-ordinates in Linux and ChromeOS (browser side) \[0.3\] Remove WebMouseEvent -coord truncation, fix regressions. \[0.1\] Expose fractional coordinates for -PointerEvents of mouse type (blink side) - -## Make Pointer Events spec & tests ready for L2 P2 0.70\[0.3\] Drive solving -all of the 4 current L2 Blocking issues. \[0.7\] Resolve all of the current 29 -tests with less than 2 passing browsers from failure list. - -## Champion Auxclick P3 0.80\[0.7\] Merge auxclick spec into UI Event spec -\[0.3\] Get at least Edge or Safari to implement auxclick - -## Predicted points API P3 1.00\[0.7\] Put together challenges and different -solutions we had for this API in a doc \[0.3\] \[PUNTED\] Put a prototype -together in Chrome to demonstrate this feature - -## Drive TouchEvents-to-PointerEvents switchover for Google apps P3 -1.00#internal \[0.5\] \[PUNTED\] Support Google Maps API switchover to -PointerEvents. \[0.5\] Make Google Maps usable with Android mouse. - -## Keyboard Input Mode Consensus P4 \[0.5\] Continue with driving consensus in a -design internally \[0.5\] Publish design externally - -## Add Richness to Editing events P3 0.60\[0.3\] Make sure InputEvent was -shipped without substantial issue \[0.4\] Rewrite all layout tests into WPT -through Input Automation API \[0.3\] Follow and fix incoming bugs - -## \[PUNTED\] Synthetic pointer actions in WebDriver P4 \[0.3\] Design doc for -exposing the synthetic pointer actions in webdriver \[0.4\] Implementation of -the synthetic pointer actions in webdriver \[0.3\] Exposing the functionality in -WebDriver Js - -### Code Health 0.71 - -## Target input events to either the RenderFrame or RenderView not both P1 -1.00Make input event targeting on Chrome IPC consistent. 21 messages are sent to -the RenderFrame, and the remaining goto the RenderView on two different IPC -channel identifiers. - -## Point person for MUS hit test API P1 0.70\[0.4\] Propose and agree on Mojo -Interface \[0.6\] Implementing the interface - -## Move input messages to be mojo based P2 0.70\[0.4\] Define a mojo -InputHandler interface to the compositor thread and convert existing messages -\[0.4\] Define a mojo InputHandlerHost interface and convert existing messages -\[0.2\] Cleanup existing layering not necessary - -## Complete switch to pointer events input flow in Blink code P2 0.45\[0.4\] -Replace all occurrences of WebTouchEvent in Blink with unpacked WebPointerEvent. -\[0.3\] Move grouping of touch events to the end of pipeline using raf signal -\[0.2\] Align WebMouseEvent attributes with WebPointerEvent \[0.1\] Merge -WebMouseEvent into WebPointerEvent - -## Using WM_POINTER for all input types on Windows 8+ P2 0.40\[0.5\] Listen to -WM_POINTER to handle all mouse events to replace WM_MOUSE on Windows 8+ \[0.5\] -Listen to WM_POINTER to handle all touch events to replace WM_TOUCH on Windows -8+ - -### Performance 0.42 - -## Hold the line on input performance P1 0.50No regressions in key metrics that -last a milestone and monitor usage of touch-action - -## Add richer set of metrics to input pipeline P1 0.30\[0.3\] Add -Event.Latency.Scroll(Begin|Update).(Touch|Wheel).TimeToScrollUpdateSwapBegin2 to -UKM \[0.2\] Do the initial round of analysis on RAPPOR data gathered last -quarter for input metrics and file at least 2 bugs for slow sites found via -RAPPOR \[0.2\] Prepare a document explaining a flow for analyzing UKM data from -dashboard or raw data \[0.3\] Compare the Rappor and UKM and decide what we will -be doing with RAPPOR metrics \[Towards the end of the quarter gathered data was -deleted due to mistakenly gathering some reports in incognito mode. We will have -more data next quarter for analyzing.) - -## Quantify accuracy of Expected Queueing Time metric P2 0.50Measure how closely -actual queueing time correlates to expected queueing time. End-of-quarter update -- patch up here: <https://codereview.chromium.org/2954473002/>. - -## \[PUNTED\] EGL frame timestamps for input latency metrics P4 \[0.7\] Utilize -Android O frame-timing data \[0.3\] Compare the new metric with the old -TimeToScrollUpdateSwapBegin2 metrics and write a doc explaining the results - -## Scrolling Related 0.58 - -### Add Richness to Web Platform 0.60 - -## document.rootScroller P1 0.50https://crbug.com/505516 \[0.5\] Finish an -implementation that’s usable for AMP case \[0.2\] Preliminary spec describing -the new implementation \[0.2\] \[PUNTED to 61\] Ship origin trial in M60 \[0.1\] -Create example demos - -## scroll-boundary-behavior P1 0.50\[0.4\] Implement scroll-boundary-behavior -for viewport (i.e. to prevent navigation) in M60 behind a flag \[0.4\] Implement -scroll-boundary-behavior for inner scrollers (i.e., chaining) on both cc and -main thread \[0.2\] Ship the final API in M61 - -## \[PUNTED\] Unify On-Screen Keyboard Resize Behavior \[Stretch\] P4 -https://crbug.com/404315 \[0.2\] Determine if existing implementation is -sufficiently flexible to support app-like scenarios \[0.3\] Propose any missing -APIs needed for PWA like scenarios \[0.3\] Create GitHub explainer and demos -(similar to URL bar resizing) \[0.2\] Fully implemented by M61 feature freeze - -## Rationalize viewport coordinates on the web P2 1.00Note: Added at mid quarter -check-in \[0.3\] Create WPT suite for visual viewport API \[0.2\] Ship -ViewportAPI in M61 (<https://www.chromestatus.com/feature/5737866978131968>) -\[0.5\] Ship inert visual viewport in M61 - -### Improve Scrolling UX 0.74 - -## Ensure Overlay Scrollbar launch is Successful P1 -0.90<https://crbug.com/307091> \[0.3\] Land in M59 \[0.4\] Address all P0/P1 -implementation issues \[0.3\] All polish items in the spreadsheet are addressed - -## Supoort Windows precision touchpad P3 0.10\[0.6\] Use Windows API to mark -events coming from a precision touchpad \[0.4\] Support gesture navigation on -windows touchpad crbug.com/647140 - -### Performance 0.60 - -## Touchpad Scroll latching P1 0.60<https://crbug.com/526463> \[0.3\] Latching -logic should work for OOPIFs \[0.3\] Improve test coverage: unittests of all the -classes with the flag must cover both latching and propagation cases, and no -flaky layouttests \[0.2\] Enable the flag on the waterfall by default and -address any regression bugs. \[0.2\] \[Punted to 61\] Ship a finch trial in M60 - -## Async wheel events P1 0.60<https://crbug.com/706175> #WP-Alignment \[0.3\] -\[Punted to 61\] Finish the implementation behind a flag in M60 \[0.2\] Design -doc for wheel scroll latching and async wheel events \[0.3\] Enable the flag on -the waterfall by default and address any regression bugs. \[0.2\] Ship a finch -trial by EOQ - -## \[Punted\] MouseWheel listeners on scrollers out of the scroll chain -shouldn’t block scrolling P4 <https://crbug.com/700075> \[0.2\] Add metrics to -have an approximation of cases that scrolls are blocked on listeners that are -not part of the scroll chain. \[0.6\] Implement tracking the wheel event per -individual scroller by EOQ \[0.2\] Ship a finch trial - -### Improve Code Health 0.38 - -## Unify main and compositor scrolling paths P2 0.90<https://crbug.com/476553> -\[0.4\] Create design doc outlining a path to scroll unification between main -and impl threads \[0.2\] Create detailed implementation plan/design doc for -reraster-on-scroll \[0.4\] Share with relevant teams, iterate and come to -consensus shared vision - -## Use scroll gestures for all user scrolls P2 0.00\[0.5\] \[Punted\] Keyboard -Gesture Scrolling \[0.2\] Autoscroll \[0.3\] Scrollbar Gesture Scrolling - -## Unify Mac scrollbars P3 0.00\[0.4\] Remove scrollbar paint timer \[0.4\] -Decouple ScrollAnimatorMac from painting \[0.2\] \[Stretch\] Paint Mac -Scrollbars from WebThemeEngine - -## Decouple Scrollbars from ScrollableAreas in Blink P3 -0.50<https://crbug.com/661236> \[0.6\] Move all scrollbar generation/management -code out of ScrollableArea \[0.2\] Move scrollbar creation for main frame to -happen in RootFrameViewport \[0.2\] Fix blocked issues -<https://crbug.com/456861>, <https://crbug.com/531603> - -### Improve threaded rendering code health - -## \[Punted\] LTHI Scroll logic refactoring P2 \[0.75\] Design doc \[Punted\] -\[0.25\] An internal scroll manager that isolates scrolling logics in LTHI -\[Punted\] Bokan@ has a new idea, so the unifying work does not make sense -anymore. - -## Threaded Rendering Related 0.53 - -### Enable rich scroll effects 0.60 - -## Finish position:sticky P1 0.80#wp-ergonomics #wp-predictability \[0.6\] fix -all current P2+ bugs (5 bugs) \[0.4\] Upstream web platform tests for spec’d -testable exposed behavior - -## Scroll Snap Points P1 0.20Land the spec-matching version (behind flag) - -## CSS OM Smooth Scroll P2 1.00Ship CSSOM View smooth scroll API (enabled by -default) - -## \[Punted\] Scroll-linked animations polyfill P3 #wp-ergonomics wait for the -existing (external) editors to have something ready for review, then look at an -implementation and/or polyfill strategy at that point \[0.6\] Implement JS -polyfill \[0.3\] Implement CSS polyfill \[0.1\] Publish on shared team github -\[PUNTED\]. Waiting for Mozilla people to push this. - -### Enable performance isolated effects on the web (AnimationWorklet) 0.46 - -## Implement AnimationWorklet M1 features behind flag P1 0.50\[0.2\] Implement -blink::WorkletAnimation (single timeline, multiple effects) \[0.2\] Implement -Animator and Animator definition in Worklet scope \[0.2\] Implement -cc::WorkletAnimationPlayer \[0.1\] Plumb mutation signal and current time to -worklet \[0.1\] Plumb WorkletAnimation blink => compositor => worklet -\[0.1\] Proxy Keyframe effects in Worklet scope and plumb local times worklet -=> compositor \[0.1\] Get required changes to web-animation spec upstreamed -\[stretch\] Implement ScrollTimeline in blink \[stretch\] Run animation worklet -on dedicated thread Result: progress made on first 4 items. Will continue -working on in Q3. - -## \[Punted\] Schedule animation calls at commit deadline P2 This needs to be -rolled into the animation worklet plan as the new API and integration with -animations will change how we schedule updates. - -## \[Stretch\] Ship origin trial P3 0.30- amp or fb as potential clients Result: -flackr@ implemented a polyfil that can be used to experiment with API while -implementation is not complete. Blocked on majidvp@ updating the documentation -and making contacts. - -### Make compositing excellent 0.58 - -## Resolve at least as many Hotlist-ThreadedRendering bugs as incoming P1 1.00 - -## Promotion of opaque fixed (and sticky) position elements P1 0.20\[0.6\] -Resolve consistent scroll position between composited and non composited -elements \[0.4\] Enable by default, 4% more composited scrolls - -## Enable compositing border-radius with tiled masks P1 0.90\[0.2\] Investigate -if mask tiling can be disabled on AA bugs - Done \[0.5\] Implement demoting -logic - Done \[0.2\] Disable mask tiling on bugs and rare cases (AA, filters) - -Done \[0.1\] Stretch - Antialising bug (both RPDQ and content quads, but on RPDQ -it’ll be a regression) - not urgent if tiling is disabled. - Done Discuss with -paint team on whether blocked by a pre-existing paint bug. - Done Landing CLs -that enable the flag. - Reverted due to regression. - -## Draft plan shared with team for raster inducing animations P2 Punted for now. - -## Prototype compositor side hit testing (shared with paint team) P2 -0.70Documented plan for touch action. Needs more work on browser side when -handling the white-listed touch actions. - -## Triage - track incoming vs redirected / fixed / closed P2 0.00The app-engine -tool path looks a lot longer than it should. - -## Enable reporting subpixel scroll offsets back to blink P3 0.00- Fix issue -456622 - bokan@ can provide consulting - -### Identify opportunities / improve understanding of threaded rendering limitations in the wild 0.46 - -## Metrics about interactions with scrollers P2 0.80\[0.5\] Land UMA metrics -regarding size of scroller on page load and on scroll \[0.3\] Use results from -the metrics to launch a Finch trial to see the differences w, w/o compositing -small scrollers \[0.2\] Document and plan for the next step - -## Analyze CPU/GPU cost due to layer explosion P3 0.50\[0.3\] Use current UMA -metrics to analyze CPU cost \[0.4\] Land new metrics regarding GPU memory cost -due to layer creation \[0.3\] Analyze GPU cost - -## Analyze main thread scrolling reasons; from uma data added in previous -quarter P3 0.20\[0.2\] Resume the non composited main thread scrolling reasons -recording \[0.4\] Identify and resolve top remaining reason after opaque fixed / -sticky promotion. \[0.2\] Work on the case that transform with non-integer -offset cases \[0.2\] Work on the case that translucent element without text - -## Save composited filter result (18% pages have filter according to CSS -popularity) P3 0.30\[0.4\] How often do we have a composited filter, land UMA -metrics \[0.3\] Timing metrics \[0.3\] Stretch - Figure out a way to apply the -animated-blur machinery in chromium to improve the perf - -## Perf party P3 0.60\[0.4\] File 3 bugs. \[0.4\] Identify resolution of those -bugs. \[0.2\] Fix them. - -## Publish three UI pattern blog posts P3 0.00\[0.25\] animated blur \[0.25\] -directional shadow \[0.5\] hero transition in scrolling content (google music) - -### Improve threaded rendering code health - -## \[Punted\] LTHI Scroll logic refactoring P2 \[0.75\] Design doc \[Punted\] -\[0.25\] An internal scroll manager that isolates scrolling logics in LTHI -\[Punted\] Bokan@ has a new idea, so the unifying work does not make sense -anymore. - -## ==2017 Q1== - -## Eventing Related 0.70 - -### Improve Smoothness and Predictability of Input Events 0.65 - -Align Events with Appropriate Lifecycle P1 0.50#wp-performance 0.3 Interpolate -touchmove events on the main thread 0.2 Analyze rAF Aligned Touch finch trial -data 0.2 Ship rAF Aligned Touch Input 0.3 Compositor vsync aligned input finch -trial - -Intervene to improve scroll performance P2 1.00#wp-alignment #wp-performance 0.2 -- Decrease fraction of page views which prevent default touch events without -having a touch-action from 0.66 to 0.57% 0.8 - \[PUNTED\] Land and evaluate -finch trial forcing event listeners to be passive if the main thread is -unresponsive. (<https://crbug.com/599609>) - -Hold the line on input performance P2 0.85#wp-performance 0.7 No regressions in -key metrics that last a milestone 0.3 Monitor usage of touch-action - -Measure Latency of Keyboard Input P2 0.50Report Latency of Keyboard Input via -UMA Did a bunch of cleanup making this easier. Patch in progress here: -https://codereview.chromium.org/2756893002/ - -Handle Input Events as soon as possible P3 0.50#wp-performance 0.5 Place all non -event based IPC messages in the main thread event queue so we don’t have to rely -on message pumps to process input events 0.5 Coordinate with the blink scheduler -so it can ask the main thread event queue if it has work to do. - -### Add Richness to Web Platform 0.78 - -Ship Coalesced Points API P1 1.00#wp-ergonomics 0.5 Ship Coalesced Points API in -M58 0.5 Adding at least 3 tests in WPT for different aspect of the feature - -Drive Pointer Events L2 to Recommendation P1 0.80#wp-ergonomics 0.3/0.5 Drive -solving all the new L2 Blocking issues; end quarter with zero issues 0.5/0.5 -Prepare the full test result for all vendors and the explainer doc for the -failures - -Make mouse a first-class event in Android P1 0.750.1/0.1 Address major user -concerns around mouse rerouting by M56 release. <https://crbug.com/675339> -0.3/0.3 Fix text selection triggering with mouse. <https://crbug.com/666060> -0.0/0.2 Enable page zoom through mouse. <https://crbug.com/681578> 0.2/0.2 -Update old-style mouse click code. <https://crbug.com/669115> ---/0.2 \[PUNTED\] -Unify mouse & gesture triggered text selection in Android. - -Input Automation for testing P2 0.40#wp-predictability 0.5 Get consensus on -input automation APIs 0.3 Implement the plumbing to use the input automation in -wpt serve 0.2 Make all Pointer Event tests to make use of this API - -Round out stylus support on all platforms P2 0.900.3 Ship PointerEvent.twist and -.tangential on Mac <https://crbug.com/679794> 0.1 Complete Wacom Intuos Pro -support for Mac <https://crbug.com/649520> 0.4 Switch Windows (>= 8) -low-level path to use WM_POINTER <https://crbug.com/367113> 0.2 Add missing -plumbing for stylus properties in Windows <https://crbug.com/526153> - -Add Richness to Editing events P2 0.70#wp-ergonomics 0.3 Get a consensus -internally how to ship beforeinput/input 0.4 Finish cleanup and remaining bugs -0.3 Intent to Ship - -Drive Adoption of auxclick P3 1.00#wp-predictability 0.5 Auxclick is implemented -by at least one other vendor 0.5 Click event is no longer fired for middle -button by at least one other vendor - -Consensus on inputmode design P3 0.30#wp-fizz 0.5 Write up options and -distribute and build consensus 0.5 Build consensus in external WICG; -<https://crbug.com/248482> - -### Product Excellence 0.78 - -Be responsive to our users P1 0.90Triage all new Input, Scroll issues within 7 -days Triage all Hotlist-Input-Dev > 10 starred issues every 90 days to ensure -we drive resolutions. Fix 5 top starred issues <https://goo.gl/fMt74P> -specifically <https://crbug.com/161464>, <https://crbug.com/25503>, - -Fix touch interactions hiccups with PointerEvent P1 1.000.5/0.5 Fix multi-finger -panning with touch-action <https://crbug.com/632525> 0.4/0.4 Disable touch slop -suppression for touch-action:none. <https://crbug.com/593061> 0.1/0.1 Fix CrOS -device issues with touch-like stylus. <https://crbug.com/682144>, -<https://crbug.com/691310> - -Address misc implementation issues with PointerEvents P2 1.000.3/0.3 Video -default event handler problem with PointerEvents. <https://crbug.com/677900> -0.3/0.3 PointerEvent should set movementX & movementY. -<https://crbug.com/678258> 0.4/0.4 Fix 5 other chromium bugs with PointerEvents. - -Ignore clicks on recently-moved iframes (crbug.com/603193) P2 0.000.4 Add tests -and fix bugs in prototype 0.4 Land prototype behind a flag 0.2 Extend prototype -to handle OOPIF - -Address long standing mouse event quirks P3 0.60#wp-predictability 0.5 -Consistent behavior of zero-movement mousemoves plus hover states. -<https://crbug.com/488886> 0.5 MouseLeave on all platforms working correctly. -<https://crbug.com/450631> - -### Code Health and Future Design 0.47 - -Simplify event processing P2 0.20#wp-architecture 0.5 Remove touchmove -throttling in the touch event queue 0.5 Remove fling curve generation from the -main thread - -Continue removing artificial layering in event pipeline P2 0.80#wp-architecture -0.6 Remove PlatformMouseEvent and PlatformTouchEvent 0.4 Cleanup -PageWidgetEventDelegate - -Improve Blink event bookkeeping P2 0.500.0/0.4 Event-handling states on frame vs -page. <https://crbug.com/449649> 0.3/0.3 InputRouter event queue cleanup: -<https://crbug.com/600773>, <https://crbug.com/601068> 0.2/0.3 Design doc on -PointerEvent driven event handling in Blink: <https://crbug.com/625841> - -Make coordinates consistent for all Web pointer-type events P3 0.700.3/0.4 Make -WebMouseEvent coordinates fractional <https://crbug.com/456625>. 0.4/0.4 Remove -refs to deprecated location data in WebMouseEvent <https://crbug.com/507787>. -0.0/0.2 Normalize coordinate systems between WebMouseEvent and WebTouchPoint. - -Update pointer/hover media query API & internal usage P3 1.000.5/0.5 Collect -data & possibly drop support for hover:on-demand. <https://crbug.com/654861> -0.5/0.5 Update mouse/touch detection code to use media queries. -<https://crbug.com/441813> - -MUS Main Thread Hit Testing P3 0.00Support MUS team by providing API for hit -testing against the blink tree. - -Touch-action hit testing P3 0.00#wp-architecture, #wp-performance Have a -concrete design of how SPV2 will information necessary for touch-action hit -testing on the compositor. EOQ update: no design doc in place. - -## Scrolling Related 0.58 - -### Eliminate key developer pain points 0.44 - -Polish document.rootScroller design P1 0.40#wp-fizz \[0.5\] Ship -document.rootScroller origin trial in M57 \[0.2\] Provide demos and motivating -cases on how to use document.rootScroller \[0.2\] Create WICG repo to host -standardization process and engage with other vendors \[0.1\] Publicize the -experiment via developer outreach channels #wp-devx - -Fix layout vs visual viewport discrepancy in window APIs P2 0.20Description: -#wp-predictability \[0.2\] Publish doc describing the issue and summarizing the -current situation \[0.4\] Get feedback from a senior Safari engineer on whether -they’re likely to change their viewport model and if they like the “inert” -viewport mode. \[0.4\] Ship either “inert visual viewport” or change “client” -coordinates to be visual in M58 - -Ship Overscroll Action API P1 0.60\[0.4\] Land drafted overscroll-action API -in M58 behind a flag \[0.2\] Get consensus for new scroll-boundary API \[0.3\] -Implement new scroll-boundary API \[0.1\] Ship a final API in M58. - -Ship unified OSK model on Android in M58 P3 0.40\[0.2\] Document behavior of -other browsers \[0.3\] Verify interactions with fullscreen, orientation, split -screen, web app mode. Fix bugs and write web-platform style tests. \[0.5\] Ship -in M58 - -### Improve wheel scroll performance 0.63 - -Support of touchpad scroll latching on all platforms behind a flag. P1 -0.70#wp-performance \[0.5\] Implement touchpad latching behind a flag on all -platforms in M58 \[0.5\] Ship a finch trial by EOQ (not a finch trial?) - -Support of async wheel events with only the first event cancellable behind a -flag. P2 0.30#wp-performance \[0.7\] Implement async wheel events behind a flag -in M58 \[0.3\] Ship a finch trial by EOQ - -### Code Health 0.00 - -Remove scrollbar code duplication P3 0.00#wp-architecture \[0.5\] Mac Scrollbars -painted in same paths as Aura/Android (<https://crbug.com/682209>) \[0.5\] Move -scrollbars out of ScrollableArea (<https://crbug.com/682206>) - -### Understand how users scroll 0.55 - -Collect UMA stats for how users scroll P1 1.00\[0.5\] Measure how often users -scroll with scrollbars in M57. \[0.3\] Measure how often users scroll using -keyboard, wheel, touch in M58. \[0.2\] Measure how often users scroll with auto -scroll in M58. - -Process is in place to analyze Rappor metric results for scroll latency P1 -0.10#wp-performance \[0.4\] Get Rappor metric data analyzed and aggregated in -UMA or some other database \[0.4\] Generating appropriate charts in the Rappor -dashboard or Locally \[0.2\] Use Rappor data to investigate at least one related -issue if anything comes up - -### Reliable Web Platform Scrolling 0.40 - -End quarter with 5 fewer Pri=0,1,2 scrolling bugs P2 0.40#wp-predictability -Currently at 99, query: http://go/input-dev-scrolling-bugs - -### Implement Aura Overlay Scrollbars 0.95 - -Turn on Overlay Scrollbars in CrOS in M59 by default P1 1.00 - -Prioritise and fix all polish related issues P2 0.80Issues tracked in -<https://docs.google.com/spreadsheets/d/13pt4tM4Prm7WSVL_bAtdGN6XKHPhvEYoYSvjwH-CGTU/edit#gid=0> - -Be responsive in working with PMs and UI review team 1.00 - -## Threaded Rendering Related0.45 - -### Accelerate more CSS animations 0.15 - -Accelerate transform animations containing percentages P2 -0.10<http://crbug.com/389359> MQU: Discussed with Paint team, no potential -problems found. Otherwise, no progress EOQ: No further progress - -Accelerate independent transform properties P2 0.20MQU: Investigation done, -seems good to go. Needs design doc, no implementation yet. We now support the -value 'none', and updated spec and Blink (main-thread) for smooth animation -to/from none. EOQ: No further progress. - -Accelerate background-position P3 - -### Enable more rich scroll effects 0.47 - -Polish position sticky P1 0.700.7 - all P1 bugs older than 30 days fixed in M58 -\[100\] 0.3 - shared test suite uploaded to csswg-tests \[50\] - -Implement Scroll Snap Points for composited scrolling in M58 behind a flag P2 -0.400.2 - design what information needs to be sent to CC 0.2 - match the new CSS -properties and box alignment model 0.2 - Implement snap info on main and send to -CC 0.4 - Implement snapping for touch scrolling on compositor - -Scroll-linked animation polyfill P2 0.50Polyfill of proposed API written to -support / inform the spec. A demonstrating demo. Polyfill WIP. - -Support main thread scroll customization P3 0.00Implement declarative API to -allow main thread scroll customization without affecting all scrolling. This is -required for an original trial experiment. \[PUNTED\] - -Implement CSSOM Smooth Scroll P2 0.80Implement CSSOM Smooth Scroll and collect -UMA metrics along with implementation - -### Improve performance-isolation on the web. 0.36 - -Fix known bugs in existing AnimationWorklet / Compositor Worker implementation -P1 0.25Fix any remaining bugs and polish the interface and performance: - -document.scrollingElement is not working (<https://crbug.com/645493>) - -occassional renderer freeze (<http://crbug.com/647035>) - -Batch property updates to compositor proxies enabling running on a different -thread. P1 0.40 - -Fix known bugs in AnimationWorklet spec P1 0.50We have a number of ship-blocking -issues outstanding. Drive resolution to have an MVP animation worklet draft spec -by EOQ - -Implement new AnimationWorklet API P3 0.00This is gated on resolving -specification issues and is therefore marked as stretch (we can use the polyfill -in the interim). - -\[stretch\] Document / share plan for receiving input in animation worklet P4 -0.50With plans for how this will work in Salamander. A plan was shared at -blinkon to no objections for a rudimentary WIP API but objections have been -raised regarding sharing this more broadly at houdini f2f. Need more feedback -externally. - -### Improve Threaded Rendering Code Health 0.10 - -Factor cc scrolling logic out of LTHI P3 0.00It should be possible to factor -scrolling logic out of LTHI 0.5 Write design doc and create consensus around -doing this clean up 0.5 Implement ScrollingHost to be responsible for scrolling -logic in LTHI - -Investigate flakiness in threaded-rendering tests P3 0.40We have heard from -animation team that some test are failing when used with threaded compositing. -We need to investigate why and decide if it is worth more effort and formulate a -solution - -Refactor AnimationWorklet plumbing to use animation machinery 0.00Adapt existing -machinery for web-animation where appropriate reaching stage #3 as described in -this initial design doc: -https://docs.google.com/document/d/1q8ubhpeOvDOQk-BwthZzOcaZOvhWj7D-dTVYxPOvHYM/edit - -### Make compositing excellent 0.51 - -Fix 16 open Hotlist-Threaded-Rendering bugs P1 0.80 - -Track whether we're closing more Hotlist-Threaded-Rendering bugs than are opened -P1 0.00 - -Scroll on compositor thread more frequently on desktop. P1 0.60Increase the -percentage of scrolls on the compositor thread by 5%. Ideas include making it -possible to promote opaque fixed position elements, non text containing elements -, border-radius (without memory hit, 80% completed). Blocking bug for mixing -composited and non composited content was not resolved. - -Experiment not compositing small scrollers P2 0.74We have seen during perf -parties that small composited scrollers can cause layer explosion. We should -launch a Finch trial tracking memory and performance tradeoff. - -### Identify / demonstrate best performance web practices 0.67 - -Implement and publish 2 new UI patterns P1 1.00Expect to get ~40k views per -post. #wp-devx - -Identify effects used in 5 native applications which should be web apps P3 0.00 - -Analyze one existing framework and identify potential pitfalls / improvements -\[stretch\] P3 0.00 - -### Improve understanding of the limitations and tradeoffs of threaded rendering in the wild. 0.38 - -Analyze CPU costs as layer count increases based on UMA data P2 0.20 - -Fix metric measuring difference between compositor frame rate and main thread -frame rate P2 0.20tdresser@ found that -scheduling.browser.mainandimplframetimedelta2 was not accurate. We should fix -this so we can accurately track the upper bound on slippage. tdresser -investigating whether rAF aligned input fixes this. We found particular -instances of slippage in a trace which reported no slippage, but code looks like -it should be correct. Needs further debugging. - -Measure time to move compositor frame from renderer to display compositor P2 -0.80- Did measurement on Daisy CrOS and local machine. - Added Microbenchmark. - -Added UMA for aggregation and draw frame in display compositor. - -Perf Party: compositing edition P2 0.40Case study specific to GPU/compositing w/ -write-up and action items. 2 this quarter. - -Measure additional GPU cost due to layer promotion P3 0.20Ensure we can track -regressions due to layer explosion.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/input-dev/input-objectives/2018-okrs/index.md b/chromium/docs/website/site/teams/input-dev/input-objectives/2018-okrs/index.md deleted file mode 100644 index 0af829fe668..00000000000 --- a/chromium/docs/website/site/teams/input-dev/input-objectives/2018-okrs/index.md +++ /dev/null @@ -1,343 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/input-dev - - Input Team -- - /teams/input-dev/input-objectives - - Input Objectives -page_name: 2018-okrs -title: 2018 OKRs ---- - -## 2018 Q4 - -## **Eventing Sub-team** - -### Add Richness to Web Platform 0.67 - -Worker input event routing P1 0.50 - -Ship predicted points API P1 0.50 - -Ship User Activation v2 P1 1.00 - -Resolve all User Activation v2 test regressions by M72 P2 0.80 - -Ship pointerrawmove P2 0.80 - -Harden User Activation code against untrusted renderer (crbug.com/848778) P3 -0.20 - -### Product Excellence 0.58 - -Synthetic pointer events automation 0.70 - -Be responsive to our users P1 1.00 - -Fix impactful bugs P1 0.60 - -Fix prominent input interaction bugs P1 0.55 - -Improved key inputs on Windows P1 0.30 - -GPU Benchmarking enhancements P2 0.00 - -PointerLock & MovementX/Y P2 0.50 - -Unified Pointer Capture in Blink P3 0.40 - -### Code Health 1.00 - ---use-zoom-for-dsf in Android 1.00 - -Land 8 code-cleanup CLs. P2 1.00 - -## Scrolling Sub-team - -### Add Richness to Web Platform 0.70 - -Enable pull to refresh on the web P1 0.60 - -Ship Implicit RootScroller P1 0.80 - -### Improve Performance 0.60 - -Hold the line on Input Performance 0.80 - -Passive root wheel event listener intervention (crbug.com/125223) P1 0.80 - -Prediction framework experiments for scrolling P1 0.50 - -Improve scrolling smoothness in high-latency mode P3 0.00 - -Remove timer to update hover state P3 0.30 - -### Code Health 0.50 - -Ship Blink-Gen-Property-Trees P1 0.80 - -Threaded and OOPIF scroll tests coverage P2 0.00 - -De-flake Scrolling Tests P2 0.60 - -Scroll Unification P2 0.80 - -Fix scroll restoration issue on youtube P3 0.50 - -## 2018 Q3 - -### **Eventing Sub-team** - -### Add Richness to Web Platform 0.58 - -Fix remaining User Activation v2 test failures P1 0.50 - -Ship User Activation v2 P1 0.60 - -Worker input event routing P3 0.10 - -Harden User Activation code against untrusted renderer P2 1.00 - -Ship predicted points API P2 0.60 - -Move Pointerlock spec v2 to recommendation P4 0.20 - -### Product Excellence 0.70 - -Be responsive to our users P1 0.50 - -Fix impactful bugs P1 0.70 - -Move movementXY calculation to Blink P4 0.10 - -Direct manipulation stylus across all platforms P1 1.00 - -Yeti team support P1 1.00 - -Prediction framework experiments P2 0.40 - -Noisy mouseleave events on Windows (crbug.com/798535) P2 0.40 - -Automate pointerevent tests in wpt.fyi P4 0.20 - -Enhance GPU benchmarking API surface P2 1.00 - -Make GPU synthetic pointer action calls consistent with test driver calls P4 -0.00 - -### Code Health 0.72 - -Enabling --use-zoom-for-dsf in Android P1 0.90 - -Use TSF instead of IMM32 on the latest Windows edition P2 0.60 - -Cleanup User Activation v2 interface at Web layer (crbug.com/803203) P3 0.60 - -Switch |WebInputEvent::Modifiers| to an enum class P4 0.00 - -## Scrolling Sub-team - -### Improve Performance 0.78 - -Hold the line on Input Performance P1 1.00 - -Make document-level wheel listeners passive by default (crbug.com/626196) P1 -0.80 - -Async touchpad pinch zoom (crbug.com/565980) P2 0.90 - -Keyboard threaded scrolling (crbug.com/125223) P4 0.00 - -Make new chrome metric dashboard P4 0.00 - -UKM in-depth analysis P4 0.00 - -### Add Richness to Web Platform 0.80 - -Ship Implicit RootScroller P1 0.80 - -### Improve Code Health 0.69 - -Blink Generated Property Trees P1 0.90 - -Create concrete plan for scroll unification P2 0.30 - -Drive down layout test flakiness P3 0.60 - -### Product Excellence 0.53 - -Fix bugs related to “scrolling does not work” P1 0.50 - -Fix bugs related to fling and autoscroll fling P2 0.60 - -Fix bugs related to scroll restoration P3 0.50 - -## 2018 Q2 - -**Eventing Sub-team** - -### Add Richness to Web Platform (#blink-eco-standards) 0.53 - -Resample input events on main thread and compositor P1 0.50 - -User Activation v2 test failures P1 0.75 - -User Activation v2 core implementation P1 0.45 - -Browser-side triggering of User Activation P2 0.70 - -Predicted Points P3 0.20 - -Resume prototyping Worker input event routing (#blink-prim-workers) P4 0.10 - -PointerLock v2 (#blink-eco-wpt) P4 0.00 - -### Product Excellence (#blink-pe) 0.71 - -Be responsive to our users (#blink-pe-bugs) P1 0.50 - -Fix 10 regression bugs (#blink-pe-bugs) P1 1.00 - -Fix 8 bugs with >10 stars (#blink-pe-bugs) P1 0.90 - -Move movementXY calculation to Blink (#blink-pe-bugs) P2 0.40 - -Rational gesture token handling in Blink (crbug.com/789643) P4 0.50 - -Automate pointerevent tests in wpt.fyi (#blink-eco-wpt) P4 0.10 - -### Code Health (#blink-pe-code-health) 0.57 - -Enabling --use-zoom-for-dsf in Android P2 0.70 - -Cleanup User Activation v2 interface at Web layer (crbug.com/803203) P3 0.10 - -Fix WebFrameClient vs WebRemoteFrameClient naming problem (crbug.com/846405) P3 -1.00 - -Use WebPointerEvent instead of WebMouseEvent Blink (#blink-pe-oopif) P4 0.10 - -## Scrolling Sub-team - -### Code Health (#blink-pe-code-health) 0.70 - -Flings generated in the browser process P1 0.90 - -\[SPv2\] Implement scrollbars for SPv2 P2 0.40 - -\[SPv2\] Implement ScrollTree/Layer construction in PaintArtifactCompositor P2 -0.60 - -\[SPv2\] Implement visual viewport for SPv2 P3 0.70 - -### Performance (#blink-opti-scheduling) 0.81 - -Improve understanding of real-world scrolling performance P1 0.70 - -Hold the line on Input Performance P1 1.00 - -Publish Integrated UMA/UKM dashboard P4 0.20 - -### Product Excellence (#blink-pe) 0.58 - -Window Touchpad P1 1.00 - -Implicit root scroller (#blink-pe-bugs) P1 0.40 - -Improve Wheel Scrolling Code (#blink-pe-bugs) P2 0.40 - -Improve ChromeOS Scrollbar Experience P3 0.00 - -## 2018 Q1 - -**Eventing Sub-team** - -### Improve Smoothness and Predictability of Input Events 0.33 - -### Resampling input events at rAF P1 0.50 - -### Predictive Points P2 0.00 - -### Add Richness to Web Platform 0.57 - -### User Activation v2 (Simple User Activation) P1 0.70 - -### Ship InputMode P1 1.00 - -### PointerEvent spec - Close out V2, start on V3 P1 0.70 - -### Continue prototype for Worker input event routing P2 0.00 - -### Spec for input for Workers P2 0.00 - -### Improve Android Drag & Drop (crbug.com/156390) P2 0.50 - -### Spec and Ship InputModeAction P3 0.50 - -### Clarify screenX/Y and movementX/Y definitions P4 0.20 - -### Performance 0.82 - -### Hold the line on Input Performance P1 0.70 - -### UKM dashboard P1 1.00 - -### Clean up input metrics P2 0.70 - -### Product Excellence 0.75 - -### Be responsive to our users P1 1.00 - -### Touch Adjustment (crbug.com/625198) P1 0.80 - -### Fix 8 regressions bugs P2 1.00 - -### Fix 6 bugs with >10 stars P2 1.00 - -### Interoperable mouse user gestures (crbug.com/769796) P2 0.00 - -### Rational gesture token handling in Blink (crbug.com/789643) P3 0.00 - -## Scrolling Sub-team - -### Great Windows 10 Experience 0.74 - -### Windows 10 Precision Touchpad basic support P1 0.80 - -### Windows 10 Precision Touchpad support gesture based navigation P3 0.50 - -### Product Excellence 0.57 - -### Fix impactful bugs P2 0.71 - -### \[Stretch\] Subpixel precision scrolling on main thread P4 0.00 - -### Improved Code Health 0.71 - -### Flings generated in the browser process P1 0.60 - -### Frame and Element Scrolling Unified P1 1.00 - -### Keyboard scrolls using gesture events P3 0.00 - -### Improve Viewport Interoperability 0.07 - -### Describe visual/layout viewport in an official spec P2 0.00 - -### Settle on an interoperable and compatible way to size the layout viewport P3 -0.00 - -### Fix interop issues related to how pages load initially P3 0.20 - -### Add Richness to Web Platform 0.21 - -### Web Apps can compose in views P1 0.20 - -### Ship Scroll Customization Origin Trial P4 0.30 - -### Performance 0.71 - -### Improve Wheel Scrolling Performance P1 0.80 - -### Improve understanding of real-world wheel scrolling performance. P4 0.00
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/input-dev/input-objectives/index.md b/chromium/docs/website/site/teams/input-dev/input-objectives/index.md deleted file mode 100644 index 3e7f193e102..00000000000 --- a/chromium/docs/website/site/teams/input-dev/input-objectives/index.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/input-dev - - Input Team -page_name: input-objectives -title: Input Objectives ---- - -At Google we define and track progress against our goals using -["OKRs"](https://www.gv.com/lib/how-google-sets-goals-objectives-and-key-results-okrs) -(Objectives and Key Results). Here are most of the OKRs for the input-dev team -(a couple minor KRs relating to internal projects such as future Android -releases have been omitted for confidentiality reasons). Note that these are -**intentionally aggressive** and so we will be happy if we deliver 60%-70% of -them. - -## 2019 Q1 - -**Eventing Sub-team** - -### Add Richness to Web Platform (#AppGap) - -Ship predicted points API P1 - -Off-Main-Thread Input Event Delegation P1 - -Pointerevents V3 extension P2 - -Ship pointerrawmove P2 - -Virtual Keyboard API P2 - -Activation delegation API P2 - -HTML spec for UAv2 P2 - -### Product Excellence (#ProductExcellence) - -Enable TSF by default - -Handle UAv2 post-launch regressions - -Be responsive to our users P1 - -Fix impactful bugs P1 - -Disable platform inputs in testing mode P1 - -Synthetic pointer events automation (#HappyPath) P1 - -Trusted Activation Triggers P1 - -PointerLock coordinates: make the coordinate space well-defined. P2 - -GPU Benchmarking enhancements (#HappyPath) P2 - -Fix Android startup delay caused by slow hardware updates P2 - -Resolve mouse interop issues P2 - -### Code Health (#TechnicalExcellence) - -Pen input with Palm rejection (crbug.com/852022) - -Unified Pointer Capture in Blink P3 - -PointerLock coordinates: consolidate calculation of movementX/Y P4 - -## Scrolling Sub-team - -### Add Richness to Web Platform (#AppGap) - -Enable pull to refresh on the web - -Scroll to text fragment P1 - -### Improve Performance (#FluidUI) - -Hold the line on Input Performance P1 - -Improve scroll prediction with other predictors P1 - -Compositor touch action P2 - -Keyboard threaded scrolling P3 - -### Code Health (#TechnicalExcellence) - -Non-Flaky Tests P3 - -Scroll Unification P4 - -## Historical Objectives and Results - -## [2018 OKRs](/teams/input-dev/input-objectives/2018-okrs) - -## [2017 OKRs](/teams/input-dev/input-objectives/2017-okrs) - -## [2016 OKRs](/teams/input-dev/input-objectives/2016-okrs) - -## [2015 OKRs](/teams/input-dev/input-objectives/2015-okrs)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/bug-triage/index.md b/chromium/docs/website/site/teams/layout-team/bug-triage/index.md deleted file mode 100644 index 1297558fe95..00000000000 --- a/chromium/docs/website/site/teams/layout-team/bug-triage/index.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -page_name: bug-triage -title: Bug Triage Instructions ---- - -The layout team has a bug triage rotation where for a week at a time a member of -the team is responsible for triaging bugs associated with parts of the code that -the team is responsible for. This document outlines the policy and suggestions -surrounding bug triage. - -Our SLA is to triage all incoming bugs within one week and to fix all P1 -regressions within one release. - -## Suggested workflow: - -1. Every other day check the list of [Untriaged - bugs](https://bugs.chromium.org/p/chromium/issues/list?can=37830509&sort=-id&colspec=ID+Pri+M+Status+Owner+Summary+Modified) - with the aim to reduce the number to zero. - For each bug, check whether the issue can be reproduced. - * If not either mark as WontFix or add the "Needs-Feedback" label - and ask for follow up information. - * If it can be reproduced, determine if it's a valid bug. Check - behavior in other browsers and the relevant specifications. - * If it is a valid bug determine whether it is a regression or - not. Set type to Bug-Regression if it is and determine [when it - broke](/developers/bisect-builds-py). Set relevant sub category - and assign to the person that introduced the regression. - * If valid and not a regression determine severity. For P0 and P1 - assign to owner for specific area. For P2 set status to - Available. -2. At least once a week check the list of regressions - ([P0/P1](https://bugs.chromium.org/p/chromium/issues/list?can=37830592&q=Pri%3D0%2C1&sort=-id&colspec=ID+Pri+M+Status+Owner+Summary+Modified), - [P2/P3](https://bugs.chromium.org/p/chromium/issues/list?can=37830592&q=-Pri%3D0%2C1&sort=-id&colspec=ID+Pri+M+Status+Owner+Summary+Modified)). - For each P0 or P1 regression, check if it can still be reproduced. - * If not mark as Fixed and add comment to CL that fixed it. - * If the issue persists ping the owner or assign one as needed. - Continue with P2 and P3 regressions as time allows. Don't spend more than - ~1h/week on regression triage. - -## Relevant Links - -* [Untriaged - bugs](https://bugs.chromium.org/p/chromium/issues/list?can=37830509&sort=-id&colspec=ID+Pri+M+Status+Owner+Summary+Modified) -* [P0 and P1 - regressions](https://bugs.chromium.org/p/chromium/issues/list?can=37830592&q=Pri%3D0%2C1&sort=-id&colspec=ID+Pri+M+Status+Owner+Summary+Modified) -* [P2 and P3 - regressions](https://bugs.chromium.org/p/chromium/issues/list?can=37830592&q=-Pri%3D0%2C1&sort=-id&colspec=ID+Pri+M+Status+Owner+Summary+Modified) -* [Bisecting builds](/developers/bisect-builds-py)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/eliminating-simple-text/index.md b/chromium/docs/website/site/teams/layout-team/eliminating-simple-text/index.md deleted file mode 100644 index 25e8a21e7ac..00000000000 --- a/chromium/docs/website/site/teams/layout-team/eliminating-simple-text/index.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -page_name: eliminating-simple-text -title: Eliminating Simple Text ---- - -[eae](mailto:eae@chromium.org), [drott](mailto:drott@chromium.org), -[behdad](mailto:behdad@chromium.org), [kojii](mailto:kojii@chromium.org) -April 2, 2015 - -Blink currently has two separate text paths, the simple path and the complex -path. The simple path is an optimization and is used for a handful of scripts, -most notably latin-1, when no advanced typesetting features are used. - -## Complex Text Performance - -We'd like to eliminate the simple text path and have all text use the current -complex text path. Doing so would allow us to support kerning and ligatures -everywhere, have similar performance regardless of script and, more importantly, -greatly reduce code complexity and reduce bugs resulting from differences in the -two code paths. - -In order to do that though we must first improve the performance of the complex -path to match, or exceed, the performance of the simple path. Early measurements -here or here suggests that hb_shape() itself is not anything nearly the -bottleneck at all, and a lot of churn happens in HarfBuzzShaper, which can and -should be streamlined. - -### Ideas for improving complex text performance: - -* Replace current (broken) run cache with a word cache (see below for - more ideas on how to cache width info), ala Firefox. -* Normalize text directly on harfbuzz buffer, avoiding extra copy of - string. -* Add support for latin-1 text to shaper, avoiding upconverting - latin-1 text to utf-16. -* Remove overhead of deciding which code path to use. -* Do not repeatedly setFontFeatures on each shaper construction -* Do not create list of HarfBuzzRun’s, etc, just to free them after - iterating over them once. Copy to output buffer directly from - hb_buffer(). -* Switch to HarfBuzz-based itemization; this, if done properly, will - result in improved performance; but is mainly a correctness feature. -* Keep information about HarfBuzzRun segmentation in a parallel data - structure, see below. - -## Details - -### Keeping Word Length Measurements / Thoughts on Caching - -Word length measurements are a function of a styled font instance, language -information, script information, and a string of text and it’s surrounding text -or context. - -length = f(font, language, script, text, context) - -Instead of continuously calling constructTextRun and textWidth during layout, -then doing this all over again for selections, dirty rectangles and so on, we -can perhaps keep a separate text tree that contains the information required for -length measurements and the strings. Then RenderObjects would just reference -portions of this text tree, and can directly derive width information. - -Instead of a “singleton word cache” somewhere with only an eviction heuristic or -a fixed size, we could have stricter lifecycle control over the objects in such -a tree - they would stay in sync with the RenderObjects that reference them. -When more text containing nodes are added to the DOM, new objects in the text -tree are created. When DOM Nodes are deleted, we no longer need portions of the -text tree. - -Note that the size of a word is not always easy to define for languages that do -not necessarily use an explicit word separator such as a space character. - -### HarfBuzzRun Segmentation - -The parallel data structure as outlined above, should also keep information -about shaping run segmentation, and - if needed - recompute that on a finer -granularity, if text changes. - -### Optimize hb_shape() - -HarfBuzz’s OpenType processing is much faster than alternatives we have -measured. Still, the kerning feature in Roboto takes half of the shaping time. -That’s way too excessive. In general, comparing hb-shape’s performance with ---shaper=ot against --shaper=fallback shows how far off we are from a barebone -fastpath. Currently this number stands at about 10x, depending on what font and -what font_funcs implementation. More measurement and optimizations here are -possible. - -### Benchmarks - -We should restructure our telemetry benchmarks specifically for text measurement -performance, perhaps have a separate group of tests besides blink_perf.Layout. - -In addition to that, we need to develop new test cases, to better cover real -world text-performance heavy use cases. - -Out of that effort we could develop a publicly available text layout benchmark, -to compare Blink performance against other engines. The Sunspider, Kraken of -text layout. - -### Unit Testing - -We should create a native test harness for the Font.cpp and HarfBuzzShaper.cpp -logic. - -In order to improve our shaping correctness and perhaps do performance tests on -a level that cuts out blink layout etc. we should try to create a test harness -for Font.cpp where we can instantiate fonts by name, size and font features. -Then we can test for how runs are formed, shaping results, etc. - -## Eliminating Simple Text - -Once the complex text path is as fast (or nearly as fast) as the current simple -text path we should force all text down the complex text path and (eventually) -eliminate the simple text path entirely. This will give us an extra performance -win as it allows all text path branching to be removed, including costly string -scans. It would also allow us to enable typesetting features, such as kerning -and ligatures, for all text. More importantly though it would allow us to have a -single unified text layout path which in turn would reduce complexity and -maintenance costs as well as as ensure consistent performance regardless of -script.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/index.md b/chromium/docs/website/site/teams/layout-team/index.md deleted file mode 100644 index 591474b9aa0..00000000000 --- a/chromium/docs/website/site/teams/layout-team/index.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: layout-team -title: Layout Team ---- - -The layout team has been subsumed into the new [rendering -core](//chromium.org/teams/rendering) team. Please see the rendering core page -for details about ongoing style and layout work. -This page is preserved for posterity and will no longer be updated. - -The layout team is a long-term engineering team tasked with maintaining, -supporting, and improving the layout capabilities of the Chromium Blink -rendering engine. This includes line layout, block layout, text, fonts, and -high-dpi support. It is distinct from [style](/teams/style-team) and -[paint](/teams/paint-team), both of which are handled by their respective teams. - -## Team Charter - -Our overarching goal is to **improve the experience for end users and platform -developers alike**. - -* By offering fast, correct, and compatible layout features supporting - the majority of writing systems and scripts. -* By providing layered and powerful APIs for developers. -* By driving the layout capabilities of the web forward through - collaboration with web developers, other browser vendors, and - standard bodies. -* And finally, by intervening when required. Thereby allowing a better - user experience for existing and legacy content. - -## Big ticket items for 2017 - -* Schedulable, interruptible engine - * LayoutNG can render ~50% of web content. -* Give framework authors the ability to extend the rendering engine - * Ship at least one CSS Houdini API. -* High quality predictable platform - * Maintain bug SLA - * Full test and design doc coverage. - * Ship CSS Grid. - * Unify scrolling implementation (root layer scrolling). - * Ship OpenType variation support. - * Intersection Observer v2. -* Improve rendering performance - * Improve line layout performance by 20% - -A large number of other individuals not listed above routinely contribute to our -layout code and their impact and contributions should in no way be downplayed. -This merely lists the people that formally make up the layout team or have -committed to a certain task or project. - -If you are looking for someone to review a change to the layout code anyone on -the list above should be able to help or connect you with the right person. For -questions about the design or implementation of a certain layout sub-system or -about layout in general the entire team may be reached through the -[layout-dev](mailto:layout-dev@chromium.org) mailing list. - -For higher level questions or if you are interested in joining the team, please -reach out to [Emil](mailto:eae@chromium.org). - -## Design Documents - -* [LayoutUnit & Subpixel - Layout](https://trac.webkit.org/wiki/LayoutUnit) (2012) -* [Line Box float -> LayoutUnit transition - plan](https://docs.google.com/a/chromium.org/document/d/1fro9Drq78rYBwr6K9CPK-y0TDSVxlBuXl6A54XnKAyE/edit) - (2014) -* [Blink Coordinate - Spaces](/developers/design-documents/blink-coordinate-spaces) (2015) -* [Eliminating Simple - Text](/teams/layout-team/eliminating-simple-text) (2015) -* [LayoutObject Tree API - Proposal](https://docs.google.com/document/d/1qc5Ni-TfCyvTi6DWBQQ_S_MWJlViJ-ikMEr1FSL0hRc/edit) - (2015) -* [Using Zoom to Implement Device Scale - Factor](https://docs.google.com/document/d/1CZSCPzOYujdUMyChocwzOBPKxYAoTsEoezMye30Hdcs/) - (2015) -* [Scroll Anchoring](http:////bit.ly/scroll-anchoring) (2016) -* [Shaper Driven Line - Breaking](https://docs.google.com/document/d/1eMTBKTnWEMDu00uS2p8Xj-l9Pk7Kf0q5y3FbcCrWYjU/edit?usp=sharing) - (2016) -* [Root Layer - Scrolling](https://docs.google.com/document/d/137p-8FcnRh3C3KXi_x4-fK-SOgj5qOMgarjsqQOn5QQ/) - (2017) - -**Documentation** - -* [Out of flow - positioning](https://docs.google.com/document/d/1Qbgfx7vh2CTxa8CsYVS25tQWtkGdrN-D6TzPmYGZNtc/edit#heading=h.ndf3qdi6efu4) - -## Links - -* [Readmap & Potential - Projects](/teams/layout-team/potential-projects) -* [Team mailing - list](https://groups.google.com/a/chromium.org/forum/#!forum/layout-dev) -* [Profiling Blink using Flame - Graphs](/developers/profiling-flame-graphs) -* [Skia telemetry try - bot](http://skia-tree-status.appspot.com/skia-telemetry/chromium_try)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/20141209/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/20141209/index.md deleted file mode 100644 index 95559141d4f..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/20141209/index.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: '20141209' -title: Tuesday, December 9, 2014 ---- - -Attendees: benjhayden, cbiesinger, dsinclair, dglazkov, eae, jchaffraix, nduca, -szager, skobes -Introductions, quick updates: -eae: In SFO, currently working on text and line layout cleanup/performance -szager: In SFO, recently transferred to blink from chrome infrastructure. -dan: In WAT, working on paint invalidation and not mutating the render tree -during layout -cbiesinger: In NYC, working on all sorts of things, mostly cleanup at the -moment. -jchaffraix: In MTV, working on rendering and project warden -skobes: In MTV, scrolling cleanup, warden -benjhayden: In MTV, recently transferred to blink to work on layout performance. -Project Warden update from Dan: -Warden is a project to clean up long standing issues, mostly in the -layout/rendering space, including: -- widget tree hierarchy -- asserts, clusterfuzz -- fixing full screen to work correctly -- avoiding render tree mutations during layout -- move line layout to layout unit -- unify scrolling paths -- type system for blink (screen vs layout coordinates) - -Project warden is a project under the layout team and will continue as is. With -the additional resources of the entire layout team we can now take on additional -tasks. Performance is a key goal but we are currently suffering from reliable -metrics and limitations when it comes to performance testing. - -Legacy webkit performance tests are non-ideal in that they are sampling based -and do properly account for scheduled cpu time. Modern telemetry tests account -for scheduling and measures time on a low, fine grained level resulting in more -reliable metrics. We should investigate converting existing tests to -telemetry-style or creating new layout performance tests to guide our work. We -also need to profile the layout code based on these tests and real world -websites to determine performance bottlenecks and hot code paths. - -Overhead: -- Weekly stand-up meetings? -- Re-purpose the existing project warden meetings (Mondays at 11am PST) -- Bi-quarterly OKR meetings (beginning of quarter to grade last quarters OKRs -and set new objectives, mid-quarter check-in). -- Set up team mailing list? Decided not to and use blink-dev for the time being. -- Set up team web site? Yes. -OKR candidates: -- position sticky? -- measurement api -- better perf tets -- report on whats slow -- performance work -- layout hooks (from glitter) -- natural animations -- subpixel when animating -Action items: -- Add all layout team members to weekly stand-up \[dsinclair\] -- Schedule OKR meeting for \[eae\] -- Come up with short list of proposed OKRs in preparation for next meeting -\[eae, jchaffraix\] -- Set up web site for team \[eae\] -- Discuss performance testing strategies \[benjhayden, nduca, eae\] -- Explain team role in overall blink \[deferred until after OKR meeting\]
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/20150107/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/20150107/index.md deleted file mode 100644 index b20aee82e9e..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/20150107/index.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: '20150107' -title: Q1 OKRs - Wednesday, January 7, 2015 ---- - -Attendees: benjhayden, cbiesinger, dsinclair, eae, jchaffraix, nduca, szager, -skobes - -... Pleasantries, going over the list of proposed OKRs ... - -\[ Discussing the proposed "Have ten layout benchmarks with less than 1% -variation between runs" OKR \] - -<benjhayden> For the benchmark OKR are you referring to to descriptive -benchmarks? - -<eae> Not necessarily, the goal is to have reliable benchmarks to guide -our work. Short term that likely means silk-style measuring layout times. - -<jchaffraix> We do want to move to descriptive benchmarks (new type of -benchmark using recipes) eventually. - -\[ Discussing the proposed "Improve two benchmarks by 10%" OKR \] - -<cbiesinger> How will we choose which tests to improve by 10%? - -<jchaffraix> Any of the tests really. - -<eae> Will be guided by our findings when adding benchmarks and doing -profiling. - -<cbiesinger> We should make the objective more precise, what kind of -benchmark? - -<nduca> Make it two key_silk cases - -\[ Discussing the proposed "Support subpixel layout during animation" OKR \] - -<skobes> What is involved with subpixel layout during animation? - -<eae> Today we snap to CSS pixels during layout, which ensures crisp -rendering, but during animations this causes animations to move on full pixel -boundaries which isn't ideal. - -<nduca> It's all about enabling natural animations.. without that layout -animations looks bad. - -<eae> ...really bad. - -<dsinclair> Do we have any idea how hard it will be? - -<eae> Technically all we need to do is not pixel-snap during animations -but doing that without complicating the code and introducing a separate code -path for animations could be tricky. - -<dsinclair> We don't want to add "if (animation)" checks everywhere. - -\[ Discussing the proposed "Move line layout to LayoutUnits" OKR \] - -<eae> How is the work to move line layout to LayoutUnits coming along, is -finishing it in Q1 a realistic goal? - -<benjhayden> Should be doable, making good progress. Stefan has started -helping out. - -<dsinclair> A lot of it is figuring out rounding errors and burning down -the list of issues. - -\[ Discussing the proposed "Prototype and propose Measure API" OKR \] - -<nduca> Is the Measure API OKR about Element.measure - -<eae> It is really too early to tell. We don't know Element.measure is the -right API yet, hence the need for a prototype. - -<jchaffraix> The idea is to create a prototype, possibly based on -Element.measure, implement it and see if it solves the problem. - -<nduca> So basically talk to Tab, spec the API and send out an "Intent to -Implement"? It doesn't have to be faster, it just needs to be separate from -layout. - -<eae> An intent to implement might be premature, we need to figure out if -we can support the proposed API first and if it actually works as expected. - -<nduca> We have a lot of requests for this and it is really important. -Nothing is sure or has been decided but we need to do something in the space. - -<eae> Julien and I talked about it earlier and think it is important to -have a prototype and have someone from Docs or another client experiment with it -to make sure it fits their use cases. - -<nduca> This isn't for Docs or desktop apps, they already have working -solutions and use native apps on android. It is more about animations between -layout states. - -<nduca> Check with \[ internal team, redacted \] - -<nduca> This is important for people doing transition animations from one -layout to another. They have to do the new layout and measure it, doing that -today requires jiggling and hacks when all they need to know is the final state. -We don't have to make it faster, just needs to support doing the measurements -without invalidating the universe. - -\[ internal discussion, redacted \] - -<eae> If that is the end goal there are other ways we could approach it. - -<jchaffraix> Let's change the OKR to "Create a prototype and write-up of -lessons learned" - -\[ Discussing the proposed "Finish root layer scrolling" OKR \] - -<eae> Is finishing root layer scrolling this quarter a realistic goal? - -<skobes> Making good progress, should be able to finish this quarter. - -\[ Discussing the proposed ClusterFuzz OKRs \] - -<skobes> How many clusterfizz asserts are you seeing now? - -<cbiesinger> About 4 pages, burning down, not sure if more will surface. -Some are on the chrome side and out of scope but there are a good number of -them. - -<cbiesinger> Actually, make that 18 pages, 10 per page... - -<eae> The OKR might be a bit too optimistic then, just triaging that many -will take quite a while. - -<dsinclair> Triage and fix 50%? - -<cbiesinger> More reasonable. - -<dsinclair> Can we do the auto triage? - -<cbiesinger> Abhishek said the ClusterFuzz team would help with that. - -<jchaffraix> How about team warden specific OKRs? - -<eae> We have 'scrolling' and 'line layout'. Do we need more? - -<julien> Ok. What other warden tasks are ongoing? - -<dsinclair> Fullscreen and single item list selectbox (also on android) -are ongoing tasks in that realm. - -<nduca> Should we have a code health objective that captures what you are -doing Dan? - -<nduca> Next quarter the the boundary between layout and style needs to be -better defined, we should help with that. - -<julien> By defining an API? - -<nduca> Code health and new features are separate concerns. We can make -our lives and the life of the style team easier by being healthier, paying down -technical debt. Making people faster is good investment. - -<dsinclair> Agreed. - -\[ Discussing position sticky \] - -<eae> Gmail, docs doesn't see it as top priority. - -<nduca> Mobile first matters for this, apps do not... ads, mobile apps -matters. - -<eae> Seems to have fizzled out from a year ago, is it still relevant? Do -we have anyone asking for it? - -<nduca> We can likely punt it for bit longer but it will come up. We might -have to bite the bullet and do it eventually. - -<nduca> The extensible web approach (layout hooks) might be better. - -\[ internal discussion, redacted \] - -<eae> Agree that solving the larger problem would be better. Let's revisit -position sticky in Q2. - -<dsinclair> Wouldn't layout hooks disable the compositor? - -<nduca> By delegating to js we would lose compositor hotness. - -<skobes> Already moving in that direction with delayed scrolling, other -concepts. Certain features disables the compositor wins. Trade-offs. - -\[ Discussing the proposed "Improve two tests by 10%" OKR \] - -<skobes> Who would be responsible for the 10% perf wins? - -<benjhayden> Would be everyone? I have some things that would imrpove -performance. I think Emil can deliver some wins though the text optimization -work. Text shows up prominently in profiling runs. - -<skobes> Is that simple vs complex text? - -<eae> not really, in the short term. Long term there are a lot of things -we can do to speed up complex text and (eventually) move to one text path. In -the short term there is a lot of room for improvement by simplifying things and -avoiding unnecessary work. - -<eae> Some of Ben's work, like short-circuiting the float handling in -layout, could have a big perf impact. - -<nduca> Everyone should try. - -<eae> Agreed, with new the new tests it is easier to track. - -<nduca> How about having a weekly meeting to keep on track? - -<dsinclair> We have one already, Mondays at 11. Re-purposed the Team -Warden stand-up.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/friday-october-2-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/friday-october-2-2015/index.md deleted file mode 100644 index 453191189a5..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/friday-october-2-2015/index.md +++ /dev/null @@ -1,822 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: friday-october-2-2015 -title: Friday, October 2, 2015 (Q3/Q4 OKRs) ---- - -Attendees: eae, cbiesinger, jchaffraix, leviw, ojan, skobes, and - -szager (with ikilpatrick, drott, and kojii giving updates offline) - -<eae> Good morning everyone. I know it feels like just yesterday we - -set our Q3 OKRs but the quarter has already come to an end. Let's - -spend the next 20 minutes going though our KRs and see how we did and - -then use the rest of the time to discuss Q4. - -\[ Discussing "Update flexbox implementation to match latest version of - -specification" \] - -<eae> Christian, this one falls on you. Would you mind giving an update? - -<cbiesinger> I've updated some aspects of it to match the latest - -specification and sent numerous "Intent to Ship" announcements to - -blink-dev. For one of the biggest changes I added a use counter to - -ensure that we don't break too many websites, now waiting for it to - -reach a stable release to get numbers. As for the second big change I - -didn't do a very good job prioritizing and all of a sudden it was - -mid-October. Will carry over into Q4. - -<cbiesinger> Spent a lot of time on importing css test suites which - -wasn't captured in OKRs. - -<eae> Sounds like a 0.5? - -<cbiesinger> Agreed. - -\[ Discussing "Remove page zoom" \] - -<eae> This one falls on me, shared with the style team. We determined - -to be feasible, vast majority of usage in the wild is for "zoom: 1", - -i.e. a no-op used to trigger "has layout" in older version of IE. No - -progress on implementation. Wasn’t a priority for either the style nor - -the layout team. It's used extensively by layout tests so requires - -quite a few tests to be updated before we can remove it. - -<eae> Score: 0.0 - -\[ Discussing "Updated Unicode Bidirectional Algorithm" \] - -<kojii> Had some progress on investigations, but not enough to write - -up. Propose score 0.2? - -<eae> Sounds reasonable. - -\[ Discussing "Unprefix CSS Writing modes" \] - -<kojii> All spec issues and critical code issues were resolved, design - -doc and consensus to ship in blink-dev and in CSS WG done. Patches - -are WIP. - -<eae> Spec issues and intent to unprefix took longer than expected, not - -due to any fault of ours. Let's call it 0.8. - -<kojii> Good. Should ship in early Q4. - -\[ Discussing "Improve font fallback" \] - -<eae> Drott couldn't make this meeting but reported the following earlier. - -<drott> Issue breaks down into better CSS font matching, better shaper - -integration, and better usage of user preference and system fallback - -APIs. Precondition, better CSS font matching done. Font fallback APIs - -on all platforms surveyed, shaper integration see below. After shaper - -integration is done, we can move to making better use of preference - -font, perhaps add per-script fallback fonts and make better use of - -system fallback APIs/Lists. - -<eae> Was a bit more work than anticipated, making solid progress. - -Will carry forward into Q4. - -<eae> Score: 0.5 - -\[ Discussing "Spec work for houdini block & line custom layout" \] - -< ikilpatrick> Mainly concentrated on the other aspects of Houdini - -this quarter being custom paint and related specs. Groundwork is being - -done for layout w.r.t. Isolated Workers & CSSOM 2.0. - -<ikilpatrick > Had some more discussions with other browser vendors - -w.r.t. what this API would actually look like. Expect that more spec - -work will be done for layout in Q1/2 next year. - -<ikilpatrick> 0.1? - -\[ Discussing "Have all calls into block layout go through well defined API" \] - -<eae> This one was shared between Levi and Ian K. Could you give an - -update here Levi? - -<leviw> So, we got line layout almost entirely buffered form block - -layout. But we didn't get anywhere to style, editing or dom. I didn't - -expect us to get to all of that but we're still making solid progress. - -Have haven't started on the other vectors. - -<eae> Should we continue full steam ahead or stop and evaluate the - -line layout API before continuing? - -<leviw> I think there is value in doing that once we've completely - -finished the line layout API work, which we're close to, and have - -include guards in place. Then we should spend a few days to see how - -much we can do to clean up the API before going forward and maybe, if - -it seems really difficult, we could take a step back. That's my take - -on it. - -<leviw> This ended up being a bigger API that I was hoping for. On the - -other hand there are places where we can simplify it, a lot. - -<ojan> I also think line layout is the chattiest one, right? - -<leviw> Right, the other ones should be simpler. So, to answerer your - -question, I think we should continue full steam ahead. - -<eae> Great. How does 0.7 sound for a score? - -<leviw> Sounds about right. - -\[ Discussing "Have a clear understanding of the cost/complexity of - -custom layout." \] - -<leviw> We should continue. A lot of understanding the cost will be - -figuring out what the API will be like. That's why we're planning to - -sit down with the IE Edge team to help clarify the API. The ultimate - -cost and complexity of getting it into our engine is entirely - -dependent on what the API ends up being. So it's hard to say right - -now. - -<eae> Would it be fair to say that our plan is to continue our work on - -a layout API boundary and have discussions with other browser vendors - -to help steer and influence the custom layout APIs? - -<leviw> Getting agreement and knowing the scope, yes. Beyond the work - -we are doing with the API it's hard to get further ahead without broad - -agreement,. - -<eae> Are we doing everything we can to help this? - -<leviw> The most important thing we can do is to engage other vendors. - -We could always do more but we're in a good place. - -<eae> So, it sounds like we've done all we can here even though we - -don't yet have a clear understanding. 0.6? - -<leviw> I'd say 0.5, just because the ultimate goal was only inched - -towards, though we know the path to get there it has a lot of external - -dependencies. - -<leviw> All we can do is try and drive it as much as possible. - -<eae> 0.5 it is. - -\[ Discussing "Finish root layer scrolling" \] - -<skobes> So we landed a bunch of stuff here, the two I'm most excited - -about would be that it now works for inner and outer viewports on - -Android. The second one being coordinates scrollbars which is pretty - -awesome. So it's not done yet but made solid progress. - -<skobes> Still a bit worried about a tree walk for overflow scroll. We - -walk the entire deprecated paint tree underneath scrollable area for - -overflow scroll. Tried to get rid of it but it's complicated. - -<skobes> Would give a score of 0.7. - -<eae> Sounds fair. - -\[ Discussing "Remove simple text code path" \] - -<eae> The performance of complex path now exceeds that of simple path - -and all remaining functionality blockers have been resolved. All that - -is left to do is flip the switch. Sadly that will involve updating - -about 50 tests and rebaselining _all_ of our layout tests. So, we did - -all of the hard work, what remains is easy but labor intensive. - -<eae> Score 0.4? - -\[ Discussing "Improve integration between Blink and Harfbuzz" \] - -<drott> Implementation done, an issue with (anyway broken) small caps - -and an edge case with ZWJ and ZWNJs for Arabic and AAT font remains so - -far. Needs code cleanup, and performance evaluation, but functions - -well. Then should be ready for landing in steps. - -<drott> Perhaps 0.8-0.9? - -<eae> Let's say 0.8. - -\[ Discussing "Triage all incoming layout bugs within one week" \] - -<eae> Next up, the first of our goals around bug health. - -<eae> We have procedures are in place to triage all incoming bugs - -within a week. Mostly a manual process for now due to lack of better - -tooling but is working fine. For the latter part of the quarter we’ve - -manage to adhere to the SLA and triage all bugs within five to six - -days. Takes me about two hours a week which isn't too bad. - -<eae> Score: 1.0 - -\[ Discussing "Reduce bug count by 30%" \] - -<eae> So, this one was definitively more ambitious.... - -<ojan> How did we do? 3%? - -<leviw> 2%? - -<eae> We actually did a lot better than I feared. We reduced the total - -bug count by 16%, just over half of our goal. We did much better for - -high-priority bugs where the count was reduced by over 75%. - -Total: From 2742 down to 2301, a reduction of 441, ~16% - -Untriaged: From 860 down to 479, a reduction of 381, ~44% - -P0/P1: From: 247 down to 56, a reduction of 191, ~77% - -<ojan> That's really impressive. - -<leviw> Reduction of over 400? Nice! - -< jchaffraix > The fact that we still have over 50 P0/P1 bugs is - -pretty telling though, probably means we're using the priority labels - -wrong. - -<eae> We have a bunch of larger blink team level goals around bugs in - -Q4, we'll come back to that in a bit. - -<eae> Does a score of 0.6 sound reasonable? We did a little over half - -of as well as we set out but better for the bugs where it really - -matters. - -<leviw> Sounds about right. - -\[ Discussing "Reduce unnecessarily forced layouts" \] - -<eae> This was overly vague and we didn't really make any progress - -here. Plan to work with dev-rel to get a couple of examples of - -concrete cases where this is a problem on real world web sites and - -then make specific goals around that. - -<ojan> The goals should probably be around either reducing or making - -the layouts cheaper. - -<eae> That's a very good point, if we cannot avoid it than making it - -cheaper/more predictable is certainly a worthy goal. - -<eae> I'd score this as a solid 0.0. - -\[ Discussing "Add UMA tracking & monitoring for different types of layout" \] - -<eae> This is the work than Ben started before he left the team. - -Dominik had signed up to take it on but he was oversubscribed last - -quarter and this was deemed the lowest priority. Will carry over and - -could use a new owner. - -<eae> Score: 0.0 - -\[ Discussing "Brainstorm/plan devtools/rail score/layout integration" \] - -<eae> We have some ideas here but implementation is blocked on the - -actual rail integration into dev tools. This goal was about coming up - -with ideas and thinking about what we might want to include, things - -like forced layouts, layout costs etc. - -<eae> Score 0.4 - -\[ Discussing "Trace layout on some popular websites in US, Europe, - -Brazil, India" \] - -<eae> We held a number of rather productive tracing parties in MTV, - -SFO and WAT. Very useful and something we should continue doing. - -<eae> Score 0.8. - -\[ Discussing "Spin up effort around spatial" \] - -<ojan> We spun up an effort. Most of the work is pretty low priority. - -Have roadmap but it hasn't been staffed as it isn't considered to be - -super high priority at the moment. We don't want to starve other - -efforts. - -<ojan> There is a set of use cases about where things are on a page, - -mostly about delay loading things not on the screen. Other things on - -the list include the CSS contain property, Will sent out a list. There - -are a few smaller things. - -<ojan> Mostly a bunch of P2 work, nothing that we HAVE to do next - -quarter but if we don't do any then next year we'll be in a really sad - -state. - -<eae> Spun up, 1.0. - -<eae> Thanks everyone. Before we start talking about Q4 goals let's - -take a moment to think about things we did particularly well or - -particularly bad. - -\* silence \* - -<eae> Please, don't all speak at once. - -\* further silence \* - -<ojan> I think that the steady progress we made on reducing the bug - -count and fixing important bugs was great. - -<szager> I like that we keep our weekly meetings short and to the - -point. Is around 15 minutes which is about perfect. - -<szager> It's been nice having people from other offices come up to SF - -every now and then. Would be great if we could coordinate that better. - -<leviw> We have BlinkOn coming which is a great excuse for everyone to - -hang out here for a few days. - -<skobes> Is that in SF? - -<leviw> Yes, it was just announced. - -<eae> Christian will be in SF for the full week of BlinkOn, as will - -Dominik. He'll also be there the week before. Not sure about Koji yet. - -Always great to have everyone in the same room. Especially given how - -distributed we are. - -\[ Discussing "Q4 OKR Ideas & Suggestions" \] - -<eae> Let's move on. It sounds like we want to continue the flexbox - -work, right Christian? - -<cbiesinger> Yes. - -<eae> And continue on fullscreen, bokan has recently signed up to take - -that over. - -<jchaffraix> Right, he'll take it over from Dan. Dan is about to land - -his big fullscreen fix which is really exciting. - -<eae> We should have an item about houdini. - -<leviw> I put a tentative okr in there, should get Ian in on that - -conversation. Will follow up. - -<eae> Stefan, do you still want to drive the hyphenation work? We've - -had a couple of meetings with the Android team and it looks like we'll - -do a push to add hyphenation support and better line breaking in Q1. - -Q4 is too much of a push. We'll still need to do some design work and - -work with the Android text team in Q4 however. - -<szager> Sounds sane, hyphenation is the number one user request in - -Germany. Q1 sounds good, I'm fine with doing the required design work - -in Q4. - -<skobes> How about other browsers, do they all support hyphenation? - -<leviw> All other browsers support it. We had some support but ripped - -it out after the fork from WebKit. - -<eae> Finish root layer scrolling? - -<skobes> Yup. - -<eae> Do you think we could finish it in Q4 or will it carry over into Q1? - -<skobes> Think so. - -<eae> Another idea we've been toying with is reimplementing ruby on - -top of custom layout. - -<jchaffraix> Isn't that blocked on implementing custom layout? - -<eae> The idea is to use the internal API we've been working on and - -then develop it in conjunction with the API. That way we ensure the - -validity of the API. - -<eae> To be clear, this goal is not about _shipping_ a custom layout - -based ruby implementation. It's about seeing if it is feasible to use - -some of the custom layout APIs to implement it internally and then, if - -it is a successes, we'll see about shipping it. Would be nice if we - -could as the current ruby implementation is a bit of a mess and isn't - -complete. If we need to reimplement it I'd rather do it in a - -extensible way. Having a custom for custom layout would be nice. - -<eae> Next up, remove simple text. It's all about the rebaselines. - -<eae> Font fallback, continue shaper integration and pref fonts and - -system fallback improvements. Falls on Dominik and he wants to - -continue this work. - -<eae> As for bug health we've had a number of discussions in the - -larger blink team and we've agreed to some common goals. What it comes - -down to for us is the following: - -- Continue to triage all bugs within one week - -- Fix all (new) P0/P1 within one release - -- Reduce untriaged bug count by 50% - -- Reduce total bug backlog by 15% - -<eae> The two last goals are ambitious but doable. - -<jchaffraix> I'll be helping with bug triage in addition to documentation. - -<eae> Thanks Julien! We should also make sure to have a goal around - -documentation. - -<jchaffraix> For those that haven't been following along, I've been - -adding google style class level comments documenting the design and - -implementation details for many of our core classes. - -<leiw> I have a very long bug list, if we triage by just assigning - -them I'll have an even longer list. That's not very helpful. Might - -make more sense to have a bucket or label of sorts rather than - -assigning more bugs? - -<ojan> Does triage imply assignment? - -<eae> No - -<ojan> The way it used to work is that assigned means it's something - -you will work on in the next week or so. Used to be standard practice - -on Chrome, not any more. We should move back to it. - -<leviw> I don't mind having them assigned, for these specific bugs I'm - -a good fit and the right person to work on it. - -<ojan> cc:ing would be fine for that, no? - -<leviw> Yeah, should be fine. Hard to prioritize, I work off things - -that are assigned to me. - -<szager> I also think that, we use bug tracker for work items, bugs - -and feature requests are intermingled. - -<ojan> Sorry to derail the discussion, we could talk about this offline. - -<eae> Not at all, this is super useful. We need to understand what - -triage means and come up with a way to handle the backlog. - -<ojan> How about we add a set of hot-lists or labels to help with this - -without giving an illusion of forward progress? - -<leviw> Would make me feel less like I'm drowning in bugs. Would be -helpful. - -<skobes> I have the same problem with text auto size bugs, mix of - -assigned and watching label. There are too many for me to look at, - -need way to filter. - -<ojan> How about you use a label for this? like -"important-text-autosizing". - -<skobes> How about two separate triage passes, one to delegate and one - -to set priority? - -<eae> As for priority we need to have a team wide definition of what - -P1 vs P2 vs P3 means, today P1 is essentially for blockers, P2 for - -everything else and P3 means it'll never be looked at. Dru is driving - -an effort to define the priorities. - -<eae> We should continue this discussion and see what we can do to - -make this work better. - -<ojan> Who should drive this? - -<eae> any volunteers? - -\* crickets \* - -< jchaffraix> I'm fine volunteering a little but seems to big for one -person. - -<ojan> Might not need a formal owner. - -<leviw> Let's try a few things and sync back in a month. - -<ojan> Great, once we have something that works we can expand to - -larger blink team. This is a team-wide problem but fixing it probably - -needs to start in the sub-teams. Grassroots. - -<eae> Let's talk about RAIL and the work we'd like to do in that space. - -<eae> Implement CSS containment from Ojans spatial list seems like a - -good candidate. Question is how to prioritize. Do you want to give a - -sixty second summary Ojan? - -<ojan> Sure, it's a feature where you can say contains: and a bunch of - -values. Specifies that a div fully contains all of its children. No - -position absolute can escape, no overflow outside the div. Also - -doesn't auto-size. What this allows us to do is when you hit a contain - -thing, if it's outside the screen, you can completely ignore doing - -layout on the children. Might not even need style recald and certainly - -no layout. - -<ojan> Today you cannot do that without detailed knowledge of the - -children. It's our proposal, it's has gone through the working group - -and is ready to implement. Mozilla is about to start implementing it. - -<ojan> Skipping style recalc work is tricky but possible. Skipping - -layout is easy. - -<ojan> V1 would not do the majority of optimizations, would implement - -the correct behavior (no auto-size, reset list numbering, clip - -content), Super easy. Small amount of work. The only optimization - -would be the subtree layout root. Plugging in to existing system. - -Easy. Get performance benefit form that. In future quarters we could - -plug in more performance work. As web devs get aboard we get more - -value from doing the performance work. - -<ojan> Useful for delayed loading, infinitive list etc. Also useful - -for things like text editors where typing in a text box doesn't - -trigger layout for the full page. Only the text area. - -<skobes> Positioned content? - -<ojan> Changes behavior. Performance wise, nothing bad will happen. - -<skobes> What if we have a lot of subree layout roots? - -<ojan> Might require some fixes on our side, i.e. not having a flat - -structure. Work should be guided by usage. Also, as you cannot have - -inlines or auto sizer for this it naturally limits the places it can - -be used. - -<ojan> Not a p1, new feature. Helps in short term in building - -libraries. Long game. - -<eae> Also not much work, would be good to get started given the long - -term goals and benefits. - -<ojan> It's the one big thing I want to do from spatial in Q4. - -<eae> Do you want to talk about smooth scrolling Steve? - -<skobes> This is one of chromes oldest bug, issue 575, every other - -browser has had this for a long time. - -<eae> Do we have the pieces? Can we do this? - -<skobes> All pieces are in place, doable in Q4. - -<eae> Let's do it! - -<eae> Finally, we should have a goal around forced layouts. Will - -discuss specifics with devrel and come up with a set of concrete goals - -that we can iterate on. Paul mentioned requesting window size as one - -candidate. - -\[ Wrapping up \] - -<eae> Anything on this list you think we should _NOT_ be doing? - -<szager> Maybe the rail work should be prioritized. Was mentioned last - -but seems like the most important. - -<eae> Ordering not indicative of priority, agree that it's one of the - -top priorities. - -<eae> How about the other way around, anything we should be doing that - -we haven't talked about? - -<wkorman> Flipped box writing mode that Levi and Ojan talked about? - -<wkorman> The proposal to unprefixing vertical writing mode triggered - -a discussion where some of the paint folks where saddened by the - -complexity of vertical wiring mode combined with RTL combined with - -flipped blocks. Could we simplify this around a sane path. Starting - -thinking about it. - -<eae> RTL isn't too bad but the others are a bit of a mess, also a - -combinatorial explosion. - -<leviw> Can't do much about RTL due to UBA, flipped blocks and - -vertical writing mode shouldn't be as much overhead though. - -<leviw> I think for somebody that would be a fun project to re-think. - -<wkorman> Flipped blocks and vertical writing mode. - -<leviw> Make it not suck. - -<ojan> Please include me in the discussion. - -<wkroman> How about document life cycle? - -<leviw> I don't think anyone has worked on that in a long time. - -<ojan> Mostly blocked on paint team, mostly compositor related. - -Slimming paint v2. - -<wkorman> There are some comments along we can come back to this node - -multiple times, surprising but ok. We should fix these things and - -enforce lifecycle. Editing code in particular is really quite bad. - -Fixing might invoke adding another phase to the life cycle. - -<leviw> Not a new phase, push computing rect until end of operation. - -Could potentially do less work. - -<wkorman> What about your high dpi work? - -<eae> Captured in the windows teams OKRs, my involvement is mostly - -advisory at this point now that we've decided on the design and - -integration. Implementation is handled by the windows team. - -<eae> Thanks everyone. I'll be following up with each one of you - -offline over the next week or two.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/index.md deleted file mode 100644 index aaeb7fa5d05..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/index.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -page_name: meeting-notes -title: Layout Team Meeting Notes ---- - -Meeting notes in reverse chronological order: - -* [Monday, August 29, - 2016](/teams/layout-team/meeting-notes/monday-august-29-2016) -* [Monday, July 18, - 2016](/teams/layout-team/meeting-notes/monday-july-18-2016) -* [Monday, June 27, - 2016](/teams/layout-team/meeting-notes/monday-june-27-2016) -* [Monday, June 6, - 2016](/teams/layout-team/meeting-notes/monday-june-6-2016) -* [Monday, May 16, - 2016](/teams/layout-team/meeting-notes/monday-may-16-2016) -* [Monday, April 25, - 2016](/teams/layout-team/meeting-notes/monday-april-25-2016) -* [Monday, April 11, - 2016](/teams/layout-team/meeting-notes/monday-april-11-2016) -* [Monday, April 4, - 2016](/teams/layout-team/meeting-notes/monday-april-4-2016) -* [Monday, March 28, - 2016](/teams/layout-team/meeting-notes/monday-february-28-2016) -* [Monday, March 21, - 2016](/teams/layout-team/meeting-notes/monday-february-21-2016) -* [Tuesday, March 15, - 2016](/teams/layout-team/meeting-notes/tuesday-march-15-2016) -* [Monday, March 7, - 2016](/teams/layout-team/meeting-notes/monday-march-7-2016) -* [Monday, February 29, - 2016](/teams/layout-team/meeting-notes/monday-february-29-2016) -* [Monday, February 22, - 2016](/teams/layout-team/meeting-notes/monday-february-22-2016) -* [Tuesday, February 16, - 2016](/teams/layout-team/meeting-notes/tuesday-february-16-2016) -* [Monday, February 8, - 2016](/teams/layout-team/meeting-notes/monday-february-8-2016) -* [Monday, February 1, - 2016](/teams/layout-team/meeting-notes/monday-february-1-2016) -* [Monday, January 11, - 2016](/teams/layout-team/meeting-notes/monday-january-11-2016) -* [Monday, January 4, - 2016](/teams/layout-team/meeting-notes/monday-january-4-2016) -* [Monday, November 30, - 2015](/teams/layout-team/meeting-notes/monday-november-30-2015) -* [Monday, November 23, - 2015](/teams/layout-team/meeting-notes/monday-november-23-2015) -* [Monday, October 19, - 2015](/teams/layout-team/meeting-notes/monday-october-19-2015) -* [Monday, October 12, - 2015](/teams/layout-team/meeting-notes/monday-october-12-2015) -* [Monday, October 5, - 2015](/teams/layout-team/meeting-notes/monday-october-5-2015) -* [Friday, October 2, - 2015](/teams/layout-team/meeting-notes/friday-october-2-2015) (Q3/Q4 - OKRs) -* [Monday, September 28, - 2015](/teams/layout-team/meeting-notes/monday-september-28-2015) -* [Monday, September 14, - 2015](/teams/layout-team/meeting-notes/monday-september-14-2015) -* [Monday, August 31, - 2015](/teams/layout-team/meeting-notes/monday-august-31-2015) -* [Monday, August 24, - 2015](/teams/layout-team/meeting-notes/monday-august-24-2015) -* [Monday, August 17, - 2015](/teams/layout-team/meeting-notes/monday-august-17-2015) -* [Monday, August 10, - 2015](/teams/layout-team/meeting-notes/monday-august-10-2015) -* [Monday, August 3, - 2015](/teams/layout-team/meeting-notes/monday-august-3-2015) -* [Monday, July 20, - 2015](/teams/layout-team/meeting-notes/monday-july-20-2015) -* [Monday, July 13, - 2015](/teams/layout-team/meeting-notes/monday-july-13-2015) -* [Monday, June 22, - 2015](/teams/layout-team/meeting-notes/monday-june-22-2015) -* [Tuesday, June 16, - 2015](/teams/layout-team/meeting-notes/tuesday-june-16-2015) -* [Monday, June 8, - 2015](/teams/layout-team/meeting-notes/monday-june-8-2015) -* [Thursday, June 4, - 2015](/teams/layout-team/meeting-notes/thursday-june-4-2015) (Q2 OKR - mid-quarter check-in) -* [Monday, June 1, - 2015](/teams/layout-team/meeting-notes/monday-june-1-2015) -* [Thursday, May 28, - 2015](/teams/layout-team/meeting-notes/may-28-2015) (Layout Moose - post BlinkOn Sync Up) -* [Tuesday, May 26, - 2015](/teams/layout-team/meeting-notes/tuesday-may-26-2015) -* [Monday, May 4, - 2015](/teams/layout-team/meeting-notes/monday-may-4-2015) -* [Monday, April 27, - 2015](/teams/layout-team/meeting-notes/monday-april-27-2015) -* [Monday, April 20, - 2015](/teams/layout-team/meeting-notes/monday-april-20-2015) -* [Monday, April 13, - 2015](/teams/layout-team/meeting-notes/monday-april-13-2015) -* [Monday, April 6, - 2015](/teams/layout-team/meeting-notes/monday-april-6-2015) -* [Thursday, April 2, - 2015](/teams/layout-team/meeting-notes/thursday-april-2-2015) (Q1/Q2 - OKRs) -* [Monday, March 30, - 2015](/teams/layout-team/meeting-notes/monday-march-30-2015) -* [Monday, March 23, - 2015](/teams/layout-team/meeting-notes/monday-march-23-2015) -* [Monday, March 9, - 2015](/teams/layout-team/meeting-notes/monday-march-9-2015) -* [Monday, March 16, - 2015](/teams/layout-team/meeting-notes/monday-march-16-2015) -* [Monday, March 9, - 2015](/teams/layout-team/meeting-notes/monday-march-9-2015) -* [Monday, March 2, - 2015](/teams/layout-team/meeting-notes/march-2-2015) -* [Monday, February 23, - 2015](/teams/layout-team/meeting-notes/monday-february-23-2015) -* [Wednesday, February 18, - 2015](/teams/layout-team/meeting-notes/wednesday-february-18) (Q1 - OKR mid-quarter check-in) -* [Monday, February 9, - 2015](/teams/layout-team/meeting-notes/monday-february-9) -* [Monday, February 2, - 2015](/teams/layout-team/meeting-notes/monday-february-2) -* [Wednesday, January 7, - 2015](/teams/layout-team/meeting-notes/20150107) (Q1 OKRs) -* [Tuesday, December 9, - 2014](/teams/layout-team/meeting-notes/20141209)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/march-2-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/march-2-2015/index.md deleted file mode 100644 index bfc04e53d86..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/march-2-2015/index.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: march-2-2015 -title: Monday, March 2, 2015 ---- - -We had three new people joining the meeting this week: -- Mark Pilgrim (pilgrim) -- Works on Blink in Chapel Hill. Much of his recent work falls under -code-health and Project Warden. -- Nate Chapin (japhet) -- Works on Blink in Mountain View. Working on low-level blink platform -code cleanup and resource handling. -- Walter Korman (wkorman@google.com) -- New to the Blink team in SF, transfer from Glass. Getting up to -speed on Blink. Not sure which sub-team he'll end up on yet. -Updates since last meeting (on Monday, February 23rd): -Performance Tracking (benjhayden) -- Working ob exporting diagnostic information for performance tracking. -Scrolling (skobes) \[crbug.com/417782\] -- Mostly understand the issues around fixed position. - -- Dealing with layout tests failures and fallout. -Rename Rendering -> Layout (dsinclair) \[crbug.com/450612\] -- Massive RendereBlock to LayoutBlock change landed, touched 50k+ files! -- Plan to move RenderLayer and Renderer this week. -Measure API (jchaffraix) -- Addressed comments and concerns in Measure API proposal, started -circulating and soliciting feedback. -- Working on typing information and fragments this week. -Line Boxes (hartmanng, szager) \[crbug.com/321237\] -- Back to work on layout unit conversion, working on text rendering and -going through test failures fixing poorly written tests and getting -rid of float imprecision type failures. -Flexbox (cbiesinger) \[crbug.com/426898\] -- Working on updating flexbox implementation to match latest spec -revision. One of the changes involves rolling out a two year old CL -that removed a feature that has since been re-added to the spec. -- Estimate another two weeks of work. -Isolate core/fetch (japhet) \[crbug.com/458222\] -- Working on isolating core/fetch from the rest of core. Currently -touches frame and document which it probably shouldn't. -Blink componentization (pilgrim) \[crbug.com/428284\] -- Moving things from core to modules; core/storage and core/timing. -Text (kojii, wjmaclean, eae) -- Started looking into text iteration code in detail, discovered that -BitStack has been incorrect since day one. (wjmaclean) -- Cleaning up text iteration code. (wjmaclean) -- Continued work on HarfBuzz normalization performance improvements, -CL ready but blocked on perf numbers. -- Performance work for complex path with eae and Dominik. (kojii) -- 5-9% gain for CJK text landed. -- 3-4x gain for all languages close to land. With this we should be -pretty close to match the performance of the simple text path for -vertical text. -- Exploring a few more ideas. -- Added shared shaper base class to ease the transition to the complex -path. (kojii) -Page scale handling (bokan) \[crbug.com/459591\] -- Auditing window vs frame coordinates. -Assertions/Regressions/blocking bugs -- Working through list of ClusterFuzz assertions (cbiesinger). -- Dealing with Mac core text crashers/blockers. (eae) -- Help with git repository merge work. (szager) -- Looking at regression relating to document life-cycle. (walterkroman) -Misc -- Dealing with fallout from --dump-render-tree rename, heated discussion -following deprecation CL, will send out mail to blink-dev and -coordinate with eae. (paulmeyer) -- Helping philipj at Opera with syncing IDLs. (jsbell)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/may-28-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/may-28-2015/index.md deleted file mode 100644 index 915515c1143..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/may-28-2015/index.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: may-28-2015 -title: 'Thursday, May 28, 2015: Layout Moose post BlinkOn Sync Up' ---- - -a.k.a. the project formerly known as "the grand layout re-factoring" and briefly -as "layout slimming" - -Attendees: eae, leviw, esprehn, jchaffraix, ojan, cbiesinger, dsinclair - -<eae> Thanks for organzing Levi, I'd like to get a quick update, hear -concerns and discuss logistics. - -<jchaffraix> I'm concerned about a lack of transparency, meeting notes not -getting out and key people being excluded from meetings. - -<ojan> Been meaning to send out notes from BlinkOn sessions, oversight -that they weren’t. Not intentioanlly exlcuding anyone. - -<ojan> How do we ensure everyone’s on board? - -<eae> I’ve stayed out of the technical part of the discussion to avoid -having yet another cook in the kitchen. Now I want to make sure we have a plan, -circulate it, and ensure we’re moving forward. - -<jchaffraix> We need to ensure we have a concrete roster and include all -steakholders. - -<eae> We have that. - -<ojan> We just didn’t have a chance post-BlinkON to send out the notes. We -weren’t trying to be exclusive. - -<ojan> Dan, it sounded like maybe you wanted to be included too? - -<dsinclair> I’m interested because it seems like the future, but couldn’t -go to the meetings because of timezones. - -<ojan> Sydney + Waterloo is hard. - -<esprehn> Ian K will be moving here so we won’t have to keep having Sydney -time zone involved. - -<ojan> For future reference voice if you want to be involved. I’ll try to -keep sending emails to layout-dev to tell people ahead of time when there will -be meetings. - -<eae> Things will be easier when discussion go from being predementantly -brainstorming and turn into more of a concrete plan. Circulating an actual -design will help guide the discussion. - -<ojan> Let me summarize our discussions and current thinking: - -- There are a certain set of features we want to achieve (measure, fragments, -async append). - -- All these have require things that are hard to do in the current codebase - -- We also want more sanity and understanding in the codebase. - -- We took our brainstorm and turned it into a slightly more concrete set of -proposals (v1, v2, etc.) - -- Added psuedocode - -- Result proves some of our ideas, but not necessarily the feasibility of the -approach. - -- Doc still isn’t really ready for external consumption - -- Next step is to put current box layout code behind an API, then there’s the -controversial step of re-implementing that api behind a flag. - -- Unsure of the sense of time required here (somewhere between 3 months and 3 -years). - -- Important to see the API requirements ahead of time to understand. - -<esprehn> Implementing the various box layout algorithms is a relatively -easy exercise. - -<ojan> We all agree what the first step is an API. We should do that then -see about next steps. - -<jchafrraix> We don’t \*need\* that API. - -<eae> We don't but I think we want it regardless. - -<jchaffraix> Do we really want to put this in the critical path since -we’re now gating everything on this? - -<eae> It fits with our overall goals of a layered platform and it isn't -necesarrily gating other work. Other than opertunity cost of work we could be -doing instead. - -<esprehn> This will allow us to enforce sanity. - -<jchaffraix> You don’t need to sell me on the API. My point is whether or -not this should be the priority. - -<eae> That is a discussion for our OKR meetings. We don't need to resolve -that here today. - -<ojan> What happened in Sydney was that we had had a hackathon meeting -where we started working on a Line Layout API. It’s possible that we’ll get -1/3rd the way through this and decide that it doesn't work and have to start -over. We ended up with a patch that moves a handful of Line Layout accessors -into the box tree into an API. - -<esprehn> We should do Paint next. - -<ojan> My perspective is the next step is to get someone to own the line -layout api patch and get it landed. - -<jchaffraix> It seems odd we’re not designing this api, but just grabbing -the things we’re using. - -<leviw> Designing it is step 2. - -<ojan> We didn’t know exactly what methods are currently in use. The next -step is refactor how the API is used and make it sane. - -<eae> Next thing I'd like to see is a 1-pager of our plan, shared with -layout-dev, and a high level overview of what we want in terms of an evental -API. - -<ojan> That’s hard to plan ahead of time, we don't know what the API is -going to look like it. - -<eae> This could be a living document, maybe that section is blank to -start. Having a document would be super useful as would having an owner. - -<ojan> Someone should draft this document and share it around. - -\* ojan stares at levi \* - -\* levi is volunteered \* - -<eae> Assuming this is something we want to work on in Q3, we should have -this document ready in the next couple weeks. It would also be useful to have -something like this for the “v2 rewrite the world” approach. - -<ojan> On my todo list is to take the doc we have today and turn it into -something an outsider can read. - -<eae> Great! Current doc unreadable unless you where in all the meetings. -Would be useful to have something more concise. - -<ojan> Seperate tasks (from nduca); taking all our layout-related -rendering leads items and drawing a chart that tells us what we need to do to -implement all of them. Here’s this proposal that let’s us do them, here’s what -it would take to do it incrementally and how long, etc. - -<eae> I agree but having the API doc is the highest properity for me. - -<esprehn> Boundaries would exist between layout, paint, dom, editing APIs. -Woudln’t be super disruptive. Then we’d have a real list of where we’re actually -interacting with the layout tree. - -<dsinclair> Sounds like someone else will own all clusterfuzz bugs -- -hooray! - -\* everyone hooray! We haz plan! \* - -<eae> As for the API document, I'd really like to see it ready for -circulation in the next week or two to allow it to be circulated and reasoned -about in time for setting the Q3 OKRs. - -\* eae looks at Levi \* - -<leviw> This shouldn’t block anything. - -<ojan> Mark pilgrim would be a good guy to run with the layout stuff once -it’s started. - -<ojan> I keep hearing people say “Should I not do this because Moose” and -I say Noooooooooooo. - -<leviw> Ties in with much of our, and Dans, previous work. Should not -block. - -<dsinclair> Do we know what all our API boundaries are? - -<ojan> We know the big ones. We don’t necessarily need to know \*all\* of -them. (line, paint, dom, editing) - -<esprehn> Chris says they’re aiming for 45-46 to rip out paint stuff. Is -optimistic. Hope that by December we should be able to take out tons of -compositor-related stuff. Shouldn’t focus on that api surface. Editing will be -so gross we’ll have plenty to do without the compositor. - -\* levi makes moose noise \* - -<eae> That’s a wrap!
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-11-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-11-2016/index.md deleted file mode 100644 index 356c4185d97..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-11-2016/index.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-11-2016 -title: Monday, April 11, 2016 ---- - -Updates since last meeting (on Monday, April 4, 2016): -Scrolling -- Focus on root layer scrolling for now. The top most element, the -layout view, (frame view contains layout view, both are scrollable -areas. Frame view has special magic, plan is to have LayoutView handle -scrolls using the standard ScrollableContainer logic. Been ongoing for -awhile, skobes has done most of the work but has been pulled into -other things. (szager) -CSS Flexbox (cbiesinger) -- Spent way too much time on scrolling and will have to spent more time -on scrolling. Still haven't found a good solution, trying to move -scroll clamping to after the layout phase. -- Landed a few cleanup patches. -- Focus on other flexbox issues this week. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Fixed multicol assertion failures. (mstensho) -- Improved the forced fragmentainer break implementation: Only allow -those at class A break points. (mstensho) -<https://drafts.csswg.org/css-break/#possible-breaks> -CSS Houdini -- Last week got custom paint end to end working, out for review. -(ikilpatrick) -- Working on style invalidation this week. (ikilpatrick) -- Next up, spec stuff for houdini. (ikilpatrick) -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- As promised, spent last week working on layout view. Migrated callers -to use the new block layout API (LayoutViewItem). (pilgrim) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- mstensho getting up to speed. -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- No updates since last week - -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Intersection observer on by default in M51. Yay! (szager) -Text (eae, drott, kojii) -- Attended Edge Summit, interesting discussion on potential underlying -issue with system font cache. (drott) -- Submitted Conference Abstract to 40th Unicode Conference. (drott) -- Worked with dpranke@ to get hb-ot-font linkage issue out of the way, -and landed hb-ot-font change. (drott) -- Continued work on Small Caps Implementation. (drott) -- Started looking into hyphenation support and sent out a outline for -a implementation proposal. (kojii) -- Added comma and dot segmentation for shaping cache in order to fix -a perf regression for minimized js in devtools. (eae) -Logistics: -- skobes out until end of the month. -- leviw leaving the team and Blink in a month. Will be trying to offload -knowledge and transfer ownership. Get your questions and code reviews -in while you can!
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-13-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-13-2015/index.md deleted file mode 100644 index 9f00a52caac..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-13-2015/index.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-13-2015 -title: Monday, April 13, 2015 ---- - -Performance Tracking (benjhayden) - -- LayoutAnalyzer-based UMA histograms. - -- Benchmark metric work. - -- Made progress understanding bug 369123 (Absolute position and display: - -inline-block are order-dependant) - -- Experimenting with data-mining traces - -First letter refactoring (dsinclair) -\[[crbug.com/391288](http://crbug.com/391288)\] - -- Fixed bug where a block and an inline both used first-letter. - -- Fixed bug where changing the text content didn't updated the layout - -resulting in the first-letter disappearing. - -- Broke first-letter hit testing while trying to fix the same. Added a - -bunch of new tests for hit testing pseudo classes. - -Measure API (jchaffraix) - -- Working on proposal/brainstorming document for layout refactoring. - -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Added check to ensure that min-size cannot be negative. - -- Changes to bring min-width auto up to spec in review. - -- Working on positioning of position: absolute elements. - -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] - -- Eliminating wrapper classes helped improve performance but there is - -still a performance regression. - -- Trying to figure out the right place to draw the line between floats - -and layout units. Text metrics still uses (and will continue to use) - -floats, box layout uses (and will continue to use) layout units. - -Doing most text metric in floats and converting at the boundary - -between the block and inline trees might make sense. - -Isolate core/fetch (japhet) \[[crbug.com/458222](http://crbug.com/458222)\] - -- Continuing work to isolate core/fetch from the rest of core. - -RenderObject cleanup (pilgrim) \[[crbug.com/436473](http://crbug.com/436473)\] - -- Continuing to pull things out of RenderObject. - -Text (kojii, eae) - -- Started work to improve caching for complex text shaping results. - -(eae) - -- Running/writing tests to check where we are; in some cases complex - -text is already faster than simple text. In others it is up to 5x - -slower. (eae) - -- Worked on CSS Writing Mode test suites with contributors. (kojii) - -Misc Warden - -- Cleaning up bindings, replacing custom bindings with auto-generated. - -(jsbell) - -- Started to plan storage type cleanup. (jsbell, pilgrim)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-20-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-20-2015/index.md deleted file mode 100644 index 9ec50661498..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-20-2015/index.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-20-2015 -title: Monday, April 20, 2015 ---- - -Performance Tracking (benjhayden) -- Audit trace view for layout analyzer. -- Split LayoutAnalyzer::LayoutBlockRectangleChanged into X/Y/Width/ -HeightChanged. -- LayoutTreeAsText as JSON. -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] -- Crashing bugs, fixed use after free in FrameView. -- Issue with the interaction between painting the viewport and view -scrolling. -- Don't force layout for scrollTo(0, 0). (rune) -List marker refactoring (dsinclair) -\[[crbug.com/370461](http://crbug.com/370461)\] -- List element pseudo elements, marker inside wasn't getting the -correct side for the parent container, need to notify parent. -- Found issue where if you modify the subtree you may need to reinsert -the elements as it needs to be in a specific place of the tree, i.e. -inside a form element. -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Landed min-width auto, handful of regressions as expected, burning -down one by one. -- Identified a performance regression, computeLogicalWidthUsing is -slow, caused a 25% slowdown for flexbox as it calls the compute -method more frequently. Have a fix that should be landed by now. -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] -- Going after perf regressions. Got a CPU profile and did some work to -allow perf tools to run on render process only in multi process -chrome. -- Have made progress on performance, still some regressions for floats. -Blink componentization (pilgrim) \[[crbug.com/428284](http://crbug.com/428284)\] -- Slimming down render object (aka layout object), expect to continue -this week. -Text (eae, rune) -- Started work on implementing a word-cache for complex text shaper, -first step is to add unit tests for existing and desired behavior. -(eae) -- Don't clear FontFaceCache if no @font-face were removed. (rune) -Style resolution (rune) -- Various selector matching issues. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- New multi-col implementation was reverted due to clusterfuzz issues, -working on identifying and fixing the potential problems. Aim to -re-land before the end of the week. -Layout refactoring -- jchaffraix, esprehn, ojan working on coming up with concrete proposals -for changes to how we do layout based on ideas and concepts from the -last few weeks of discussions on the topic. Will be shared with wider -blink team.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-25-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-25-2016/index.md deleted file mode 100644 index 01fd098edde..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-25-2016/index.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-25-2016 -title: Monday, April 25, 2016 ---- - -Updates since last meeting (on Monday, April 11, 2016): -CSS Flexbox (cbiesinger) -- Flexbox bug triage and bug fixes. Unrelated to scrolling for a change -(bug 576202, bug 341310, bug 375693). -- Ramping back up on scrolling, trying to help cbiesinger with flexbox -overflow:auto heartache. Lots of fun. (szager) -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- Reviewing CSS Grid specification. (cbiesinger) -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Continuing to focus on multi-col and fragmentation. -- Orphans and widows, need to clean up this code, to support -break-before & break-after. -CSS Houdini -- Waiting on codereivews for CSS Paint API. (ikilpatrick) -- Begun work on spec stuff, cleaning up paint, worklets. Starting to -work more on CSS Layout API. (ikilpatrick) -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Migrated most references of Document::layoutView() to Document:: -layoutViewItem() in preparation for removing Document::layoutView() -and routing everything through the block layout API. (pilgrim) -- Migrating references to the layoutBlockView on document, and move to -item. (pilgrim) -- Start the LineLayoutAPI document with leviw. pilgrim, dgrogan to -clustering all the API methods into groups, figuring out we want -to rationalize these roots. (dgrogan) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- No updates since last week - -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Sent out Intent to Ship. (eae) -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Wrapped up most Intersection Observer work, merged a patch into -M51. (szager) -Tables (dgrogan) -- Table layout refactor, putting out fires with patch going to stable. -- Working through list of highly starred table bugs. -- Much digging into tables for <https://crbug.com/427994> and -<https://crbug.com/178369> which are different but related issues. -mstensho has been consulting. -Text (eae, drott, kojii) -- Continued to work on font-variant-caps, blocked on rebaseline bot -being offline. (drott) -- font-variant property into a shorthand, CL up for review. (drott) -- Contributed to Koji's document on implementation/shipping plan for -hyphenation. (drott) -- Implemented font-variant property parsed as CSS shorthand (as opposed -to being a CSSPrimitive Value before), working well. Font-variant now -accepts font-variant-ligatures and font-variant-caps values, and -combines synthetic small caps with ligatures \\o/. Up for review. -(drott) -- Fixed bug where we sometimes omitted tab characters to due incorrect -rounding in LineWidth::snapUncommittedWidth. (eae) -- Fixed crash in Font::computeCanShapeWordByWord. (eae) -- Fixed handling of very large transforms in ContainerNode::boundingBox. -(eae) -Logistics: -- cbiesinger is now a core OWNER, congratulations! -- skobes out until end of the month. -- eae in Tokyo until end of week, Zurich next week. -- drott in Zurich next week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-27-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-27-2015/index.md deleted file mode 100644 index 0df760d7c75..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-27-2015/index.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-27-2015 -title: Monday, April 27, 2015 ---- - -Performance Tracking (benjhayden) - -- Preliminary LayoutAnalyzer-powered UMA findings. A few surprises - -already, lots of opportunity for further analysis and more data. - -- Working on LayoutTree trace object snapshots and various - -LayoutAnalyzer improvements. - -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Reviewed bokan's RootFrameViewport change, and investigated a - -background painting issue with root layer scrolling + slimming paint - -(trchen is now working on a fix). - -- Plan to work on testing root layer scrolling on Android this week. - -Looking at failing layout tests related to fractional scroll offsets. - -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] - -- Continued work on line layout LayoutUnit conversions. Have a patch - -that sets the barrier between float and LayoutUnit at the InlineBox - -level, which seems like the sensible place. - -- There is still a performance regression that I haven't been able to - -eliminate. Was able to get some small performance wins by looking at - -profiling data, but I've hit a wall with that approach. Will discuss - -next steps and come up with a plan this week. - -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- More flexbox updates. - -- Trying to get answers to flexbox spec questions, was promised answers - -this week. - -List marker refactoring (dsinclair) -\[[crbug.com/370461](http://crbug.com/370461)\] - -- Working on performance of list marker code. New version is slower - -then old version. html5-full-render on ToT was ~16.5 seconds for me, - -with ListMarkerPseudoElement is ~17.5 seconds. - -- Discussions this week on how to proceed with ListMarkerPseudoElement. - -Misc Warden (dsinclair, pilgrim) - -- Finishing work on decoratedName split, all annotations are moved - -over, just finishing off rebaselines. (dsinclair) - -- More renderer to layoutObject renames. (dsinclair) - -- Wrapped up selection gap clipping rework. (wkorman) - -- Working on slimming LayoutObject and pushing bits down to - -descendants. (pilgrim) - -Text (eae) - -- Added unit tests for complex text shaping (eae) - -Style resolution (rune) - -- Working on type selectors for SVG in HTML documents and picking up - -componentized style resolver work again. There is some question - -about whether the SVG bug is worth fixing. - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- Found a new crash. Maybe something changed on trunk. Will fix then - -reenable multi-col. - -Layout refactoring - -- esprehn, ikilpatrick, cbiesinger, ojan, leviw working on coming up - -with concrete proposals.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-4-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-4-2016/index.md deleted file mode 100644 index 816e576cd4c..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-4-2016/index.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-4-2016 -title: Monday, April 4, 2016 ---- - -Updates since last meeting (on Monday, March 28, 2016): -Short update this week as a lot of people are due to Edge conf. -Scrolling (skobes) -- Restored ScopedLogger. -- Continued to work on on getting ScrollAnchor to work during smooth -scroll animation. (skobes) -CSS Flexbox (cbiesinger) -- Fixed a scrolling bug, caused a small regression, looking into it now. -- Landed a work-around to allow DI into branch, have a better patch -that I'll keep working on this week. Currently breaks one of our -tests. -- Might be helpful to have scroll behavior better defined in spec. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No updates since last week - -CSS Houdini -- No updates since last week - -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Bunch of progress on layout view item, working on getting rid of -anything that touches LocalFrame and LayoutObject. Moving to new -shiny LayoutItem. (pilgrim) -- Have about ten files left, some pending review. (pilgrim) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Sent out hackathon report for initial review. (leviw) -- Started working on design doc. (eae) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- No updates since last week - -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Getting back into Intersection observer, dotting the i's and crossing -the t's before branch point on Friday, Have one significant patch to -land, today, hopefully. (szager) -- Figure out behavioral difference between actual implementation and -polyfill. (szager) -- Prep work for shipping. (szager) -Text (eae, drott, kojii) -- Looking into android memory regression with mixed success, getting the -tests working locally have proven to be quite challenging. Working -with the Chrome Android team to resolve. (eae, drott) -Misc -- Fixed crash in localCaretRectForEmptyElement. (eae) -Logisitcs: -- skobes out until end of the month. -- eae out Wed-Fri. -- drott, leviw, ikilpatrick at edge conf Mod-Tue.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-6-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-6-2015/index.md deleted file mode 100644 index 41b62c650d8..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-april-6-2015/index.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-april-6-2015 -title: Monday, April 6, 2015 ---- - -Most offices had the day off due to Easter so this update is limited - -to the SFO, MTV and NYC offices. - -Updates since last meeting (on Monday, March 30th): - -Performance Tracking (benjhayden) - -- About to land a LayoutMetric rewrite that should give more details. - -- Started working on LayoutAnalyzer UMA histograms after discussion - -with chrishtr. - -Scrolling (skobes) \[crbug.com/417782\] - -- Fixed a positioning bug affecting scrollToAnchor. - -Measure API (jchaffraix) - -- Started thinking about the grand block layout refactoring and smaller - -cleanup tasks that can be done in parallel. - -Flexbox (cbiesinger) \[crbug.com/426898\] - -- Working on positioning of position: absolute elements. - -- Working on importing w3c test suite for flexbox. - -Blink componentization (pilgrim) \[crbug.com/428284\] - -- Started working on moving clipboard from core to modules. - -Text (kojii, wjmaclean, eae, rune) - -- Removed incorrect optimization for fixed-pitch fonts. (eae) - -- Renamed SurrogatePairAwareTextIterator to UTF16TextIterator and added - -support for multi character glyphs which was previously handled separately. -(eae) - -Cleanup/code health - -- Removed canHaveGeneratedChildren from RenderObject and turned it into - -a static function. (pilgrim)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-10-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-10-2015/index.md deleted file mode 100644 index a8179f40eb9..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-10-2015/index.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-august-10-2015 -title: Monday, August 10, 2015 ---- - -Updates since last meeting (on Monday, August 3rd): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Fixed setPageSclaeFactor and anchor root layer scrolling. (skobes) -- Turned on scroll restoration tests for root layer scrolling. These -tests ensure that scroll positions are correctly restored on history -navigation. (skobes) -- A Samsung contributor has agreed to help with custom scrollbar work. -- Containing work cleaning up DepricatedPaintLayerScrollableArea in an -effort to have sane scroll bounds for the root layer. (szager) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Helped szager with a flexbox scrollbar bug that triggered unspeced and -untested behavior. -- Sent intent to ship and intent two unprefix and will follow up on -those this week. The intent to unprefix looks ready to go ahead with. -- Had meeting with tabatkins about absolute position for flex items. -- Flexbox bug triage. -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] -- Fixed bug where grid containers reported the wrong preferred width. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- First patch for nested multicol is just around the corner. -- Blocked on reviews for multicol improvements. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Successfully posted several API patches after help from Levi. Converted -several more bits of line box and descendants to use the new line -layout API. Nothing broken. yay! (pilgrim) -- Some weird edge cases and debugging code that relies on printing out -layout objects. Ongoing discussion. (pilgrim) -Text (eae, drott, kojii) -- Follow up from text workshop in Helsinki, Behdad and Drott working on -optimizing the Blink/HarfBuzz integration. -- Fixed space normalization bug where cr/lf characters where incorrectly -collapsed. (eae) -- Debugging several crashers in line layout. (eae) -Logistics: -- drott on vacation until Friday.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-17-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-17-2015/index.md deleted file mode 100644 index 7e40f264dff..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-17-2015/index.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-august-17-2015 -title: Monday, August 17, 2015 ---- - -Updates since last meeting (on Monday, August 10th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Moved scrolled-by-user flag out of FrameView. (skobes) -- Custom scrollbars are now working with root layer scrolling. (skobes) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Got go-ahead to unprefix intrinsic sizing keywords (min-content, -max-content, fill and, fit-content). Will go ahead and unprefix all -but fill (currently -webkit-fill-available) as there is still some -open questions around it and the CSS working group doesn't quite think -it's ready for prime time yet. -- Added use counter for prefixed intrinsic size keywords. -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] -- Working on refactoring min/max ContentForChild calls to share more -code and logic. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Landed initial support for nested multicol layout. Column balancing -still needs work but the most common use cases work. -- Plan to hook up printing code once I'm more confident about the -implementation. Will finally enable multicol for printing for the -first time ever in Blink. :) (mstensho) -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Landed several API patches and finishing up API conversion for box -model object. Estimate about a weeks worth of work remains. (pilgrim) -Text (eae, drott, kojii) -- Debugging font matching issue on windows, looks like Skia is not -returning the full font name. (drott) -- Implemented tab characters for complex path, one of the blockers to -unify simple path to complex path. (kojii) -- Landed font fallback cleanup to fix a crash bug with support from the -memory team. (kojii) -- Enabled Unicode Variation Selector for Chrome OS. (kojii) -- Eliminated the last remaining direct caller to HarfBuzzShaper for -better layering. (kojii) -- Fixed handling of invalid and unmatched UTF-16 surrogate pairs, we now -replace invalid pairs with a replacement glyph and keep processing the -rest of the text node while before we would abort after the first -invalid character and not paint the remaining text. (eae) -- Fixed handling of tabs in complex path in cases where tabs are not -supported. (eae) -Misc: -- Cleaned up PageBoundaryRule and nextPageLogicalTop. (mstensho) -- Fixed issue with auto-height table cells and percentage heights that -broke a couple of popular legacy websites. (mstensho) -- Issue with win10 bots where hundreds of tests where failing and tools -not yet updated to support win8 or win10 specific results, since -resolved. (cbiesinger) -- Got go-ahead to upstream layout tests to W3C. (cbiesinger) -- Discussion around layout test standards and guidelines, jsbell gave -update on plan to support web platform tests and will send out further -information when ready. -- Wrapping up custom properties. (leviw) -Logistics: -- cbiesinger gardening last week (Thu-Fri). -- leviw gardening this week (Mon-Tue). -- Pre-CSS F2F meeting in SF on Tuesday.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-24-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-24-2015/index.md deleted file mode 100644 index 3d414cf7d5e..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-24-2015/index.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-august-24-2015 -title: Monday, August 24, 2015 ---- - -Updates since last meeting (on Monday, August 17th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Working on an issue where Element.clientWidth and clientHeight are not -excluding the width/height of scrollbars as expected. (skobes) -- There is logic for coordinates scrollbars in the compositor that has a -check in scrolling coordinator that only applies to the main frame on -some platforms. Needs investigation as we'd like this to apply for -root layer scrolling on all platforms. (skobes) -- Trying to land a fix for scroll bounds but encountered a couple of -test failures that only occur on Mac and Windows. Do not have access -to either platform at the moment (working remotely). Looks like off-by --one errors. Will work with skobes to track it down. (szager) -- Have been continuing to struggle with flexbox scrollbar change. Had -perf regression that prevented landing it. Fixed regression mostly, -is close but is a great deal of variance in inspector tests between -runs. Working on getting tracing information from running layout -tests. Will reach out to tracing-team. (szager) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Added use counters for flexbox intrinsic size change and for the -prefixed intrinsic size keywords. -- Unprefixed the intrinsic size keywords, with the exception of fill. -Will be in M 46. -- Looked into deprecating the old prefixed intrinsic size keywords, -only supported by us and webkit, fairly low usage. -- fill-avalible will be kept as prefixed, pending spec changes to -unprefix. Oddly seems to be the most used one. -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Refactoring the multicol balancing implementation. It currently -assumes that the layout engine feeds the balancer with accurate data -(space shortage and explicit breaks) for each layout object once and -only once for each layout pass. This is an incorrect assumption, -because sometimes we relayout a subtree (typically because the initial -logical top estimate was wrong) (in which case what the balancer got -during the first pass is most likely wrong). Sometimes we also just -skip an entire subtree as an optimization (which may mean that the -balancer doesn't get all the data it's supposed to get). Trying to -change it to performing everything related to column balancing after -layout of a flow thread, instead of partially during layout and -partially after layout. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Landed several API patches. Estimate a couple of days worth of work -remains. (pilgrim) -Text (eae, drott, kojii) -- Landed font-stretch and better matching for font-style, had some -issues that delayed landing it but it's in now and we have great test -coverage for it. (drott) -- Discussed font mathcing tests with adobe. (drott) -- Will continue work on font fallback this week. (drott) -- Encountered a skia bug where the full font name wasn't returned as -expected on windows, was quickly fixed by bungeman, thank you! -- Working on blink/harfbuzz integration, plan is to have harfbuzz do the -font fallback instead of doing it prior to shaping. That way combining -marks, among other things, can be better supported and we avoid having -to reinvent the wheel given that harfbuzz already has support for font -fallback. Long process and complicated dependencies. Will require -changes to how we handle variance (like small caps and emphasis marks) -as our current implementation cannot be supported and will need to be -updated. Should also result in cleaner code. (drott) -- Fixed handling of CSS word-spacing for non-breaking spaces. (eae) -- Investigating test changes required for enabling complex text -everywhere. Might be able to disable kerning and ligatures for some -scripts temporarily to avoid having to rebaseline all tests and to -make the change in two stages; (1) enable complex text everywhere, -(2) enable kerning & ligatures. Not sure it's worth the effort. (eae) -- Working on blockers for unifying simple path and complex path. (kojii) -- Enabled Unicode Variation Selector in ChromeOS/Linux. (kojii) -- Fix line breaking issue around ruby. (kojii) -- Working on CSS Writing Modes issues. (kojii) -Misc: -- Subpixel bugs. (leviw) -- Burning down Mac OS 10.10 test expectations, down 900 lines last week -alone! (leviw) -Logistics: -- leviw goes on vacation (that thing in the desert) on Wed + two weeks. -- skobes goes on vacation on Thu + one week. -- szager on vacation Wed and Fri. Back in SF on Mon. -- esprehn, ojan, ikilpatrick in Paris for CSS F2F meeting this week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-29-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-29-2016/index.md deleted file mode 100644 index 263352edfee..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-29-2016/index.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-august-29-2016 -title: Monday, August 29, 2016 ---- - -Updates since last meeting (on Monday, August 22, 2016): -Scrolling -- Work on root layer scrolling continues. (szager) -Scroll Anchoring \[[crbug.com/558575](http://crbug.com/558575)\] -- Support for SANACLAP (Suppress if Anchor Node Ancestor Changed Layout- -Affecting Property) landed. Should help reduce the number of hacks -required to support the feature. \[<http://bit.ly/sanaclap>\] (skobes) -- Aim this week is to get it (SANACLAP) into canary to gather data. -- Dealing with a devtools scroll anchoring bug. -CSS Flexbox -- Incoming bug rate for flexbox is going down, most issues have been -fixed and we aren't detecting many new ones. Yay. (cbiesinger) -- Some lingering reports and concerns about the abs-pos change that -will require outreach/evangelism. Not nearly as much as previously -thought though. Microsoft paved the way and did a really good job of -reaching out to web authors. (cbiesinger) -CSS Grid Layout \[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week. See tracking bug for status. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Still working on paint layer issues triggered by an investigation into -incorrect behavior for getClientRects. Issues mostly around writing -mode and paint layer interaction. Paint layer is a mess when it comes -to coordinate spaces. (mstensho) -CSS Houdini -- Lots of work around Worklets for Web Audio and Web Animations in -preparation for TPAC last week. (ikilpatrick) -- Plan to spend more time preparing the Worklets and CSS Custom Layout -specs for TPAC this week. (ikilpatrick) -- Working on event loop spec. (glebl) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Converted every backing fragment and constraint space to physical -coordinates instead of logical. (ikilpatrick) -- Might attempt to add initial support for floats this week. -(ikilpatrick) -- Started on inline layout support. (eae) -- Initial layout opportunities implementation. (eae) -- Implemented state machine for async layout. (cbiesinger) -- Added fragment builder class to help with fragment construction. -(cbiesinger) -- Start working on margin collapse. (glebl) -Resize Observer (atotic) -- Finally landed and is looking good for M54. (atotic) -Tables (dgrogan) -- Continuing work on fixing high priority table bugs. (dgrogan) -Text (eae, drott, kojii) -- Complex text on Android is looking good and is on track for M54. -(drott) -- Investigated a shaping regression on old OS X versions. Due to a few -previous shaping fixes we now crash in certain cases due to the font -fallback cascade on old versions of OSX. Looking into options. (drott) -- We don't support type1 (bitmap) fonts on Linux however they show up -in the font selection UI. Fixed this and in doing so also broke the -dependency on Pango. (drott) -- Made a change to skia to avoid picking type1 fonts during fallback, -thereby reducing the number of attempts thus improving performance. -(drott) -- Preparing for ATypI. (drott) -Interventions -- Iterated on data collection methodology for a potential third party -iframe intervention. Missed the branch point but got a patch that -I'm happy with. (dgrogan) -Misc: -- Helping Physical Web team with Google infrastructure integration. -(glebl)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-3-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-3-2015/index.md deleted file mode 100644 index 1d2a3c6d27a..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-3-2015/index.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-august-3-2015 -title: Monday, August 3, 2015 ---- - -Thanks for running the show last week jsbell. Now back to our regularly - -scheduled programming. - -Updates since last meeting (on Monday, July 27th): - -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Fixed under-painting issue on android. (skobes) - -- Fixed a regression causing double scrollbars caused a previous bug - -fix. (skobes) - -- Identified that scrollable elements with animated gifs will do a - -full re-layout even if it's composited. (skobes) - -- Fixed a hairy flexbox scrollbar bug where the size of the scrollbar - -wasn't taken into account when computing the flexed size. (szager) - -- Containing work cleaning up DepricatedPaintLayerScrollableArea in an - -effort to have sane scroll bounds for the root layer. (szager) - -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Had a meeting with CSS flexbox spec authors last week and leared that - -some areas of the spec that I've been working on implementing might - -change further. Will follow up this week. - -- Triaged a bunch of flexbox bugs. - -- Up-streaming flexbox tests have proven harder than expected, might - -take a week or two to resolve. - -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] - -- cbiesinger have been helping with reviews. - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- Doing a lot of cleanup and bug fixing work. - -- Containing working on support for nested columns, progressing nicely - -but nothing landed yet. - -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] - -- Working on moving layout box and descendants over to use the API. - -(pilgrim) - -Isolate core/fetch (japhet) \[crbug.com/458222\] - -- No update. - -Text (eae, drott, kojii) - -- Text workshop in Helsinki, Behdad and Drott working on optimizing the - -Blink/HarfBuzz integration. - -- Completed tests for styling and selection, found a few issues as a - -result and have been working on fixing those. (drott) - -- Unicode range matching is next. (drott) - -Misc: - -- Continuing to talk to people about position observer, got lots of - -feedback, mostly positive. (slighgtlyoff) - -Logistics: - -- kojii on vacation this week. - -- drott on vacation this Wednesday until next Friday. - -- cbiesinger in SF this week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-31-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-31-2015/index.md deleted file mode 100644 index 974a2c72a84..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-august-31-2015/index.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-august-31-2015 -title: Monday, August 31, 2015 ---- - -Updates since last meeting (on Monday, August 24th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Tracked down issue with scroll bounds change and determined that the -failing tests where due to a bug in the old implementation. New test -results are correct. Will require a rebaseline. (szager) -- Still having some problems with the flexbox scollbar change, need to -figure out why the fix is causing a perf regression. Happy with code -change and convinced the fix is correct and that the new behavior is -better. (szager) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Unprefixed sizing keywords. -- Continuing work to bring implementation up to spec. -- Various bug fixes. -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Continuing work on multicol balancing and nesting. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Landed several API patches. Estimate a couple of days worth of work -remains. (pilgrim) -Text (eae, drott, kojii) -- Working on CJK fonts pri 1 issues. (kojii) -- Working on complex path blockers and recent regressions. (kojii) -- Resolved all open spec issues in Writing Modes in CSS F2F. (kojii) -- Investigating unprefix planning for Writing Modes. (kojii) -- Continued on shaper driven segmentation work. Have working prototype. -Quite a bit of work remains to handle all edge cases, vertical text -and emphasis marks. (drott) -- Various Windows font fallback fixes. (eae) -Misc: -- Ripping out linebox contain implementation following last weeks intent -to deprecate and remove. (wkorman) -- Misc bug fixes, mostly related to rounding and line boxes. (szager) -- Plugin persistance was re-landed last week, this allows plugin state -to persist across reattach and is a big win. (dsinclair) -Logistics: -- leviw on vacation (that thing in the desert) this week and next. -- skobes on vacation this week. -- szager back from Seattle. -- esprehn, ojan, ikilpatrick in Paris for CSS F2F meeting until mid week. -- cbiesinger out until Wednesday.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-1-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-1-2016/index.md deleted file mode 100644 index ce3f191a5c8..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-1-2016/index.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-1-2016 -title: Monday, February 1, 2016 ---- - -Updates since last meeting (on Monday, January 25th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Prototyping scroll anchoring and added a flag for enabling it, ---enable-scroll-anchoring. Working on a basic implementation. Current -design looks solid and well encapsulated. Still needs testing in the -real world but looks promising. (skobes) -- Changed LayoutRoots to avoid making scrollbars trigger relayout. -(leviw) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Fixed a number of flexbox regressions last week. As of now all known -regressions in 49 and 50 have been resolved. Most 48 regression have -been addressed, merged a last fix this morning. -- Flexbox interop work continues, including a follow up to a temporary -fix for a regression. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last meeting. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Intent to unprefix multicol as is turned out not to be too popular. -Gated on generic breaking properties. Will send out a separate intent -for that. Breaking properties are generic and apply to all paginated -(and in theory region based) content. Not simply an alias for -webkit -prefixed properties as the values differ. -- Fixed a number of multi-col bugs. -CSS Houdini (ikilpatrick) -- Presented custom paint, custom properties and custom layout at CSS -working group meeitng in Sydney. (ikilpatrick) -- Updated custom paint, custom properties and custom layout specifications. -(ikilpatrick) -- Barista for the houdini working group, exceeding expectations. -(ikilpatrick) -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Moved resolvedColor to use line layout api, had a lot of cascading -effects that allows for simplifications in TextPainter and further -allows the API to be used in unit tests. Nice properties and -simplification ensued. (pilgrim) -- Multiple line layout patches includes a potential large change to the -API that was discussed last week. Fully up to speed on api work and -have a few layout patches pending. (dgrogan) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Discussed CSS containment at CSS working group meeting, positive signals -from working group and other implementors. (leviw) -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Added optimization to skip render-throttled iframes during hit -testing. (szager) -Text (eae, drott, kojii) -- Presented CSS Writing Modes, CSS Text Decorations, and Snap at CSS -Working Group meeting in Sydney. (kojii) -- Emoji segmentation, tests on all platforms. Some blockers on Android -due to lack of capabilities with regard to font family based font -selection for fallback. (drott) -- Enabling open type features through CSS keywords. (kojii) -- Dealing with regressions and fallout following font fallback overhaul. -(drott) -HTML Tables (dgrogan) -- Misc table interop fixes relating to percentage height resolution. -(dgrogan) -- Working on a table regression dating back to the WebKit days, will -send out to Morten for review later today. (dgrogan) -Misc -- Made int to layout unit conversion explicit to avoid unnecessary -round-trips and v8 problems during style conversion. (leviw) -Logistics: -- ikilpatrick, leviw, kojii, and eae in Sydney for Houdini and CSS WG -meetings. <https://wiki.csswg.org/planning/sydney-2016> -- drott, behdad, kojii in Tokyo for Text workshop February 19-28.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-2/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-2/index.md deleted file mode 100644 index 5f0f6cea96c..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-2/index.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-2 -title: Monday, February 2, 2015 ---- - -Performance Tracking (benjhayden) -- Running perf tests on Android, have preliminary data. -- Loading fonts takes up a lot of time for some specific tests, these -tests have very simple layout though so font-loading is the only -"slow" thing. -- Most test have a more even distribution that looks very similar to -linux. -- Added histogram for layout times to collect user data. Might add more -detailed ones (text layout vs block layout etc) later. -Rename Rendering -> Layout \[[crbug.com/450612](http://crbug.com/450612)\] -(dsinclair, bsittler, -jchaffraix, eae) -- Moving rendering to layout. Using spreadsheet to coordinate. -- Moved hit testing last week, moving compositing now (dsinclair) -First-letter (dsinclair) -- More Clusterfuzz issues. -Line Boxes (hartmanng, szager) \[[crbug.com/321237](http://crbug.com/321237)\] -- Continuing on float to layout unit conversion. Looks like a few more -classes will need to move to layout unit. -- hartmanng and szager to sync up on status and strategy. -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Started working on updating flexbox implementation to match latest -spec revision. -- Coordinating with the firefox and IE teams to ensure compatibility. -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] -- Background painting bug has been fixed (yay!) -- window.scrollTo wired up for root layer scrolling. -- Working on issues with position: fixed. -Text (eae) -- Held text workshop with android and i18n teams last week. Will try to -share hyphenation implementation (or at the very least dictionaries) -with android. szager volunteered to lead this form the blink side, -likely in Q2. -- Looks like the i18n team has dictionaries with compatible licenses -for at least a handful of languages. -- WIP patch that removes an extra copy of the text and avoids -unnecessary work for 8bit. Needs a new version of harfbuzz which is -problematic. -Logistics -- hartmanng is perf sheriff last week. -- jchaffraix and eae in Sydney for planning meeting. -- szager out much of last week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-21-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-21-2016/index.md deleted file mode 100644 index 61da2ebb411..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-21-2016/index.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-21-2016 -title: Monday, March 21, 2016 ---- - -Updates since last meeting (on Tuesday, March 15, 2016): -Scrolling (skobes) -- Working on patch to fix absolute positoined scroll anchors within -static positioned scrollers which is an interesting edge case. -- Smooth scrolling and scroll anchoring interaction is a bit problematic -and needs some work given the absolute scroll offsets that update -immediately. -- Work on speeding up smooth scrolling in response to user feedback. -CSS Flexbox (cbiesinger) -- Fixed percentage sizing, the last remaining major task. -- Almost all of the scrolling regressions (again!) still one case -remaining that needs more investigation. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- eae/svillar trying to figure out what would be required to ship CSS Grid. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- The past weeks I've been working on the break-{after,before,inside} -properties. Mostly some preparatory patches so far, while I've kept -the beefy parts to myself for now. -- Also: continued cleaning up and untangled multicol stuff in -mapLocalToAncestor() and friends, which made it super-easy to fix some -a hot PaintLayer clipping bug afterwards. -CSS Houdini -- Hooking up script support for the CSS Paint API this week. -(ikilpatrick) -- Next up is generating new CSS images for the paint API. (ikilpatrick) -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Working on getting all of the LayoutView references over to the new -block layout API, will be one of the largest leaf nodes ion the new -layout API. (pilgrim) -- Will try to add precoomit hook to enforce the line layout API. -(dgrogan) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- LayoutNG hackathon last week. It happened and was glorious. We got of -to a better start than expected, got very simple layout working day -one. I think we're convinced that it's a tenable design, deciding on -next steps. (leviw, ikilpatrick, dgrogan) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- No update since last week - -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Assortment of patches for intersection observer, including all release -blockers that I'm trying tom land this week before vacation. Gated on -reviewers. (szager) -Text (eae, drott, kojii) -- Landing fix for shaping fonts across unicode ranges, now all ranges -are all shaped together in one go. Also fixes a bug reported by -typekit, made adobe happy. (drott) -- Resume work on small-caps font variant. (drott) -- Investigating line breaking performance. (eae) -HTML Tables (dgrogan) -- Dealing with a table bug fix from a few weeks ago, breaking some -chrome-only sites relying on the old incorrect behavior. -Misc -- Rebaseline bot is now actually running on the builder, no longer on -my workstation. Exciting times. (wkorman) -- More detailed research on writing modes, continues this week and -next. (wkorman) -Logistics -- cbiesinger in SF week of March 28. -- drott in SF week of March 28. -- szager on vacation starting week of March 28.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-22-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-22-2016/index.md deleted file mode 100644 index 8ef344e0144..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-22-2016/index.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-22-2016 -title: Monday, February 22, 2016 ---- - -Updates since last meeting (on Tuesday, February 16th): -Scrolling (skobes) -- Fixed crashes caused by stale LayoutObject pointers in scroll anchor. -- Fixed an old bug in coordinated scrollbar where we hold stale -scrollbar pointers. -- Simplifications in paint layer scrollable area. -- Playing around with scroll anchoring on real world web sites. -- Discovered a new smooth scroll regression. -CSS Flexbox (cbiesinger) -- Finished up the scrolling fixes last week, at least I thought I did. -szager found another issue relating to nested flexboxes. Not quite -sure what the correct fix is, will require further work. -- More flexbox release blockers relating to overflow: auto. -- Imported Mozilla flexbox tests, pass the vast majority. One failure is -paint related and will probably fixed by slimming paint v2 (the -fundamental composting bug), a few fail due to lack of visibility -collapse support. -- Struggle with upstreaming tests to w3c continues, synced up with -fantasi and have a plan to move forward. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Multi column properties unprefixed! Congrats! -\[[crrev.com/376249](http://crrev.com/376249)\] -- Added partial support for modern breaking properties. Work on these -continues. -CSS Houdini (ikilpatrick) -- Successes in splitting up RenderingContext2d, patch out that has an -LGTM already. Should be ready to land today. -- Started adding dev-tool support to worklets, plan to have it hooked up -and working at the end of this week. -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Working on removing the default operator for the Line Layout API. -Covering gaps in the API where we are relying on implicit conversion. -(pilgrim) -- Started working on the Block Layout API. Trying to figure out the -hierarchy, still up in the air. (pilgrim) -- Hope to finish up Line Layout API and add include guard by the end of -the week. A bit hairier than expected but cautiously optimistic. -(dgrogan) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- No update since last week. -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Spent most of last week doing spec work for IntersectionObserver. -\[szager\] -- This week, I have a few code changes to make so our Intersection -Observer implementation matches the latest version of the spec. -After that plan to ramp down work on IO for the time being. \[szager\] -Text (eae, drott, kojii) -- kojii/drott/behdad doing a text workshop in Tokyo, dealing with text -shaping and font fallback issues. -HTML Tables (dgrogan) -- No update since last week. -Misc -- Fixed getBoundingClientRect for collapsed ranges. (eae) -- Removed mac specific backspace handling in editing. (eae) -- Fixed a number of release blockers. (leviw) -Logistics -- ikilpatrick in Waterloo, Canada next Week. -- leviw out Monday (today). -- dgrogan out Friday and next Monday. -- behdad/drott in Tokyo all week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-23-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-23-2015/index.md deleted file mode 100644 index 44785ef67aa..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-23-2015/index.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-23-2015 -title: Monday, February 23, 2015 ---- - -We had two new people joining the meeting this week: - -- Joshua Bell (jsbell) - -- Works on Storage APIs (TL) and ServiceWorker. - -- Interested in some of the non-layout Warden tasks. - -- Alex Russell (slightlyoff) - -- TL for Fizz. Available to consult on API questions and JS interaction. - -Updates since last meeting (on [Wednesday, February -18th](/teams/layout-team/meeting-notes/wednesday-february-18)): - -Performance Tracking (benjhayden) - -- Looking at perf regressions on a webkit performance test. - -Scrolling (skobes) \[crbug.com/417782\] - -- Fixed Mac smooth scrolling regression. - -- Working on fixed position elements this week. - -Rename Rendering -> Layout \[crbug.com/450612\] (dsinclair) - -- Trying to rename RendereBlock to LayoutBlock. Will have to land - -outside of office hours and/or close the tree. Will coordinate with - -the infra team. - -Measure API (jchaffraix) - -- Synced up with slightlyoff on API surface and implementation. - -- Continuing work on prototype and write-up. - -Line Boxes (hartmanng, szager) \[crbug.com/321237\] - -- No real progress last week. Plan to resume this week. - -Flexbox (cbiesinger) \[crbug.com/426898\] - -- Working on updating flexbox implementation to match latest spec - -revision. - -Text (kojii, wjmaclean, eae) - -- Vertical flow performance test is up and running. (kojii) - -- Temporary reverted vertical flow to simple path for the branch cut. - -(kojii) - -- Studying line breaker and exploring ideas: - -- Optimize width() when the length is one character. - -- Line breaker to use heuristic to start from likely break - -opportunities. (kojii) - -- Studying text iteration code, making it easier to follow. (wjmaclean) - -- Investigated Mac test regressions. (eae) - -- Plan to ressume work on complex text performance work, avoiding an - -extra copy of the string and unnecessary normalization. Requires an - -updated version of HarfBuzz which is tricky on Linux as we use the - -system version. Have some ideas. (eae) - -Misc - -- Finished blink starter bugs (svg image cache), image resourcem, - -Landed and done. (paulmeyer) - -- Renamed --dump-render-tree to --run-layout-tests. Done but documentation - -needs updating. Old flag deprecated but still there for now. - -Assertions/Regressions/blocking bugs - -- Working through list of ClusterFuzz assertions (cbiesinger). - -- Fixed a CluserFuzz selection range bug and got "rewarded" by being - -assigned another one. (szager)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-28-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-28-2016/index.md deleted file mode 100644 index c1bbb870981..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-28-2016/index.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-28-2016 -title: Monday, March 28, 2016 ---- - -Updates since last meeting (on Monday, March 21, 2016): -Scrolling (skobes) -- Fixed ScrollAnchor handling of position:absolute. (skobes) -- 35 tests currently fail with scroll anchoring, digging into those. -(skobes) -- Working on getting ScrollAnchor to work during smooth scroll -animation. (skobes) -- ScopedLogger got removed, I am trying to get it back in. (skobes) -CSS Flexbox (cbiesinger) -- No updates since last week - -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No updates since last week - -CSS Houdini -- Wrote up a giant patch for CSS paint. Plan to split it up into to, fix -bugs and add tests this week before landing. (ikilpatrick) -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Converting layout view to api. (pilgrim) -- Added an include guard for the line layout api and fixed the few small -API gaps it exposed. (dgrogan) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Finishing up document reporing the outcome from the LayoutNG -hackathon. (leviw, eae) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Some CSS Containment discussions. Current options are layout, paint, -style, and strict. Adding one more, bike-shedding on name. -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- szager on vacation this week, eae will try to land a couple of -outstanding changes in his absence. (eae) -Text (eae, drott, kojii) -- Fixed a text wrapping bug where a fast-path incorrectly applied to LTR -content in a RTL container. (eae) -- Finished line breaking investigation and wrote up a design document -outlining my proposed new approach, using shaper information. (eae) -<https://docs.google.com/document/d/1eMTBKTnWEMDu00uS2p8Xj-l9Pk7Kf0q5y3FbcCrWYjU/> -- Started looking into a number of white-space: pre bugs. (eae) -- Fixed the invalid unicode codepoint issue that pdr@ had pointed us -to; Ugly integer truncation issue. (drott) -- Continued the work on small caps, implementation is coming along quite -well, the opentype feature itself works, but the synthesis needs more -tweaking. (drott) -- Started looking into the confused glyphs issue on Mac. (drott) -HTML Tables (dgrogan) -- Looked into a few table bugs but haven't yet made demonstrable -progress. (dgrogan) -Misc -- Have a full page of notes that are useful to me on writing mode, was -derailed due to paint perf work, expect to get to spend a few days -this week on it. (wkorman) -Logistics -- cbiesinger in SF week of March 28. -- drott in SF week of March 28. -- szager on vacation starting week of March 28.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-29-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-29-2016/index.md deleted file mode 100644 index 737831fd8a7..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-29-2016/index.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-29-2016 -title: Monday, February 29, 2016 ---- - -The layout team is a long-term team that owns the layout code in blink. -See <https://www.chromium.org/blink/layout-team> for more information. -Updates since last meeting (on Tuesday, February 22nd): -Scrolling (skobes) -- Last week, figured out that scroll anchoring is super broken. Working -on fixing that. We're not intercepting frameview scrolls correctly. -(skobes) -- Three new smooth scrolling regressions reported last week, working on -fixing those. (skobes) -- Aim to get back to helping out with scrolling work next week. -(szager) -CSS Flexbox (cbiesinger) -- Fixed all the scrolling bugs! Much rejoicing! Sadly the fix has been -reverted to due causing a crash in FrameView. -- Upstreaming flexbox tests to w3c. -- Started working on percentage sizing of children of flex items. A lot -of user requests and required by the updated spec. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No update since last week - -CSS Houdini (ikilpatrick) -- Last week, landed PaintRenderingContext2d changes. Fun times with a ms -compiler bug. -- Got debugging for worklets working locally, coordinating with devtools -team about ways to integrate it into devtools. -- This week, talking to compositor worker team about API things. -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Have been filling out the new block layout API class hierarchy, should -be done creating all the necessary classes this week at which point I -can report back on how much work each one of the will be. (pilgrim) -- Chased down some remaining gaps in the line layout API but didn't -finish. (dgrogan) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Started working on the scafolding for LayoutNG. (leviw) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- No update since last week - -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Working on a few coding issue around intersection observers, keeping -up with spec changes. (szager) -- More or less wrapped up on heavy duty part of that, converting some -tests to w3c style. (szager) -- We should do some perf testing, we don't really know how fast or slow -our implementation is. (szager) -- Also signed up to run an experiment where we use intersection observer -to see how frequently we encounter iframes that load but are never -viewed. Gather date to inform possible interventions down the line. -(szager) -Text (eae, drott, kojii) -- Cleaned up platform specific FontCache code. (eae) -- Updated windows font fallback logic for win 7, 8, 8.1 and 10. (eae) -- Added support for Glagolitic script. (eae) -- Started looking into antialiasing toggling on windows and a better way -to query the system for font preferences that works without punching -holes through the sandbox. (eae) -HTML Tables (dgrogan) -- No update since last week. -Misc -- Have no more release blockers, yay! After battling trying to figure -out root cause for no 1 crasher for days, finally found repro. Tracked -down to "remove plugin size hack" change, reverting that fixed it. -Still some issues with regard to life cycle state but it's within -tolerance. Frames and widgets are handled differently. Specifically -from the parent frame (main frame) we have multiple loops where we go -into our child frames and tell them to move their life cycle along, -but we don't do that for widgets. When a frame within a widget (web -view plugin) we special case that causing all sorts of unpredictable -behavior. Should be fixed at some point but not a priority at the -moment. (leviw) -- Have begun the code research phase for the exploratory flipped blocks -work. at a minimum we'll learn things. (wkorman) -- Pretended it was 1997 and fixed full-page-zoom for frames (as in -frameset). (eae)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-8-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-8-2016/index.md deleted file mode 100644 index f28a87e5107..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-8-2016/index.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-8-2016 -title: Monday, February 8, 2016 ---- - -Updates since last meeting (on Monday, February 1st): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Basic implementation of scroll anchoring landed behind the ---enable-blink-features=ScrollAnchoring flag. (skobes) -- Working on adding more test cases for scroll anchoring. (skobes) -- Adding about:flags entry so folks can try on mobile canary. (skobes) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Continued triage. -- Fixed main size calculation for overflow:auto. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -(since last grid update in late December) -- Fix auto track sizing with min-size:auto (svillar) -- Add support for repeat(auto-fill|auto-fit,) (svillar) -- Support for implicit grid before explicit grid (rego) -- Fix unknown named lines resolution (rego) -- Investigating issues with positioned items and RTL (rego) -- Layout tests refactoring (jfernandez) -- Investigating issues in orthogonal grids (jfernandez) -- Add "normal" for content alignment (jfernandez) -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Working on cleaning up mapLocalToAncestor() in order to make it easier -and cleaner to fix a multicol bug. -- Intent to ship discussions continues, we might be able to unprefix -multicol real soon after all! -- Some work on the break-after, break-before and break-inside -properties. More or less ready to file a CL, once the intentery gets -resolved. -CSS Houdini (ikilpatrick) -- Stay tuned for a separate blonk-wide update on Houdini progress. -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Converted BlockPainter to new line layout API. (pilgrim) -- Convert last use of RootInlineBox to the API. (dgrogan) -- Shim AXLayoutObject uses of InlineBox->layoutObject(). (dgrogan) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Discussions about containment at CSS Working Group meeting with -standard body and other browser vendors. (leviw) -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Fixed handling of zero-sized target elements for observations. -(szager) -- Fixed handling of cross-origin observations. (szager) -- Changed observers to use DOMHighResTimeStamp for notification time. -(szager) -Text (eae, drott, kojii) -- Meeting with the Android fonts team to discuss needs and possible -integration going forward. (drott)1 -- Working on resolving emoji and multi-locale issues on Android, some -parts are tricky, some parts are easier. Will continue to work with a -android fonts team after the Tokyo workshop. (drott) -- landing the remaining parts of SymbolsIterator/EmojiSegmentation, -until now where I am hitting this issue of having to address graphemes -as a unit of fallback with Behdad first - as per my comment on the -last CL in the series. (drott) -- Working on font fallback for symbol/emoji fonts on Android with -bungman on the Skia team. (drott) -HTML Tables (dgrogan) -- No updates since last week. -Misc -- Finished work to make LayoutUnit construction explicit. (leviw) -- Fixed weird broken zooming logic in offsetTop/Left calls. (leviw)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-9/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-9/index.md deleted file mode 100644 index fe1f08084bf..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-february-9/index.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-february-9 -title: Monday, February 9, 2015 ---- - -\[ eae gave high level update on planning meeting; separate -announcement on that to follow \] -We added three new team members to this week which is very exciting! -Welcome aboard, we're glad yo have you! -- James Maclean (wjmaclean) in WAT, new to project warden. -- Paul Meyer (paulmeyer) in WAT, new to blink and warden. -- Koji Ishii (kojii) in TOK, new to the team but has already been helping -out with text rendering performance for awhile. -Performance Tracking (benjhayden) -- Refined android profiling pipeline, similar to existing linux one. -- Results match that of linux with a few exceptions, more time spent in -powf() and loading fonts. Almost 3% of total layout time is spent in - -powf() translating color spaces for fonts. -- Started to look into FontCache on android which doesn't seem as -effective as on other platforms. -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] -- Smooth scrolling now works the same for overflow divs as for frames. -win_blink flakiness (dsinclair) -- Worked to reduce win_blink flakiness by triaging flakiness and -timeouts. -- Flakiness went from 40% -> 10% (!), it is now one of the faster bots. -- Much of remaining flakiness due to font antialiasing/subpixel -rendering differences. -Rename Rendering -> Layout \[[crbug.com/450612](http://crbug.com/450612)\] -(dsinclair, bsittler, -eae, hartmanng) -- All non-prefixed files renamed. 188 prefixes files remaining. -(dsinclair) -- Most of the linbox tree has been moved. (hartmanng) -List markers (dsinclair) -- Trying to figure out how to deal with an ancestor being moved. Opera -has some ideas and there might be multi-col logic that can be reused. -Text (kojii, eae) -- Make RenderCombinedText less obstructive to the line breaker and -paint code. Mostly [donecrbug.com/433176](http://donecrbug.com/433176), -selection paint issue -[crbug.com/438852](http://crbug.com/438852) and a bit more cleanup still -remains. (kojii) -- Complex path perf issue that had been stalled due to the slow legal -permission is finally clear now, hope to re-start with Dominik this -week. (kojii) -- Folded line_break into TextBreakIteratod, removed unused logic and -de-templetized a bunch of functions. (eae) -- Difference in preferred width between text and containing element -caused regression on Facebook due to strict overflow handling. -Has fix but writing layout test is difficult due to simplified -text-rendering pipeline for tests. (szager) -- Fixed ZWJ handling on simple text path on Mac. (eae)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-january-11-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-january-11-2016/index.md deleted file mode 100644 index 1d423b6d334..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-january-11-2016/index.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-january-11-2016 -title: Monday, January 11, 2016 ---- - -The layout team is a long-term team that owns the layout code in blink. - -See https://www.chromium.org/blink/layout-team for more information. -Updates since last meeting (on Monday, January 4th): -Scrolling (skobes, szager) \[crbug.com/417782\] -- Launched smooth scrolling! Top user request for year and one of our -oldest open feature requests. Congratulations! \[skobes\] -- Swamped with smooth scrolling issues. \[skobes\] -- Biggest issue is we can't tell wheel scrolling form trackpad scrolling -on windows, might end up enabling smooth scrolling for trackpads -too. \[skobes\] -CSS Flexbox (cbiesinger) \[crbug.com/426898\] -- The behavior changes in December caused a number of problems on high -profile websites. A lot of triage and bug fixing to follow. -CSS Multi-column (mstensho) \[crbug.com/334335\] -- Bug fixing for nested multicol and print support. -CSS Houdini (ikilpatrick) -- Plan to send intent to implement for CSS Paint this week. -- Spec work; draft of css custom layout api in time for houdini meeting -in Sydney at the end of the month. -- Meeting with MS and Apple in Seattle last week, very productive in -terms of getting on the same page with regards to custom layout and -suggesting something that all rendering engines can support. -Add API for layout (leviw, pilgrim, ojan) \[crbug.com/495288\] -- Wrapping up API around inline layout. -Intersection Observer (szager, mpb) \[crbug.com/540528\] -- Enabled on trunk, work continues. -Text (eae, drott, kojii) -- Tracking down AAT font slowness on mac. Looks like we have a great -patch that will improve it by at least an order of magnitude. We had -a couple of issues with 16s rendering for a simple page. Due to AAT -artificial fallback slowness, going through the fallback path up to five -times unnecessarily. (drott) -- Emoji segmentation, assisting fallback for emoji and punctuation. -Initial approach didn't quite work as expected due to complex cases, -have a new implementation that looks better and solves all the -known cases. (drott) -HTML Tables (dgrogan) -- We had an artificial limit for row-span, increased it to match the FF -artificial limit in response to developer bug reports. -Logistics: -- This is the last layout team meeting for jchaffraix as he is leaving -the team and blink as of the end of this week. Thanks for all your -work on Blink over the years Julien and best of luck on your next -projects. -- cbiesinger in Tokyo until Jan 20. - -- eae, leviw in Tokyo next week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-january-4-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-january-4-2016/index.md deleted file mode 100644 index dc50b317ebe..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-january-4-2016/index.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-january-4-2016 -title: Monday, January 4, 2016 ---- - -Welcome back every, I hope you all had a good holiday break. -With a new year comes new goals. Before we can set the high-level 2016 -goals and Q1 OKRs though we should reflect on where we are and evaluate -our Q4 progress. -I'll reach out to everyone individually over the next week or so to -start the OKR process and will schedule a team-wide OKR meeting in a -week or two. In the mean time please try to summarize and score your Q4 -OKRs and start thinking about what you want to work on in Q1 and beyond. -Updates since last meeting (on Monday, November 30th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Landed fix for smooth scrolling target updates. (skobes) -- Sizing main graphics layer for root layer scrolling. (skobes) -- Updated scroll anchoring design doc and plan start to implementing -it this week. (skobes) -- Ready to turn onm smooth scrolling! Patch is ready and plan is to flip -the switch this week (skobes) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- No updates since last meeting, cbiesinger still out - -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last meeting. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Managed to add support for printing. Involved solving the nested mult -column use case which was tricky. Once that was in place printing -support wasn't too much work. -- Considering unprefixing, seems reasonable. -- Fixing random multicol bugs. -CSS Houdini (ikilpatrick) -- Started to implement worklets, have patch out. Implementing all the -basic stuff for that. -- Also this week updating the CSS custom paint API. -- Intent to implement for custom paint this week or next. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Finishing up line layout text this week, part of the line layout api. -- Final patches to implement box which will be ready for review shortly. -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Plan to send Intent to Implement this week. -- Have pending spec patch that needs to be upstreamed. -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Trying to land Intersection Observer patch, not having much success. -(szager) -Text (eae, drott, kojii) -- Fixed a number of issues around complex text. (eae) -- Code cleanup following the move to always use complex text. (eae) -- Got simple text removal patch ready to go. Primed and ready to land as -soon as 49 branches. (drott) -- Zurich meeting with behdad and i18n, discuss improved fullback for -punctuation and symbols. Needs some manual tweaking. Need better -handling for color emoji and emoji combinations. Might need a symbol -iterator and then explicit font selection. (drott) -HTML Tables (dgrogan, jchaffraix) -- No update since last meeting. -Bug Health -- We managed to exceed our ambitious bug health goals by quite a bit -for Q4: -- Reduced untriaged bugs by over 70%, far exceeding goal of 50%. -Down to 180 unconfirmed/untriaged from 690 at the start of Q4. -- Reduced total open bug count by over 25%, exceeding goal of 15%. -Down to 1688 open bugs from 2310 at the start of Q4. -- A lot of hard work by the entire team, thank you everyone! -- Plan to institute a triage rotation in Q1, will be ~30 min a week for -one person (rotating). Details to follow. -Misc -- Stabalizing the rebaseline bot, is stable now, some open issues. -Looking at moving it to the build bot, blocked on infra issue that has -since been resolved. (wkorman) -- Fixed one layout blocker bug, felt good and nice to get a break from -trying to land intersection observer. More of the same this week. -(szager) -- Gave talk on layout at web engine hack fest in Spain. (drott) -Logistics: -- drott out Wednesday,m public holiday. -- eae, ikilpatrick, ojan in Seattle Thu-Fri for CSS Houdini meeting -with Microsoft.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-13-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-13-2015/index.md deleted file mode 100644 index fe51e635a95..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-13-2015/index.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-july-13-2015 -title: Monday, July 13, 2015 ---- - -Updates since last meeting (on Monday, June 22nd): - -Scrolling (skobes, szager) \[crbug.com/417782\] - -- Working on pinch viewport. (skobes) - -- Has fix for double scrollbar issue and potential fix for under- - -pinch. (skobes) - -- Helping out with scrolling, trying to figure out how to set, identify, - -and honor scroll bounds for the root layer. (szager) - -CSS Flexbox (cbiesinger) \[crbug.com/426898\] - -- No update, cbiesinger on vacation. - -CSS Grid Layout (svillar) \[crbug.com/79180\] - -- Updated auto tracks to use automatic minimums. (svillar) - -- Added support for infinitely growable tracks. (svillar) - -Region-based multi-column support (mstensho) \[crbug.com/334335\] - -- Looking into nested multicol, which is required for printing. Hope to - -move on to writing code for it soon. (mstensho) - -- Made a couple of changes to how we handle overflow at column - -boundaries that fixed Wikipedia but broke Google Plus. Should be - -possible to have both working at the same time. (mstensho) - -Add API for layout (leviw, pilgrim) \[crbug.com/495288\] - -- First part of the layout API landed and did not result in any - -performance regression. (pilgrim) - -Isolate core/fetch (japhet) \[crbug.com/458222\] - -- Working on refactoring how Blink revalidates cached results. (japhet) - -- Looking into a top user complaint; sometimes we show a blank page - -without any error message or indication that it went wrong. (japhet) - -CSS Test Suites (jsbell, kojii) - -- Continued work to import more w3c tests, now works with the w3c test - -server so that they won't require modifications any more. Looking for - -volunteers to help run and validate them. (jsbell) - -- Will unblocks tkent and kojii importing tests for their respective - -feature work. (jsbell) - -Text (eae, drott, kojii) - -- Looking into font fallback and trying to understand GlyphPageTreeNode; - -it serves a lot of different uses cases and we need to understand - -exactly what it does and why. (drott) - -- WebKit has made large changes to fallback and GlyphPageTreeNode since - -the fork. - -- Will write up a quick doc on fallback and then decide if we want to do - -a set of quick fixes or do a larger overhaul of how we do font - -fallback. (drott) - -- Finally got around to finish my revamp of the complex text code and - -the results are in, a 3.5x - 28x speedup across all platforms. With - -the slower platforms improving the most. The results are from a micro - -benchmark but given the amount of time spent in text layout on real - -world websites it should have a very noticeable impact. (eae) - -- Looking into what features we need to add to the complex text path in - -order to remove the simple path entierly. So far it looks like adding - -support for tab characters is the only major things missing. (eae) - -Misc - -- Profiling with perf on Android appears to be broken, working on fixing - -the run-benchmark-scripts. (wkorman) - -- Bringing up the Mac 10.10 bots. (joelo). - -Logistics - -- pilgrim on vacation this week. - -- cbiesinger on vacation this week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-18-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-18-2016/index.md deleted file mode 100644 index e577398974c..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-18-2016/index.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-july-18-2016 -title: Monday, July 18, 2016 ---- - -Updates since last meeting (on Monday, June 27, 2016): - -Back to our regularly scheduled programming after the chrome team wide -two no-meeting period. -Scrolling -- Work on root layer scrolling continues, will carry over into Q3. -(szager) -Scroll Anchoring \[[crbug.com/558575](http://crbug.com/558575)\] -- We now have a real spec for scroll anchoring \[1\]. (skobes) -- Sent Intent to Implement \[2\] to blink-dev. (skobes) -- Added support for the css overflow anchor property. (skobes) -- Plan to continue bug triage work this week. -CSS Flexbox -- Flexbox bug triage and bug fixes. (cbiesinger) -- Two known remaining issues for flexbox: -- Min-size auto for nested column flexboxes. -- Getting better metrics for new intristic size to see if it can -potentially be enabled by default. -(cbiesinger) -CSS Grid Layout \[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week. See tracking bug for status. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No updates since last week. Morten out for the next few weeks. -CSS Houdini -- Pretty large update to the Houdini layout API spec, got into some -really gnarly issues like out of positions floats in the middle of -words and how to make the constraint space API sane for developers. -Check it out \[3\], comments welcome! (ikilpatrick) -- Going through and seeing what worklet stuff needs to be done for web -audio, been meeting with the TOK team for worklets and will continue -that this week. (ikilpatrick) -- Fixed zoom in CSS paint worklets. (glebl) -- Fixed a small regression with select elements complicated by a lack -of tests. (glebl) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- The design doc for LayoutNG has been updated and the feedback from the -layout team incorporated. Thanks for your help and input everyone! -It's all but finished and I plan to circulate among the wider blink -team later this week. (eae, ikilpatrick) -CSS Containment \[[crbug.com/312978](http://crbug.com/312978)\] -- Shiped in M52. No further updates will be provided. (eae) -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Shiped in M51 with the last few fixes and improvements shipping in 52. -No further updates expected for the time being. (szager) -Resize Observer (atotic) -- Got LGTM from szager, other reviewers posetive but suggested splitting -implementation into multiple patches. Working ongoing. (atotic) -- Hope to land initial Resize Observer implementation this week. -(atotic) -- Set goals around event loop targets for Q3. (atotic) -Tables (dgrogan) -- Fixing a class of bugs around table borders. (dgrogan) -- Plan to work with the Sydney-based style team with a couple of table -issues blocking the work to separate style resolution from layout tree -construction. (dgrogan) -- Next up is adding support for visibility: collapse to table rows and -columns. (dgrogan) -Text (eae, drott, kojii) -- Complex text enabled by default on Android again (yay!), there are a -number of small regressions with regard to both performance and memory -but nothing like the big regressions we've seen in the past. Still -deciding on strategy. (drott) -- Merged font manager change corresponding regression fix to M53. -(drott) -- Next, planning to go back to looking at the glyphToBoundsMap removal - -there were still regressions in SVG tests that I need to figure out. -(drott) -- Meeting with Docs team tomorrow to discuss what could be done in -Chrome to improve Docs. (drott) -- Fixed a couple of crashes involving LayoutTextControl. (eae) -Misc: -- Fixed SVGLength crash. (eae) -- Up until now eae has been doing all bug triage for the layout team. -Now that the triage backlog is zero it's time to start a rotation -among all team members. Expect it to start next week and to involve -one week long stint as a triager every two months. (eae) -- Wrote up instructions for bug triage \[4\]. (eae) -Logistics: -- szager out for the next two weeks. -- mstensho out for the next month. -1: -<https://www.google.com/url?q=https%3A%2F%2Fcdn.rawgit.com%2Fymalik%2Finterventions%2Fmaster%2Fscroll-anchoring%2Fspec.html&sa=D&sntz=1&usg=AFQjCNGmw2oJ64KP0QB3z2UM2UBvX0kCdg> -2: -<https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/TbuxbOtyZvk> -3: <https://drafts.css-houdini.org/css-layout-api/> -4: <https://www.chromium.org/blink/layout-team/bug-triage>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-20-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-20-2015/index.md deleted file mode 100644 index 5cb52ee73bd..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-july-20-2015/index.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-july-20-2015 -title: Monday, July 20, 2015 ---- - -Updates since last meeting (on Monday, July 13th): - -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Continuing root layer scrolling conversion. Judging progress is hard - -and we don't necessarily know how much work remains, plan is to turn - -on root layer scrolling unconditionally and then run all he tests in - -order to see how many test failures we have and then use that as a - -burn-down list. Obviously progress isn't linear with the number of - -test failures but should give us a rough idea and a way to track - -progerss. (szager) - -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Back from vacation, resuming flexbox work. - -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] - -- No update. - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- No update, mstensho on vacation. - -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] - -- Landed a couple of line-layout API patches. (ojan) - -Isolate core/fetch (japhet) \[[crbug.com/458222](http://crbug.com/458222)\] - -- No update. - -CSS Test Suites (jsbell, kojii) - -- No update. - -Text (eae, drott, kojii) - -- Dealing with fallout from complex text refactoring/optimization. (eae) - -- Adding support for tab characters to complex text path, which in turn - -will unblock work to enable the complex path by default. (kojii) - -- Continuing work on rationalizing the font fallback implementation and - -logic. Have a good understanding of the system and working on adding - -tests to ensure that we do not regress and that our system has good - -test coverage. (drott) - -- Our font selection implementation is not necessarily spec compliant - -at the moment, looking into why and working on improving our - -font selection tests. (drott) - -Misc: - -- Triaging and updating baselines for the Mac 10.10 bots. (joelo, leviw) - -- Helping windows team with win 10 changes/tests. (eae) - -Logistics: - -- mstensho on vacation this week. - -- skobes on vacation this week. - -- pilgrim on vacation today, back tomorrow. - -- cbiesinger planning trip to SF on Aug 3rd \[tentative\].
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-1-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-1-2015/index.md deleted file mode 100644 index c1bdc0a5f32..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-1-2015/index.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-june-1-2015 -title: Monday, June 1, 2015 ---- - -Updates since last meeting (on Tuesday, May 25th): - -Performance Tracking (benjhayden) - -- Continuing to focus on trace viewer overall rather than limited to - -layout performance. - -- Visualizing layout in trace viewer. - -- Interaction records. - -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Figured out a way to run the WebFrameTest unit tests with booth root - -level scrolling turned on and off. Going through tests to catch - -regressions. - -- Learned more about page scale factor, turns out that the initial scale - -factor cause the FrameView to be a different size. - -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] - -- Landed over the weekend, re-baselines almost done. Yay! - -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Updated min-size handling to match latest version of spec. - -- Sycned up with Microsoft and Mozilla about their flexbox plans to - -ensure compatibility across browsers. - -Menu list refactoring (dsinclair) -\[[crbug.com/370462](http://crbug.com/370462)\] - -- Done! - -Fullscreen (dsinclair) \[[crbug.com/370459](http://crbug.com/370459)\] - -- Landed fix to persist plugins over re-attach. Subsequently reverted - -due to browser_test failures. Looking into failures and plan to - -re-land this week. - -Misc Warden (dsinclair, pilgrim) - -- Containing work to slim-dopwn LayoutObject. (pilgrim) - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- Will start to delete the old multicol code this week. It's no longer - -possible to enable it and no major regressions have been found. - -Text - -- Continuing work on complex text performance. (eae) - -- Experimenting with only inheriting inheritable properties into text - -nodes, not yet convinced that it affects performance noticeably, but - -it WILL increase memory usage, since we create a new ComputedStyle - -object for each text node (instead of sharing with the parent). - -Each text node that has the same parent could easily share the same - -ComputedStyle object, though, but we'd still be going to increase - -memory usage. (mstensho) - -- Fixed justification crash issue. (kojii) - -- Investigating orthogonal writing modes issues. (kojii) - -- Unicode variation selectors support in progress. (kojii) - -Importing Test Suites - -- Working on importing CSS Writing Modes test suites. (kojii) - -- Imported HTML tests. (tkent) - -Removing DeprecatedPaintLayer \[[crbug.com/260898](http://crbug.com/260898)\] -(chadarmstrong) - -- Started looking at moving hit testing from DeprecatedPaintLayer to - -Box model object. - -- jchaffraix helping chadarmstrong get up to speed. - -Add API for layout \[[crbug.com/495288](http://crbug.com/495288)\] (leviw) - -- Meeting last where where the plans for the grand layout refactoring - -was discussed. We agreed that the first step is to define (and over - -time refine) an API for interacting with layout. Meeting notes at - -https://www.chromium.org/blink/layout-team/meeting-notes/may-28-2015 - -- Wrote up a document outlining the plan, sent out to blink-dev. - -https://docs.google.com/document/d/1qc5Ni-TfCyvTi6DWBQQ_S_MWJlViJ-ikMEr1FSL0hRc - -Multipart images \[[crbug.com/308999](http://crbug.com/308999)\] (japhet) - -- Implemented support for multipart image documents. - -Misc Performance - -- Looked into SVG spinner performance and found layout bug where SVG - -paths where regenerated unnecessarily. Fixing the bug should give us - -at least a 50% perf improvement. (esprehn) - -Logistics - -- cbiesinger gardener Friday/Monday. - -- Mid quarter OKR check-in on Thursday at 10am PST.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-22-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-22-2015/index.md deleted file mode 100644 index 028b9584a4b..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-22-2015/index.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-june-22-2015 -title: Monday, June 22, 2015 ---- - -Updates since last meeting (on Tuesday, June 16th): - -Scrolling (skobes, szager) \[crbug.com/417782\] - -- Fixed handling of overflow clip for root layer. - -CSS Flexbox (cbiesinger) \[crbug.com/426898\] - -- Working on intrinsic sizes, found a problem with the spec that needs - -investigation. Handling of form controls (like calendar picker) is - -problematic. - -- Hope to finish up absolut positioning handling this week. - -CSS Grid Layout (svillar) \[crbug.com/79180\] - -- Blocked on code reviews. (svillar) - -- Performance optimizations for alignment. (jfernandez, svillar) - -- cbiesinger to help with reviews. (cbiesinger) - -Region-based multi-column support (mstensho) \[crbug.com/334335\] - -- Still stabilizing multicol. - -- Intend to start working on nested multicol soon, so that we can - -print. - -Add API for layout (leviw, pilgrim) \[crbug.com/495288\] - -- Continuing work on adding API around block layout. Managed to track - -down and solve the performance problems assoscaited with it (turns - -out it was caused by the overhead of extra non-inlined constructors/ - -deconstructors). (pilgrim) - -Isolate core/fetch (japhet) \[crbug.com/458222\] - -- Continued work to separate core/fetch from core and considering finer - -grained separation per resource type. I.e css resource handling - -specific logic could be moved to the css directory. - -Text (eae, drott, kojii) - -- Removing dependency on glyph page tree node from complex path to allow - -it to be removed entierly once the simple path is removed. Trying to - -figure out exactly how it is used and where in order to break the - -dependency. (drott) - -- Unicode variation selectors support fixed for Win/Mac. Linux needs our - -harfbuzz in unofficial builds. (kojii) - -- Investigating bundling our harfbuzz for unofficial Linux. (kojii) - -- Investigating abspos issues in vertical flow. (kojii) - -- CL adding support for word-by-word shaping up for review, performance - -looks very good, will try to land this week. (eae) - -Layout Bugs: - -We currently have 1581 open bugs for the Cr-Layout label, down from 1592 - -last week. - -- Untriaged: 468 (-7) - -- Priority 0: 0 - -- Priority 1: 134 (-1) - -- Priority 2: 957 (-1) - -- Priority 3: 19 - -We need to get the number of bugs down so from now on each weekly update - -will include the number of bugs for each category and the delta from the - -week before. - -Logistics: - -- szager OOO all week. - -- eae gardener Wed-Thu. - -- OKR meeting on Thursday.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-27-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-27-2016/index.md deleted file mode 100644 index b2f507c3561..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-27-2016/index.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-june-27-2016 -title: Monday, June 27, 2016 ---- - -Updates since last meeting (on Monday, June 6, 2016): -Scrolling -- Dealing with a scroll related performance regression: when you change -the existence off scrollbars on a box it goes and sets a flag that -invalidates the width available for children which forces a re-layout -for all children. This happens even if the content width didn't -change. Landed a patch to fix that; it may not be perfect yet but it's -close, needs a few tweaks. (szager) -- Assisted ymalik in investigating smooth scroll jank issues. (skobes) -\[[crbug.com/616995](http://crbug.com/616995)\] -- Working on a fix for incorrect repainting of negative z-index children -on scroll. (skobes) \[[crbug.com/596060](http://crbug.com/596060)\] -Scroll Anchoring \[[crbug.com/558575](http://crbug.com/558575)\] -- Thinking about the scroll anchoring cycle problem -\[[crbug.com/601906](http://crbug.com/601906)\], -will likely add a limit on number of adjustments between user scrolls -per Kenji's suggestion. (skobes) -CSS Flexbox -- Fixing flexbox regressions. Number of open flexbox regression bugs is -steadily decreasing. No new major issues detected or reported latelty. -(cbiesinger) -- Refactored flexbox layout algorithm to make it easier to understand -and maintain. (cbiesinger) -CSS Grid Layout \[[crbug.com/79180](http://crbug.com/79180)\] -- Fixed some small layout bugs related to intrinsic sizes and border/ -padding. (jfernandez) -- Working on grid orthogonal flows. (jfernandez) -- Working on new CSS alignment parsing logic. (jfernandez) -- Get rid of LayoutBox::hasDefiniteLogicalWidth|Height(). (rego) -- Fixed issues with height percentages on grid items. (rego) -- Gave CSS Grid update talk at BlinkOn 6 in Munich. (rego) -- Implemented repeat (auto-fit). (svillar) -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No updates since last week. Morten out for the next two months. -CSS Houdini -- Added support for prefixed properties to the CSS Paint API. (glebl) -- Renamed Geometry to PaintSize for the CSS Paint API to match latest -spec update. \[[crbug.com/578252](http://crbug.com/578252)\] (glebl) -- Enabled worklets and the CSS Paint API as experimental web platform -features. (ikilpatrick) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Working on design doc, will be ready for circulation among the team -post BlinkOn. (eae, ikilpatrick) -CSS Containment \[[crbug.com/312978](http://crbug.com/312978)\] -- No updates since last week. -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Misc minor intersection observer fixes. (szager) -- OOPIF will need to support intersection observer, unclear what -priority or who should own the work. Complicated as it needs to walk -through the frame tree, if a frame is in another process you cannot do -that so some architecture changes are needed to have each process -compute intersections at frame time and have the browser process -process the intermediate results. (szager) -Resize Observer (atotic) -- No updates since last week. -Tables (dgrogan) -- No updates since last week. -Text (eae, drott, kojii) -- Made changes to the font cache to use ref counting which should allow -for better cache invalidation. (drott) -- Found a way to get zero-copy access to the font data tables from skia, -avoiding an extra copy per FontPlatformData. This is potentially a -very big win! (drott) -Misc: -- Rebaseline bot update: wangxianzhu did some excellent work, it should -be operating correctly now. Was previously potentially rebaselining -with stale result as it didn't wait for all bots to cycle before -triggering. One should still closely monitor baselines but it should -be working correctly now. (wkorman) -- Fixing some bugs around paint invalidation rects, -mapToVisualRectandAncestor. Bugs with flipped blocks and relative -position specifically. Likely to also affect intersection observer. -(wkorman) -- Rolled back dropdown change where we reserved extra space as it broke -a number of sites. Trying a new approach that better matches other -browsers. (glebl)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-6-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-6-2016/index.md deleted file mode 100644 index 4640dda12df..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-6-2016/index.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-june-6-2016 -title: Monday, June 6, 2016 ---- - -Updates since last meeting (on Monday, May 23, 2016): -Scrolling -- Landed all of the scrollbar fixes! Finally bringing sanity and good -test coverage to the scrollbar space. (szager) -- Scrollbar regression in web inspector, looks like an incorrect -workaround in client code. Needs further investigation. (szager) -- Found and fixed regression in google spreadsheets, due to js trying -to compensate for scrollbars. (szager) -- All regressions identified thus far have been due to client side js -working around or trying to compensate for scrollbars. Long tail but -new behavior is "better" and we're now more consistent with IE/Edge. -(szager) -Scroll Anchoring \[[crbug.com/558575](http://crbug.com/558575)\] -- No updates since last week. -CSS Flexbox -- Back from vacation, dealing with a couple of regressions including a -release blocker. (cbiesinger) -CSS Grid Layout \[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week. -- Grid talk scheduled for BlinkOn 6 in Munich. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No updates since last week. Morten out for the next two months. -CSS Houdini -- Helping audio folks with worklets, they're in a good space design -wise. Got something that'll work and that we're happy with. -(ikilpatrick) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Working on design doc, will be ready for circulation among the team -post BlinkOn. (eae, ikilpatrick) -CSS Containment \[[crbug.com/312978](http://crbug.com/312978)\] -- Identified a couple of security bugs involving containment and -tables. (eae, dgrogan) -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Changed dispatch to make the order of notifications deterministic. -(szager) -Resize Observer (atotic) -- Initial implementation up for review. It's looking pretty good. We -have a spec we're happy with and that we're implementing. (atotic) -- Two remaining issues to match spec, don't quite know how to expose -that as a part of the API. Plan is to check in what we have behind -a flag and to iterate. (atotic) -Tables (dgrogan) -- Change invalidation logic for border width changes for rows, fixing -a bug with floats. (dgrogan) -Text (eae, drott, kojii) -- More FontCache analysis and looking at lifecycle of FontPlatformData -objects. Goal is to reduce complex path font memory consumption and -achieve enabling complex by default on Android. (drott) -- We're basically leaking FontPlatformData objects and hb_blob_t with -font table information over the lifetime of a renderer. This is -especially bad for single process. (drott) -- Identified a RefPtr cycle issue. (drott) -- Identified an issue of storing full FontPlatformData objects as key -in FontDataCache. (drott) -- Plan to experiment with an LFU eviction plus threshold approach. -(drott) -- Fixed a couple of line brekaing bugs involving element boundaries due -to diffrences in rounding between prefered width calculations and -line breaking. (eae) -Misc: -- Fixed an interop issue wrt list-style inside. We now match the spec -and the Mozilla/Edge behavior. (glebl) -- We now support color fonts, including color emoji, on Windows 8.1 -and later. (kulshin) \[[crbug.com/333011](http://crbug.com/333011)\] -- Using page zoom for device scaling enabled by default on ChromeOS. -(oshima) \[[crbug.com/485650](http://crbug.com/485650)\]
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-8-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-8-2015/index.md deleted file mode 100644 index 42c0c8185e0..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-june-8-2015/index.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-june-8-2015 -title: Monday, June 8, 2015 ---- - -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Ran into problem with hit testing absolutely positioned objects within -a scrollable element. Hit testing code thinks the element is in front -of the scrollbar. (skobes) -- Plan to get back to viewport issue next, once the abs hit testing -issue has been resolved. -- szager getting ramped up on scrolling. -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] -- Done and seems to be sticking, some cleanup/monitoring left but no new -major issues encountered. -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Continuing to update to match spec, progress according to plan. -Misc Warden (dsinclair, pilgrim) -- Containing work to slim-dopwn LayoutObject. (pilgrim) -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Removed old multicol code, yay! (mstensho) -- Fixed multicol fuzzers, and also a completely unrelated fuzzer in the -CSS counters code. (mstensho) -Removing DeprecatedPaintLayer (chadarmstrong) -\[[crbug.com/260898](http://crbug.com/260898)\] -- Current plan is to move hit testing code to stacking node instead of -box model object. This prompted a discussion about the reason behind -the change and the relative merits of retaining the stacking context -concept vs moving hit testing to be self contained and on box model -object. chadarmstrong/jchaffraix/ojan to follow up offline. -Text -- Imported CSS Writing Modes test suites, minor fixes and feedback of -our run results to CSS WG continues. (kojii) -- Unicode variation selectors support in progress, close to complete the -basic support. (kojii) -- Investigating orthogonal writing modes issues. (kojii) -- Investigating abspos issues in vertical flow. (kojii) -Add API for layout (leviw, pilgrim) -\[[crbug.com/495288](http://crbug.com/495288)\] -- pilgrim and ikilpatrick working on getting initial API definition -landed. -Logistics -- dsinclair GPU sheriff (pixel wrangler) this week. -- Planning meeting for Moose on Wednesday, notes will be sent out to -layout-dev, talk to eae if you want to be included.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-16-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-16-2015/index.md deleted file mode 100644 index 21bf2b8a603..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-16-2015/index.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-march-16-2015 -title: Monday, March 16, 2015 ---- - -eae OOO, jsbell taking notes (poorly - apologies for mangling your words and -leaving out any important bits) - -Measure API (jchaffraix) - -- still working on proposal for measure - -- finished layer refactor/renaming - -Flexbox (cbiesinger) - -- almost done w/ first part of flexbox spec change - -- tests missing, importing w3c tests - -Isolate core/fetch (japhet) - -- big class responsible for most violations is mostly done - -- lots of smaller classes to tackle next - -Scrolling (skobes) - -- position fixed works w/ root layer scrolling - -- looking at layout test failures - -Performance Tracking (benjhayden) - -- adding pages to key silk pages benchmarks - -Rename Rendering -> Layout (dsinclair) - -- splitting layout name out into decorated name \[jsbell: didn't catch all of -this\] - -- updating lots of layout tests to have more correct results - -- renderer -> layout object renaming - -- fun content shell resize issue causing subsequent tests to fail, trying to -track it down - -Line Boxes(hartmanng, szager) - -- working through float to layout unit test failures - -- hartmanng: windows - tons of failures, but everything so far looks like it can -rebased, but only a few dozen out of a few hundred reviewed so far - -- szager: made it through nearly all tests on mac, two real regressions - line -wrapping, svg and platform specific layout; digging into those - -Misc: - -- jchaffraix: now working on a release blocker - -- szager: helping out jochen with repo merge - -- wkorman: still ramping up; tell me about merging to release branches...? - -- japhet: other half of time spent on site isolation stuff - -- jsbell: nothing warden-related this week (other than these notes)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-23-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-23-2015/index.md deleted file mode 100644 index c1f0bd2533a..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-23-2015/index.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-march-23-2015 -title: Monday, March 23, 2015 ---- - -Performance Tracking (benjhayden) - -- Added a couple new pages to the key_silk_cases benchmark suite. - -- Continuing counter work. - -- What further pages should be added? jchaffraix has a list. - -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Fixed a flaky test but turns out it is still flaky on one of the - -oilpan bots. Not sure why. Will coordinate with oilpan team to try to - -track down the issue. - -Rename Rendering -> Layout (dsinclair) -\[[crbug.com/450612](http://crbug.com/450612)\] - -- Renamed renderer in layout/svg. - -- Renamed Renderer to LayoutObject in ImageResource and - -LayoutTreeBuilder. - -- Renamed \*styleForRenderer to \*styleForLayoutObject. - -Measure API (jchaffraix) - -- Collected use cases and have enough to justify continued work on - -prototype. - -- Out-of-tree measurements will be tricker than expected, a lot - -trickier. Might be a problem that affects more than measure. - -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Continuing on flexbox work. Progress is slower than expected as - -updating tests takes a lot of time. - -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] - -- Found root cause for a significant chunk of layout test failures, - -including incorrect wrapping in buttons. Turns out leading whitespace - -is to blame. We subtract the width of a space character using a - -floating point representation of the width, introducing imprecision. - -- Hopeful that this'll be the last code change before landing. (szager) - -Isolate core/fetch (japhet) \[[crbug.com/458222](http://crbug.com/458222)\] - -- Continued quested to isolate fetch directory from the rest of core. - -Mostly there. - -- Changed DEPS rule to enforce core/fetch isolation, white listed - -existing bad includes (down to 7). - -Page scale handling (bokan) \[[crbug.com/459591](http://crbug.com/459591)\] - -- Coordinate transformation cleanup in FrameView. - -- Added documentation for coordinate spaces, see - -<https://www.chromium.org/developers/design-documents/blink-coordinate-spaces> - -Text (kojii, wjmaclean, eae) - -- Reviewing test results for bidi and vertical flow in W3C test suites - -with W3C contributors. (kojii) - -- Fixed vertical alignment in vertical flow, one of the biggest failures - -in the W3C test suites. (kojii) - -- Getting back to text iterator work. (wjmaclean) - -- Fixed top Mac crasher, caused by incorrect assumption in HarfBuzz - -CoreText shaper. (eae) - -- Backported fix for reverse_range tab-crash to M41 after it getting - -some media attention. (eae) - -ClusterFuzz - -- Various ClusterFuzz bugs (wjmaclean, jchaffraix, szager) - -- Working on a table layout crash bug, have repro but not sure of cause - -yet, will coordinate with wjmaclean as needed. (wkorman) - -Misc - -- Helped with repository merge issues (szager) - -- Remove old ICU hacks/code from wtf/text now that we control the - -version of ICU used. (jsbell) - -Logistics: - -- hartmanng switching to another chrome team, dsinclair will take over - -in-progress work.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-30-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-30-2015/index.md deleted file mode 100644 index 58585787997..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-30-2015/index.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-march-30-2015 -title: Monday, March 30, 2015 ---- - -We had Rune Lillesveen (rune) and David Vest (davve) from Opera join the - -meeting this week in an effort to better coordinate our work. We also had - -Ian Killpatrick (ikilpatrick) from the Chrome Sydney team join us. - -The massive Rendering -> Layout rename project is done, thanks to - -everyone who helped out and to Dan in particular who did most of the - -heavy lifting! - -The new multi-column implementation was enabled for tests and exposed as - -an experimental web platform feature on Friday! Congrats Morten! - -Updates since last meeting (on Monday, March 23rd): - -Performance Tracking (benjhayden) - -- Continuing work on LayoutAnalyzer and counters. Counters will be - -exposed via trace events allowing us to see the number of layouts on a - -per element type basis. - -- Working on adding a command line flag for android to allow metrics to - -be collected on an attached phone. - -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Fixed the scroll animation test that was failing on the leak bots. - -- Fixed a bug with scrolling to fixed-position #anchor targets. - -- Still tests failing that I need to dig into, and I need to add more - -virtual test suites as right now it is only running fast/scrolling. - -Rename Rendering -> Layout (dsinclair) -\[[crbug.com/450612](http://crbug.com/450612)\] - -- Done. All files have been moved and renamed. The rendering/ directory - -is gone! - -First letter refactoring (dsinclair) -\[[crbug.com/391288](http://crbug.com/391288)\] - -- Fixed first-letter hit testing, discovered a couple of new bugs. - -List marker refactoring \[[crbug.com/370461](http://crbug.com/370461)\] - -- Getting back to list-marker work, will turn the marker into a ::marker - -psedo element. \[crbug.com/457718\] - -Measure API (jchaffraix) - -- Been thinking about supporting measure out-of-tree and trying to come - -up with a good strategy. So far none of the approaches tried have - -panned out. Will continue to experiment and evaluate ideas to guide - -future work. - -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Finished implementing spec changes for min-width auto. - -- Started working on positioning of position: absolute elements. - -- Working on importing w3c test suite for flexbox. - -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] - -- Finished going through the layout test failures for Glenn's patch, and - -landed a few patches to fix tests. All of the remaining test failures - -are OK to rebaseline. - -- Ran the patch through the perf bots, and the results were not as I had - -hoped. There appeared to be significant performance regressions in the - -blink_perf.layout test suite. - -- Working on eliminating wrapper classes (FloatWillBeLayoutUnit) to test - -theory that they explain at least part of the regression. - -- Found a number of places where we use the wrong unit, we need to - -decide exactly where to draw the line between LayoutUnit and float. - -Isolate core/fetch (japhet) \[[crbug.com/458222](http://crbug.com/458222)\] - -- Continuing work to isolate core/fetch from the rest of core. - -Page scale handling (bokan) \[[crbug.com/459591](http://crbug.com/459591)\] - -- Remove old pinch-zoom paths from Blink. - -Blink componentization (pilgrim) \[[crbug.com/428284](http://crbug.com/428284)\] - -- Moving things from core to modules; core/storage and core/timing. - -Text (kojii, wjmaclean, eae, rune) - -- Continued work on text iterator cleanup, fixed naming to be more - -descriptive. (wjmaclean) - -- Working on a change that pulls out the part of TextIterator that - -handles text from the part that handles traversing. (wjmaclean) - -- Profiling line breaking. (eae) - -- Started working on design doc for removing simple text. (eae) - -- Fixed text overflow box bug that blocked the Slimming Paint work. - -(eae) - -- Fixed an assertion problem with baseLayoutStyle which lead to - -finding/reporting a problem causing unnecessary layouts. - -\[[crbug.com/471079](http://crbug.com/471079)\] (rune) - -- Fix vertical flow regression when a major web font site provides - -broken tables. (kojii) - -- Default to complex path more cases in vertical flow. (kojii) - -- Working with W3C and internal experts for bi-di and vertical flow - -issues. (kojii) - -Style resolution (rune) - -- Cache element indices for :nth-child and :nth-last-child selectors. - -Content sizing (davve) - -- Working on content sizing/intrinsic size for HTML and SVG. - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- New multi-column implementation enabled as experimental web platform - -feature! - -Standards (ikilpatrick, slightlyoff) - -- Pushing the layout portion of w3c houdini forward in preparation for - -the next meeting by prototyping. (ikilpatrick) - -ClusterFuzz - -- Trying to reduce an obscure clusterfuzz crasher in RenderBlockFlow. - -(wkorman) - -Discussions: - -\[ cbiesinger's work to import the w3c test suite prompted a discussion - -about w3c tests. \] - -<slightlyoff> Are we mostly writing blink specific layout tests or w3c - -web platform tests today? - -<eae> For regression and performance work we use blink specific layout - -tests pretty much exclusively. For feature work we're trying to move to - -a world where we use web platform tests tests but we're not there yet. - -<jsbell> Dirk (dpranke) started work in tooling to support w3c web - -platform tests, I have headcount for an engineer to take this over and - -work on improving the tooling. - -<jsbell> Once better tooling and procedures are in place we should start - -"strongly encouraging" people to write web platform tests for new - -features. - -<slightlyoff> Can we do that today? - -<jsbell> It is too too painful to do today, tooling needs to be improved - -first.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-7-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-7-2016/index.md deleted file mode 100644 index db50c677d54..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-7-2016/index.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-march-7-2016 -title: Monday, March 7, 2016 ---- - -Updates since last meeting (on Monday, February 29): -We had a new person join the meeting for the first time this morning, -Aleks Totic (atotic). He join Google about two months ago and his -starter project is Resize Observer. Welcome Aleks! -Scrolling (skobes) -- Have a change in review that fixes a bunch of things with scroll -anchoring, with this change it is pretty close to usable on real- -world websites. (skobes) -- Smooth scrolling bugs (have four of them now, yay). (skobes) -- Reacquainted myself with scrolling stuff, was looking into a scroll -related bug that skobes volunteered to take on. (szager) -CSS Flexbox (cbiesinger) -- Worked on flexbox percentage sizing, going well. Will continue this -week. -- Last week, re-landed the fix for scrolling that fixes everything after -a fix by kojii that caused a revert (layout scheduling at a stage -where one should not happen). -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No update since last week - -CSS Houdini (ikilpatrick) -- Kast week in Waterloo with compositor worker folks, had fun getting -compositor worker to work with worklets (that's a lot of work\* words!) -and with a cleaner API. Have a new API version, will try to move into -trunk sometime later this month. -- About to commit a small change for main frame worklets API. -- Want to get paint rendering context 2d check-in this week. -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Continued making progress on the box layout api, have sense of size of -problem. Basically every element will have to have a layout item -instead. About ~40% of them have their own element specific things -which means that we'll need element specific block element API. -Working through that list and figuring out the hierarchy. Projecting -how large of a project it is. (pilgrim) -- So far most element specific APIs have been pretty small with only a -method or two, on the leaf node level. a lot of the higher level -elements (like layout image, layout media, layout box etc) have more -complicated APIs that will take more time. (pilgrim) -- Spent much of last week burning down the list of tasks for the Line -Layout API. Only size invalid calls left, hopeful then we can change -the constructors and add include guards this week then call the Line -Layout API done. (dgrogan) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- No update since last week - -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Landed Layout Containment! <https://codereview.chromium.org/1530303003> -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Landed a couple of intersection observer changes last week, have a few -more coming but no longer a full-time endeavor. (szager) -- Focus on bugs this week. (szager) -Text (eae, drott, kojii) -- Coming back from tok, working on remaining on emoji font fallback. -After coordinating with android team changed how we get the fallback -font. When android releases the SDK preview for N then we can activate -fitzpatrick modifiers. Required further segmentation fixes. (drott) -- Fixed line-breaking issues with emjoi combiners. Not yet in ICU, -implemented on top of it for now. Will move to ICU over time. (drott) -- This week, plan to add unit tests for line breaking and then land and -coordinate with Android team. (drott) -- Fixed how we query the operating system for font settings relating to -font smoothing and LCD subpixel rendering on Windows. Previously we -tried to read the registry values from the rendering which wouldn't -work with the sandbox lockdown, changed it to query the OS from the -browser process and pass it down to the renderer. Fixes issues where -we don't respect the users font settings and also ensures consistency -across chrome and blink. (eae) -- Discovered a pretty bad perf regression for break-all. Our performance -has always been bad but got worse with complex text. Investigating and -have some ideas as to how it can be fixed. (eae) -HTML Tables (dgrogan) -- No update since last week - -Misc -- Started working on how we render table backgrounds with collapsed -borders, pulled a thread and the whole thing started to unravel. -Discovered out that collapsed borders are painted in a crazy way, -trying to clean up. (atotic) -- Spent a full day helping wkorman with the rebaseline bot, makes me -realize how happy I am that I left infra and moved to blink where -things are sane and predictable. (szager) -- Still dong analysis work for writing modes. (wkorman)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-9-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-9-2015/index.md deleted file mode 100644 index c48411c68aa..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-march-9-2015/index.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-march-9-2015 -title: Monday, March 9, 2015 ---- - -Performance Tracking (benjhayden) - -- Continuing work on exporting counters. - -- Adding layout metrics to the blink performance tests. - -- Working on simplifying the layout metrics implementation. - -Scrolling (skobes) \[crbug.com/417782\] - -- Ran into an issue with paint invalidation rects that block the later - -scroll implementation. - -Rename Rendering -> Layout (dsinclair) \[crbug.com/450612\] - -- Renamed RenderTreeBuilder to LayoutTreeBuilder. - -- Renamed various methods; renderer() to layoutObject(), rendererIs\* to - -layoutObjectIs\*, and createRenderer\* to createLayoutObject\*. - -Measure API (jchaffraix) - -- Spent much of last week discussing the measurement API with - -stakeholders. - -- Trying to determine whether there is a use case for the measure API in - -isolation or if it only makes sense as part of as part of custom - -layout. If you have a use case reach out to jchaffraix. - -- No doubt that there is need for a text metrics API. - -Line Boxes (hartmanng, szager) \[crbug.com/321237\] - -- Dealing with layout test failures, five-ish tests needs debugging on - -linux, looking into windows at the moment. Mostly false positives, - -some actual failures. (hartmanng) - -- Dealing with layout test failures on Mac. (szager) - -- Spent a lot of time fixing broken tests, eae argued this might not be - -the best use of my time. Will mark broken tests as broken going - -forward to unblock the conversion work. (szager) - -Flexbox (cbiesinger) \[crbug.com/426898\] - -- Flexbox work is taking a bit longer than expected, the win-width auto - -change took all of last week. Still dealing with test failures. - -- Two week estimate was a bit too optimistic. - -Isolate core/fetch (japhet) \[crbug.com/458222\] - -- Continuing on isolating the fetch directory from the rest of core. - -Blink componentization (pilgrim) \[crbug.com/428284\] - -- Working on modularizing various things in core, storage is now - -modules/storage. - -- Next up is (blocking on fetch) is core/xml. - -Text (kojii, wjmaclean, eae) - -- Continuing work on text iterator. Trying to modularize it to make it - -easier to understand. Many misnamed and confusing methods, tyring to - -rationalize that. (wjmaclean) - -- Line breaker optimizations based on profiling data resulted in ~10% - -speedup for line-layout and text perf tests. (eae) - -- FontMetrics::ascent(), descent(), and height() optimizations resulted - -in up to 15% speedup for complex text perf tests, ~3-5% for simple - -text. (kojii) - -Misc - -- Helping jochen on git repository merge. Their strategy is sound and - -they are doing the right thing. Will help with infra work as needed. - -(szager) - -- Created minimized tests case and tracked down root cause for starter - -bug, was an invalidation bug. (wkroman) - -Logistics - -- cbiesinger in SF next week. - -- eae out Tue-Thu this week and Mon-Tue next week. - -- wjmaclean out Thu-Fri this week and all next week. - -- paulmeyer won't be working on layout for the next couple of weeks.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-may-16-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-may-16-2016/index.md deleted file mode 100644 index 5cba2271f7e..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-may-16-2016/index.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-may-16-2016 -title: Monday, May 16, 2016 ---- - -Updates since last meeting (on Monday, April 25, 2016): -Scrolling -- Wrapping up overflow: auto work. Split up into three separate patches, -first one landed last week and fixes scrollbars in general in the -presence of "interesting" flex direction, writing mode and text -direction combinations. \[[crrev.com/392981](http://crrev.com/392981)\] (szager) -- The second patch (wip) overhauls how the flex algorithm handles -overflow: auto scrollbars. It basically makes it much clearer and -reduces unnecessary work that flex algorithm has to do to handle the -presence of scrollbars. Shouldn't have any visible changes. (szager) -- The third patch changes how intrinsic width is calculated in the -presence of scrollbars. It's a major change that will improve how -things look and will fix some incorrect coordinates that are reported -back. Right now, for instance, a zero width box width vertical -overflow will report a clientWidth of -15px. Relatively small change -but I think it'll be nice and improve things. Some fun interactions -between layout and paint clipping. (szager) -- Added a new ref test that tests all combinations and it'll keep us -honest going forward. Looking into up-streaming it. (szager) -Scroll Anchoring \[[crbug.com/558575](http://crbug.com/558575)\] -- Fixed a scroll anchoring subpixel positioning bug, was very annoying -as text kept flickering during load when anchored. (skobes) -- Have a solution for interaction between scroll event handlers and -scroll anchoring. Detects when it's bouncing between two locations and -prevents it. (skobes) -CSS Flexbox -- Flexbox specification discussions at the CSS Working group face-to- -face last week, made progress on intrinsic width calculations among -other things. (ikilpatrick) -CSS Grid Layout \[[crbug.com/79180](http://crbug.com/79180)\] -- Floated grid containers in Blink (rego) -- Fix computed style with distribution offsets (rego) -- Place positioned items with vertical writing modes (rego) -- Grid layout reviews (svillar) -- Position resolution with auto-repeat tracks (svillar) -- Auto-repeat tracks computation (svillar) -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Multicol / fragmentation is in a known good state. (mstensho) -CSS Houdini -- Last week was the Houdini face-to-face meeting. We didn't talk much -about the CSS Paint API, it's reasonably stable. We did, however, -spent about four hours talking about the CSS Layout API. -(ikilpatrick) -- Moving in a pretty good direction. The other vendors seemed pretty -happy with the overall shape of the API. Plan to update the spec -proposal in time for TPAC. (ikilpatrick) -- Plan to work on the worklets spec this week, mainly on the security -APIs. (ikilpatrick) -- Start design doc for off-main-thread worklets. (ikilpatrick, flackr) -Add API for layout \[[crbug.com/495288](http://crbug.com/495288)\] -- Finishing up report on line layout API. (dgrogan) -- Continued LayoutView/FrameView conversion. (pilgrim) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- Started working on design doc. Will share draft with team in a few -weeks. (eae) -CSS Containment \[[crbug.com/312978](http://crbug.com/312978)\] -- One remaining issue arund interaction between contain: paint and will- -change: transform. Will try to track down the root cause this week in -preparation for shipping by default. (eae) -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Shipping in M51. -Resize Observer (atotic) -- Spent a day in SF selling Resize Observer to Mozilla, IE/Edge, and -Safari. They seemed to like it, no major problems. Mozilla already -filed a tracking bug. Plan to send out an Intent-to-Implement later -this week. (aleks) -- Have a pending implementation, working with szager to get memory -management right with regards to lifetime and the oilpan GC. (aleks) -Tables (dgrogan) -- Microsoft working on updated CSS Table compatibility specification. -- Made progress on a couple of table bugs, have a good handle on the -root cause and will resume work this week. (dgrogan) -Text (eae, drott, kojii) -- Looked at an issue where we need to upconvert to the complex path on -Android for small-caps font font-variant-numeric. (drott) -- Continued android memory regression, trying to figure out where the -extra memory is spent and why it only affects Android. Independently -found the same issue that tzik and kojii identified where glyphs are -double cached. (drott) -- Added instrumentation for the glyph bounds cache. (drott) -- small-caps and font-variant-numeric will ship in M52! (drott) -- Resumed work on change to render unicode control characters in -accordance to spec. (eae) -Misc: -- Discussed test strategy for blink wrt w3c and web-platform-tests. -Learned about gecko process for keeping tests in sync. (jsbell) -- Spent the last two weeks doing general block layout clean up and -refactorings. Moving code and logic to where it makes more sense. -(mstensho)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-may-4-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-may-4-2015/index.md deleted file mode 100644 index fcaf58fcb33..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-may-4-2015/index.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-may-4-2015 -title: Monday, May 4, 2015 ---- - -Performance Tracking (benjhayden) - -- Trace viewer/rail perf work. - -- Layout Analyzer powered by UMA. - -Scrolling (skobes) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Improved unite tests for scrolling. - -- Removed m_inProgrammaticScroll scroll flag from FrameView. - -- Removed m_viewportLayoutObject from FrameView. - -Line Boxes (szager) \[[crbug.com/321237](http://crbug.com/321237)\] - -- Performance data looks a lot better, some micro benchmarks still show - -a slight regression but within error margin. Plan is to try to land - -this week. - -Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Discussions around absolut positioning within flexbox. - -- Updated handling of min-width/min-height. - -List marker refactoring (dsinclair) -\[[crbug.com/370461](http://crbug.com/370461)\] - -- Found solution for subtree modification problem, CL up for review. - -(dsinclair) - -- Change to move layout tree modification from layout walk to - -NotifyChange. (dsinclair) - -Misc Warden (dsinclair, pilgrim) - -- Moved mustInvalidateBackgroundOrBorderPaintOnHeightChange from - -LayoutObject to LayoutBox and made it private. (pilgrim) - -- Made updateShapeImage, updateFillImages private. (pilgrim) - -- Renderer to LayoutObject rename almost done, only editing and paint - -remain. Yay! (dsinclair) - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- All known fuzzers fixed. - -- New multicol implementation landed today (r194883). - -Layout refactoring (esprehn, ikilpatrick, cbiesinger, ojan, leviw) - -- Meetings and discussion contined last week and this week. Plan is to - -have one or more concrete proposals by the end of BlinkOn. - -Logistics - -- Most of the team in Sydney next week for BlinkOn 4, many travel down - -this week. - -- No meeting next week (due to BlinkOn), send updates (if any) to eae.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-november-23-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-november-23-2015/index.md deleted file mode 100644 index dc46b7add06..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-november-23-2015/index.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-november-23-2015 -title: Monday, November 23, 2015 ---- - -Big update this weeks as we didn't have a meeting during BlinkOn and I -apparently forgot to send out notes for last weeks meeting. -Updates since last meeting (on Monday, November 2nd): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Unified animation curves across Blink and CC. They now share the same -curve. (skobes) -- Looking into RTL scrollbar placement for root layer scrolling. -(skobes) -- Re-started work on root layer scrolling after focusing on smooth -scrolling and bugs for a few weeks. (skobes) -- Landed fix for scrollbar clipping, basically scroll containers should -clip their scrollers but they don't. Chocking they didn't but now -works as expected. (skobes) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Fixed a number of regressions relating to recent changes in behavior. -(cbiesinger) -- Spent some time not fixing a flexbox bug for a change, had to do with -flexbox and scrollbars. cbiesinger came in and stole my thunder. -Thank you :) (szager) -- Fixed the release blocker szager was working on. Was investigating a -different bug that turned out to be the same. (cbiesinger) -- Fixed another release blocker, affecting google translate. -(cbiesinger) -- Moar release blocking bugs! (cbiesinger) -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- Simplified interface of GridResolvedPosition. (sergio) -- Grid sizing under min|max constraints with implicit sizes. (sergio) -- Added support for implicit grid before explicit grid. (rego) -- Absolutely positioned items inside grid adjustments. (rego) -- Landed a small refactoring of grid layout code. (rego) -- Gave talk at BlinkOn 5 about recent work on grid layout and what the -future holds. (javif) -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Bombing Levi with multicol patches as usual, and he's an unstoppable -reviewing machine. -- The way it looks now, we're one patch away from being ready to -introduce multicol for printing. Hopefully, I'll file that patch today -or tomorrow, and then add support for printing later this week. But -we'll see... -CSS Houdini (ikilpatrick) -- Writing design doc for worklets, will circulate for feedback at EoW. -- Custom line layout discussions and hack-a-thon in Tokyo two weeks ago, -we came up with two proposals that we're refining and will prototype. -(eae, shans) -- Planning to re-implement ruby support on top of said API, got input -from kojii and started experimenting. (eae) -Standards work -- Published 2nd CR of CSS Writing Modes Level 3. (kojii) -- Published UTR#50 Unicode Vertical Text Layout revision 15, supporting -Unicode 8.0. (kojii) -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Line layout, last patch got rid of it in LineText delayed due to -conflicting advice and opinions. (pilgrim) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Plan to send Intent to Implement this week. -- Have pending spec patch that needs to be upstreamed. -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Everyone understands how it should work but managing the lifetime of -the objects are extremely hard is it involves relationships between -two objects with very different documents and lifetimes. Makes it very -tricky. You'd think oilpan would make it easier but so far it seems -that the opposite is true. There is an obvious leak and it's not clear -how to resolve that without having to do a lot of manual bookkeeping. -Trying to figure out a way to make it work in an oilpan world, still -not clear if that is even possible. Working with adamk to try to -figure it out, getting closer but haven't nailed it yet. Similar to -mutation observer in that it is really difficult not to leak. (szager) -- Once lifetime management has been resolved the plan is to get it into -the code base behind a flag. Then to have people give it a try and -kick the tires while, at the same time, continue to spec work and then -ship (unflag) early next year in beta, assuming spec work isn't -delayed. (szager) -Text (eae, drott, kojii) -- Spent time helping drott investigate an emoji joiner issue on android. -(workman) -- Fixed emoji joiners on Windows. (drott) -- Worked on regression due to the new shaping code where a secondary -font wasn't loaded correctly. Turns out to be a copyright protection -strategy used by some fonts. Used on -[virginamerica.com](http://virginamerica.com/) and a few other -high profile sites. (drott) -- Wrote and test emoji complex path on Webview_shell, merged to M47 and -M48 (Thanks to wkorman@ for sharing Android tricks and test phone), -reached out to WebView TL in LON regarding final verification on the -Beta build. (drott) -- Investigated T-crossbar issue: woff2 or freetype hinting issue, -[crbug.com/550523](http://crbug.com/550523). (drott) -- Prepared CL for font code memory infra instrumentation, instrumenting -word cache done, but larger remaining issue with tracking web font -blobs down to SkTypeface. (drott) -- Discussed deduplicating fallback font streams on linux with skia -folks, fmalita@ added API to SkFontconfigInterface, which on closer -inspection unblocks as, we can implement deduplication on Blink side -[crbug.com/524578](http://crbug.com/524578). (drott) -- Prepared harfbuzz roll, failed building on Mac, filed issue, fixed by -behdad, new release expected. (drott) -- Investigating Houdini custom line layout and ruby on top of it. -(drott) -- Investigating bidi-isolate by default for elements with dir attributes, -working with WebKit, Gecko, Edge, and W3C I18N WG. (drott) -- A few issues in bidi-isolate were found, working on them. (drott) -- Changed the life time of ShapeCache instances and the logic for cache -invalidation. Resulted in a massive layout speed up, more than -offsetting the regression we saw on a few micro benchmarks following -the switch to always use the complex text path. Unblocks the effort to -ship complex-by-default. (eae) -- Started looking into further tweaks to ShapeCache lifetime and -invalidation, more work to be done. Should reduce memory usage. (eae) -HTML Tables (dgrogan, jchaffraix) -- Investigating table bugs with jchaffraix. Looking into an issue where -there there are too many borders on our tables due to a bug in border -collapsing. (dgrogan) -- Helping dgrogan ramp up on tables. Here every Monday for that reason. -He has one patch up, looking good! (jchaffraix) -Bug Health -- Both eae and jchaffraix spent a lot of time last week doing bug triage -as per usual. Another two weeks or so should see our untriaged backlog -go town to zero! Yay! -- Total bug backlog, down by ~18%. If we keep this level of effort up we -should be able to hit our goal of a 20% reduction by EoQ. (eae) -Misc -- skobes, drott, ikilpatrick, and javif presented at BlinkOn. All their -sessions where well attended and very well received. Thank you! -Videos should be available within a week or two. (eae) -- Windows FixIt last week. (wkorman) -- Presented at QConf and Chrome Dev Summit. (ikilpatrick) -- Plan to get back to rebaseline bot on the bot this week. Looked into -file-locked bug where we cannot delete files due to them being locked. -Fun time untangling all the threads. (wkorman) -- Start flipped blocks work as per outlined earlier! (wkorman) -- Spent time last week working on a background image spriting bug that -we've had forever. We didn't get around to fix it back when we -implemented subpixel layout. Apple finally fixed it, in a way that's -very different from how we're approaching it. Taking a lot of time to -get things exactly right because we decide on the exact box to take -before making a final snapping decision during layout. Have patch that -is mostly ready, should be able to finish it this week. (leviw) -- Looking at a crashing big in frame loader. (skobes) -Logistic -- Looks like a quite week with everyone back in their home office. -- Short week in the US due to Thanksgiving (Thu-Fri off).
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-november-30-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-november-30-2015/index.md deleted file mode 100644 index 43295238917..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-november-30-2015/index.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-november-30-2015 -title: Monday, November 30, 2015 ---- - -Updates since last meeting (on Monday, November 23rd): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Flag specific expectations for root layer scrolling landed. (skobes) -- Have patch for RTL scrollbar placement, investigating custom scrollbar -test failures. (skobes) -- Smooth scrolling; working on main thread toggled, compositors driven -animations, a little complicated but have a prototype. On track to hit -OKR. (skobes) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Still problems with flexbox/scrollbars (need to add height of -scrollbar to flex basis). Beed to sync with cbiesinger, original -problem with devtools still exists. Need to figure out how to test and -how to proceed. (szager) -- Release blockers and misc flexbox bugs. (cbiesinger) -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Found out that support for column-span:all is really broken in nested -fragmentation contexts. So that's what I'm currently working on. If I -find nothing else after this, I'll then be ready to file the patch -that adds support for printing multicol. -CSS Houdini (ikilpatrick) -- Working on design doc for worklets, will finish today and circulate. -- Plan to finish up the worklet spec this week and started feeling out -the, as of yet unnamed, new canvas spec (splitting RenderContext2D -into discrete parts). -- Start writing patches for worklets. -Standards work -- Preparing to upstream flexbox tests, we now have a version of check- -layout that runs on top of testharness. (cbiesinger) -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- No update since last week. -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Plan to send Intent to Implement this week. -- Have pending spec patch that needs to be upstreamed. -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- The memory model for intersection observer is really complicated, -especially when multiple documents are involved. Still not sure about -how it fits in with oilpan. Making solid progress but getting the -memory model right is tricky and time consuming. (szager) -Text (eae, drott, kojii) -- Updated memory infra CL (tracking font related memory usage), had -discussion with memory team. We might want to move some allocation to -use partition alloc. (drott) -- Verified ZWJ emoji android fix. (drott) -- Started proparing cl for removing simple text, there are a few -dependencies left, addressed two but still a few left. One on svg -that might have perf impact. (drott) -- HarfBuzz roll to 1.10, might want to backport to m48. (drott) -- Improved cache key and invalidation logic for shape cache, should -lead to reduced memory usage. (eae) -- Fixed a bunch of text related ASSERT. (eae) -- Always use complex text enabled on trunk. (eae) -HTML Tables (dgrogan, jchaffraix) -- Brain dump from jchaffraix to dgrogan continues. -- Trying to figure out the madness that is border collapsing and come up -with a plan. (dgrogan, jchaffraix) -Bug Health -- On track to not only meet but exceed bug health OKRs: -- Reduced unconfirmed/untriaged bug count by 60% (690 down to 377), -OKR is 50%. -- Reduced total bug backlog by 16% (2310 down to 1927), OKR is 15%. -- A lot of hard work by the entire team, thank you everyone! Let's -keep this up! -Misc -- Worked on checked-layout.js that works with test harness, allows for -upstreamable layout tests. (jsbell) -- Added support for flag specific test expectations, will greatly aid in -doing feature work and large refactorings going forward. (skobes) -- Fixed CounterNode crasher. (eae)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-12-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-12-2015/index.md deleted file mode 100644 index f4f3c68b120..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-12-2015/index.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-october-12-2015 -title: Monday, October 12, 2015 ---- - -Updates since last meeting (on Monday, October 5th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Misc root layer scrolling fixes. (skobes) -- Plan to start working on smooth scrolling this week. (skobes) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Fixed height calculation to consider tallest column. -- FIxed handling of minimum for fill available. -CSS Grid Layout (svillar, jfernandez, rego) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Reworked column rebalancing. -- Fix handling for block pagination struts. -- Changes to break handling. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- API fixes fot SVG text chunk handling. (pilgrim) -Text (eae, drott, kojii) -- Fixed further selection painting bugs. (eae) -- Fixed measurement for RTL list-markers where we reversed the -text twice causing incorrect ordering and metrics. (eae) -- Continued work on shaper driven segmentation, will start to -land patches upstream this week. (drott) -- Unprefixed CSS Writing Modes landed, working on some follow up -fixes. (kojii) -- Trying to better integrate CSS text code path with SVG text code -path for vertical flow. (kojii) -- Cleaning up tests in CSS WG and specs for coming CR. (kojii) -Misc: -- drougan started on his first bug, getting familiar with the -Blink code base. -- drott hit size and encoding limits in Skia test infra, working -with them to resolve it. -- Change in review for list marker spacing. (wkorman) -- Lots of tracing, test case fiddling, and reading of code for -WebViewImpl::layout xploring whether there are further layout/paint -optimizations we can make. (wkorman) -- Continuing work on documentation (deep dived into reflection to -understand the design - <https://codereview.chromium.org/1391943005> + -more PaintLayer documentation). (jchaffraix) -- Mostly done documenting important objects (hopefully I could finish -these this week), after that is deep diving into features (transform, -paint invalidation, baselines...). (jchaffraix) -Logistics: -- eae & leviw in Helsinki to work with drott until Thursday. -- cbisinger on vacation this Monday. -- drougan back from recruiting trip.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-19-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-19-2015/index.md deleted file mode 100644 index 202ad6a86ff..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-19-2015/index.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-october-19-2015 -title: Monday, October 19, 2015 ---- - -Updates since last meeting (on Monday, October 12th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Fixed a regression from coordinated scrollbars. (skobes) -- Made progress on getting RTL working with root layer -scrolling (but still broken for various reasons). (skobes) -- Fixed an issue where elements become unscrollable -after an animation. (skobes) -- Discovered the cc side of smooth scrolling has been totally -broken for a while due to inner/outer viewport issues; ymalik -has a fix pending. (skobes) -- Working on getting unit tests passing with root layer scrolling -turned on, long slog. Making progress. (szager) -- Got the RTL issue (where the initial position of the scrollbar -was incorrect for RTL frames) all about figured out, on to the -next one. (szager) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Spent some time last week going through flexbox bugs, doing -bug triage and fixing issues. -- Discovered a couple of new fun bugs involving negative margins -where the resulting flexbox could end up getting a negative size. -Turns out the spec isn't clear on the correct behavior, working with -tab and fantasi on getting it clarified. -CSS Grid Layout (svillar, jfernandez, rego) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No updates since last week. -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- Working on the usual suspects; nested multicol, get it good enough for -printing, and so on. -- Also working on fixing a blocker regression pertaining to printing an -overflowing flexbox inside a bottom-aligned fixed positioned box -(in the Chrome UI). The fix is straight-forward (believe it or not), but -I'm struggling with coming up with a LayoutTest. Looks like I'll have -to fix the printing test framework first (or possibly even the engine itself). -CSS Houdini (ikilpatrick) -- Last week, working on the isolated worker spec which is a spec -about a separate js exec context for all custom houdin stuff. -- Focusing on the CSS Paint API spec this week. -- Preparing for TPAC, will be there for the entire event. Will gladly -bring up issues or concerns on behalf of others. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Still working on the line layout api, going thgough layout svg, -converting calls to go through the API. (pilgrim) -- Got a couple of smaller patches in last week, working on a -larger one this week. Probably about another two weeks of -SVG api work remaining. (pilgrim) -Text (eae, drott, kojii) -- Share more code between SVG text and CSS text. (kojii) -- Fixed fonts when lang attribute is set, investigation continues. (kojii) -- Investigate inheritance of anonymous inline and partial fix. (kojii) -- Pushing Writing Modes Level 3 to CR. (kojii) -- Proposed Update of Unicode Vertical Text Layout (UTR#50) -to publish soon. (kojii) -- Working on line break spec issues with CSS WG and Unicode. (kojii) -- Enabled complex text as experimental web platform feature, this -results in _all_ text going down the complex text path. If it sticks the -plan is to enable it for stable and then (eventually) delete the simple -text code path (yay!). Required 90% of all layout tests to be -rebaselined, due to problems with our tooling this mostly had to be -done manually. (eae) -- Fixed a bunch of ref-tests to make them more resilient against -minute text rendering differences. (eae) -- Speculative fix for a top windows crasher where fontMetrics is -null during line height computation. (eae) -- Working on getting shaper-drive-segmentation landed, very close -now but a few issues remaining. Should land this week! (drott) -Misc: -- Have a batch of bugs around lists, selection gaps, and caret. (wkorman) -- Meeting with joel about pick up running rebaseline bot. Will -run it on interim basis. (wkorman) -- Paint performance optimizations for slimming paint v2 where the -compositor side of things wants to make use of rtrees, needs -bounds of display items. Will change to accumulate during paint, -should lead to a nice performance win. (wkorman). -- We'll likely need to pull someone off their current project to help out -with intersection observer, it's a top blink-level priority for the quarter -and we need to make sure we make progress on it. (eae) -Logistics: -- jsbell gardening this week and helping out with cr-blink triage.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-5-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-5-2015/index.md deleted file mode 100644 index de9cb11fbfc..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-october-5-2015/index.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-october-5-2015 -title: Monday, October 5, 2015 ---- - -Updates since last meeting (on Monday, October 5th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Landed change that enables coordinated scrollbars everywhere. (skobes) -- Landed unit test fixes for root layer scrolling. (szager) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Worked on the flexbox layout tests, in the W3C repository. The W3C -repository is the source of truth that we pull in periodically. -- Misc flexbox bug fixes. -CSS Grid Layout (svillar, jfernandez, rego) -\[[crbug.com/79180](http://crbug.com/79180)\] -- Reviewed several grid layout patches. (svillar) -- Working on grid container height sizing when there are min|max -content constraints and min|max height restrictions. The CL is -ready for review after revamping the original design. (svillar) -- min-width|height: auto fixes for vertical writing modes. (svillar) -- Working on definite size detection for abspos items. (rego) -- Fixed abspos items behavior with implicit lines and unknown named -lines. (rego) -- Content and self alignment fixes for spanning items. (jfernandez) -- Implemented auto margin alignment for grid items. (jfernandez) -- Added 0fr support for track sizes. (jfernandez) -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Fixed pagination strut propagation for blocks. -- Removed unused clearPaginationInformation from LayoutState. -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Landed two layout API changes that added a couple of methods missing -form the API around scaling. (pilgrim) -- Converted inline text box painters to not use the line layout api but -also not call any methods on inline text box. (pilgrim) -- Houdini spec preparation work, supporting style team. (leviw) -Text (eae, drott, kojii) -- Fixed selection painting on high-DPI where before we would clip the -selection rect incorrectly causing thin white lines between certain -words due to rounding. Removed clipping entirely as it is no longer -needed in a post selection-gap-painting world. (eae) -- Continued on layout tests failures for shaper driven segmentation, -found issue in HarfBuzz relating to end of run handling for webfonts. -Working with behdad to resolve it. (drott) -- Discussion on blink-dev around custom text rendering by exposing -access to fonts. (drott) -- Will continue working on remaining issues for shaper driven -segmentation this week. Outstanding questions around small caps -handling. (drott) -- Selection highlighting in vertical writing mode (ltr) relating to -selection gap painting removal. (wkorman) -Misc: -- Fixed float stable blocker. (szager) -- drougan looking for good starter bugs. -- Working on test infrastructure for runtime enabled features to ensure -that features are reset between test runs by auto generating the js -hooks rather than having everyone roll their own. (wkorman) -- Misc stable & beta blocker bugs. (leviw) -Logistics: -- eae & leviw in Oslo this week, visiting Opera and then head to -Helsinki to work with drott early next week. -- pilgrim on vacation Wed-Fri. -- cbisinger on vacation next Monday. -- drougan on recruiting trip rest of week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-september-14-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-september-14-2015/index.md deleted file mode 100644 index 6bc0325ef22..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-september-14-2015/index.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-september-14-2015 -title: Monday, September 14, 2015 ---- - -Updates since last meeting (on Monday, August 31st): - -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Landed flexbox change for overflow auto, it's causing a regression - -on Mac only in how scrollbars are pained. Hope to sync up with skobes - -about that today and resolve it. Other than that no problems and looks - -like it'll stick. (szager) - -- Landed change running a comb through the scorll bounds code. Should - -be pretty reliable for getting minimum and maximum scoll positions - -now, while it wasn't before. Likely to have fixed a bunch of off-by- - -one scroll bound bugs. (szager). - -- Intent to fix regreision and talk about next step for root layer - -scrolling with skobes this week. (szager) - -- sataya.m from Samsung has fixed almost all of the scrollbar tests, - -these are mostly related to custom scrollbars. (skobes) - -- Trying to figure out coordinated scrollbars this weeks, turn on for - -just the main frame and only for certain platforms. Would be nice to - -use this more broadly. (skobes) - -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Need to re-think approach to deprecating sizing keywords due to leaks - -in CSS parser which resulted in the patch to be reverted. - -- Will sycn up with ojan re f2f. (cbiesinger) - -- At CSS face-to-face it was decided to standardize on chrome-impl of - -table fixup (i.e. not do it) which will save us some work. (ojan) - -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] - -- No update since last week. - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- Fixed handling for unbreakable blocks at top of a column/page. - -- Updated handling of style changes to ensure they happen in tree order - -for multicol. - -- Fixed min-height to not have an effect if content is taller than - -multicol and height is set to auto. - -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] - -- Still working on line layout api, down to some asserts and debug only - -code before we can get rid of the LayoutObject in InlineBox. (pilgrim) - -- API is as broad as it needs to be, has all the relevant methods, - -thinking about next steps. (pilgrim) - -Text (eae, drott, kojii) - -- Continued work on shaper driven segmentation: (drott) - -- Implemented an iterative approach so that for each font we can - -collect all segment supported by the font. - -- Started to work on system font fallback, with the font fallback - -iterator now also able to collect and fallback on system fonts. - -- Sent out mail about approach to modernazing system font fallback, - -on Windows 8.1+ and Mac there are sane fallback APS we could use. - -Android has a fallback XML file that is resonable and on linux - -fontconfig provides the necesarry information but returns way - -too many fonts. (drott) - -- Thinking about vertical text, needs reimplementaiton. One idea is to - -merge script iteartion with orientation. Trying to implement run - -segmenator which uses the script iteator and an orientation iteratior. - -Will continue workin on it this week. (drott) - -- Working on complex path blockers and recent regressions. (kojii) - -- Working on CJK font fallback issues. (kojii) - -- Updating CSS Writing Modes spec for resolutions from F2F. (kojii) - -- Investigating unprefix planning for Writing Modes. (kojii) - -- Writing Modes spec issues/edits, unprefix planning, and tests. (kojii) - -- Discussing with drott@ on run segmentation for vertical flow. (kojii) - -- Looking into high-priority fonts issues. (kojii) - -Misc: - -- Removed webkit linebox contained. (wkorman) - -- Happy about juliens documentation improvements. (wkorman) - -- Reverted patch to remove old containg block logic as it turns out it - -was still needed. Will revisit and try again with tests. (ojan) - -- Fixed handling of floats for blocks that establishes a new formatting - -context. (mstensho) - -- Fixed float margin logic to not collapse margins on page or column - -boundaries. (mstensho) - -Logistics: - -- leviw in Amsterdam for a Polymer summit, back on Thursday.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-september-28-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-september-28-2015/index.md deleted file mode 100644 index 5d4bfbd48c4..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/monday-september-28-2015/index.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: monday-september-28-2015 -title: Monday, September 28, 2015 ---- - -Updates since last meeting (on Monday, September 14th): -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] -- Getting closer to enabling coordinated scrollbars everywhere. Currently -enabled everywhere on Mac and Android but only for the main frame on -Windows and Linux. With these changes the main frame will no longer be -a special case and will instead use the overflow scroll -implementation. (skobes) -- Have two patches out for review that change how we paint scroll -arrows. Once those have landed we can turn on coordinated scrollbars -on all platforms. (skobes) -- Will spent some time doing bug triage this week. (skobes) -- Looking to land patch to web scrollbar theme painter, starting to have -a lot of dependent bugs, lots of of duplicate bug reports. (szager) -- Leading space char clusterfuzz bugs. (szager) -- Pushing forward to enable root layer scrolling for layout tests and -starting to triage failures. (szager) -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] -- Adding a use-counter for deprecated intrinsic sizing. -- Fixing up css working group test suite for flebox, hope patches will -be accepted/merged soon. -- Import css test suite into layout test. Plan is that the css working -group repository is the source of truth that we mirror periodically. -- Plan to upstream some more of our tests. -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week. -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] -- Multicol balancing refactoring (do it after layout). The multicol part -of it has been ready for weeks, but before landing it, some changes to -strut handling in the LayoutBlockFlow neighborhood are required. I've -landed some simplification, clean-up and bugfixing CLs in the area on -my way. Hopefully it's soon sensible enough to hold my changes without -breaking under its own weight. (mstensho) -- Still working on pagination strut rewrite. Want to get it right and as -pretty as possible first before landing. (mstensho) -Add API for layout (leviw, pilgrim, ojan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Landed several large line layout patches, after one that is pending -review we will have gotten rid of all LayoutObject references in -InlineTextBox, i.e. we'll use go through the API for all layout calls. -(pilgrim) -- Working our way up the hierarchy to get rid of the remaining calls not -using the API in InlineBox. (pilgrim) -Text (eae, drott, kojii) -- Meeting with Docs team to discuss text metrics, line layout needs. -(eae) -- Working on fix for selection painting on high-DPI devices. (eae) -- Meeting with Android team to discuss sharing text layout -implementation or parts thereof. (eae) -Misc: -- Fixed a bug where the scrollWidth and scrollHeight where snapped -differently than clientWidth and clientHeight. (leviw) -- Working with Windows team on re-implementing our high-DPI support to -use our full-page-zoom logic instead of specialized code in the -compositor. Will allow for much better support for non-integer -device scale factors, reduce code complexity and (finally!) allow us -to snap to device pixels instead of CSS pixels. (eae) -- Supporting houdini hackathon last week. (leviw) -- Houdini/custom layout discussions. (shans, eae, leviw, kojii) -- Landed change to disable selection gap painting! (wkorman) -- Mac 10.10 baselines. (leviw) -- Supporting work to enable color emoji on Windows. (eae) -Logistics: -- eae in NYC Wed-Sat.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/thursday-april-2-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/thursday-april-2-2015/index.md deleted file mode 100644 index 79605f73813..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/thursday-april-2-2015/index.md +++ /dev/null @@ -1,327 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: thursday-april-2-2015 -title: 'Thursday, April 2, 2015: Q1/Q2 OKRs' ---- - -Attendees: eae, slightlyoff, benjhayden, bnutter, cbiesinger, -dsinclair, dglazkov, jchaffraixm, kojiim, nduca, skobes -Graded Q1 OKRs: <http://www.chromium.org/blink/layout-team/okrs/2015q1> -Q2 OKRs: <http://www.chromium.org/blink/layout-team/okrs/2015q2> -Q1 Evaluation -------------------- -\* eae presents draft document \* -<eae> Let's go through our Q1 OKRs and see how we did and what we can -learn. -\[ Have telemetry benchmark suite running key_silk_cases monitoring -layout times with less than 1% variation between runs \] -<eae> Variation between runs is about 3% with the new layout_avg -telemetry metric, down from about 10% for existing webkit performance -tests. Scored at 0.6. -<benjhayden> A way to reduce variance further would be to boost the -signal ratio by doing a lot more layout. Not sure if that is the right -thing to focus on. Perhaps we should focus on real world use cases -instead. This might be as good as we can get the tolerance with the -current setup. -<benjhayden> Have started rewriting metrics to expose more -information, this work will carry forward into Q2. -\[ Add 3 real-world pages with lots of layout to key_silk_cases. At -least two of which are mobile oriented \] -<eae> Ben added two new, real world, tests. Score 0.7. -<benjhayden> Perhaps we could add more polymer tests? -<eae> The Polymer Topeka tests is great as it is representative of a -real world app. Adding more like that could be useful but for now -we're pretty good. -\[ Speed up some key_silk_cases tests \] -<eae> We speed up a couple of webkit performance tests by over 10%, -most notably chapter-reflow and line-layout. We didn't manage to speed -up layout in any of the key_silk_cases tests though. Score 0.0. -<jchaffraix> No one owned the task, no one felt responsible and that -might be way. -<benjhayden> layout is already pretty fast -<dsinclair> need to pick specific tests and have actionable goals -<jchaffraix> lets talk about that for Q2 goals -\[ Create a Measure API prototype and write-up of lessons learned \] -<eae> We split this into text and element measure and have write-ups -for both. Score 1.0. -<jchaffraix> We probably scoped this too narrowly and achieved a 1.0. -Should we have been a bit more ambitious? -<cbiesinger> Could you add links to the write-up doc(s)? -<julien> Will do. -Note: Linked from graded Q1 OKR document; -http://www.chromium.org/blink/layout-team/okrs/2015q1 -\[ Support natural layout animations (subpixel layout during animation) \] -<eae> Work was abandoned and depriotitized. Score 0.0. -<jchaffraix> Could you add some background as tho why it was -depriotitized? -<eae> Sure. It didn't seem worthwhile without perf guarantees from -something like layout boundaries. Focused on work to improve line -layout performance instead. -\[ Finish root layer scrolling \] -<eae> Steve made great progress here but didn't quite get to finish it -at all. Score 0.5 -<skobes> Somethings worked, others didn't... Need another quarter to -finish. -\[ Move line layout to LayoutUnit \] -<dsinclair> We're getting close, but haven't made the switch yet. We -still need to look through all the test changes on Windows and see if -there are problems or if we just need to rebaseline. Score 0.7. -<eae> What about the performance problems Stefan found? Do we think it -mostly from the convenience wrappers used to make the transition? -<dsincliar> Not sure, Stefan has been focusing on that. I've been -putting out other fires. -<eae> Will follow up with Stefan (szager). -\[ Triage all clusterfuzz asserts and fix 50% of them \] -<cbiesinger> We didn't do a very good job on scoping, the goal was too -ambitious. Score 0.2 -<cbiesinger> I switched focus to flexbox work half way through the -quarter. Doing both in parallel might have been better. -\[ Have bugs automatically filed for new clusterfuzz asserts \] -<cbiesinger> Auto-filing doesn't make sense without triaging. Score 0.0 -<cbiesinger> All work is done, just needs to flip a switch. -\[ Render tree modifications during layout \] -<dsinclair> Looked at list markers specifically this quarter. Fixed -all of the crashers just ran into one issue where moving a renderer -further down tree causes issues. Score 0.7 -<dsinclair> Think I know the way forward, just need to do it. List -marker work is close to done. -<dsinclair> There are other parts that we haven't started looking at, -like menus with only one item in them being a special case. -<dsinclair> Menus on mac/linux/windows special case when there is only -one item, has a single renderer. Android is different. -<dsinclair> Next up, full screen. Julien was looking at it for awhile. -<eae> Julien, do you want to give a quick update on full screen? -<jchaffraix> I wrongly though someone has fixed a prerequisite bug for -full screen. I spent some time doing tons of testing/rebaselining with -the assumption we could land the change. Realized that we couldn't as -the prerequisite bug wasn't fixed. -<jchaffraix> Blocked on complex problem around re-attach. When -toggling fullscreen you change state of render requiring re-attach -which is problematic. -<jchaffraix> Presto did work to save state when re-attaching to avoid -restarting plugins when re-attaching. Presto re-attaches more than -blink which prompted this. -\[ Speed up complex text by a factor of 2 \] -<eae> New goal added mid-quarter. We managed to speed up complex text -by a minimum of over 2 and up to 40x in some cases. Score 1.0 -<eae> We might have been a bit too conservative here, we'll correct that -for Q2! -Non-OKR tasks ------------------------ -<eae> Let's talk about tasks we spent significant amounts of time on -that was not covered by our OKRs. -From draft doc: -- rendering/ -> layout/ move and renaming -- bidi bugs -- mac text rendering follow up -- security bugs -- updating flexbox to latest version of spec -- import w3c flexbox tests -- css writing mode tests -- win_blink_rel deflaking -<eae> A few of those, like the rendering -> layout rename and the -win_blink_rel work should probably have been added to the OKRs mid -quarter. -<eae> We cannot plan for the unexpected but if we have unforeseen work -that we expect to continue we should consider adding it mid-quarter to -the list. -<jchaffraix> Did we miss anything? -\* silence \* -<eae> I guess the silence means we have agreement, let's move on. -Q2 OKR Planning ------------------------- -\[ O: Gain insight into real world layout performance. \] -\[ KR: Have a report characterizing layout performance for all layout -scenarios. - benjhayden \] -<eae> Could you explain what we mean by layout scenarios? -<benjhayden> That is part of the goal, we know load layout is -different from animation layout and incremental layout. Yet both can -do a lot of the same work. We're still trying to figure out what it -means. -<jchaffraix> Is this layout classes? Load vs animation? -<benjhayden> There are different types of animation layout, think -moves vs gets taller. Most layouts are a mix of many types, there is a -lot to figure out. It is a bit ill-defined at the moment. -<dsinclar> Could you add some words to make that more clear? Wasn't -obvious what it meant, I thought it was layout classes. -<benjhayden> That is part of it, we need to know what is text layout -vs block, load vs incremental etc. Lots of work to define. -<jchaffraix> This needs better wording. -<dsinclar> Should we split it into two KRs? One for moving on page, -other for what we call layout classes in blink? -<jchaffraix> We don't know the granularity. -<eae> Having a report split on a couple of different axis would be -useful, we don't know what the axis are yet though so being more -specific is hard. -<benjhayden> Having a report is a good key result, figuring out how to -present the data is part of the objective. -\[ O: Improve high-level layout design. \] -\[ KR: Have design document for grand node measure refactoring. \] -\[ - jchaffraix \] -\[ KR: List markers not modifying layout tree during layout (in dev). \] -\[ - dsinclair \] -\[ KR: Initial implementation of menu item not modifying layout tree -during layout (in canary). -dsinclair \] -<jchaffraix> For those that haven't been following along, we've -started talking about element measure and display outside/inside. Both -requires changes to how we handle the tree during layout in -significant ways. Wondering if we have to do this work up front to -support other goals or we can make the architecture better as we go -along. -<eae> This unblocks further work down the road, things in pipeline now -and things we want to do in the future. -<jchaffraix> Still early on, we're coming up with a broad proposal. -<dsinclar> I'd like to better understand the use cases for people that -ask about containment vs measure. -<jchaffraix> I'll share a document with use cases. -<jchaffraix> The KR here is to come up with a design document, guided -by the vision that we're still trying to define. -<jchaffraix> It might require that we remove all of the instances -where me modify the tree during layout. -<bnutter> This KR has a lot of owners, each one should have a single -person responsible for keeping track/be in charge. -<eae> Good point, first one listed is in charge. -<jchaffraix> I'm in charge of the design document one. -\[ O: Support standards efforts. \] -\[ KR: Ensure that custom layout spec is compatible with our vision. \] -\[ - jchaffraix, eae \] -\[ KR: Ensure that text measurement spec is compatible with our vision. \] -\[ - eae \] -<eae> These KRs are poorly worded, are about staying involved in the -process and making sure that the spec stays compatible with our goals -and that we can/want to implement them. -<slightlyoff> Who is in charge for the text measurement one? You Emil? -<eae> Yeah, text is on me. -<slightlyoff> Great, then I'm not worried. -<bnutter> This isn't really measurable. -<slightlyoff> Having a public github repo and discussion with other -vendors might be a better goal? -<eae> Makes sense to me. -<slightlyoff> Will be a demonstration. -<dgalzkov> As I understand it this is about us trying to be good -sports, clearing the way for houdini spec work. -<eae> Right, it is a bit hard to define what false on us vs houdini -and the other teams though. -<bnutter> I'm not concerned about who owns it. It doesn't have to be -an OKR, not all work you do needs to be. Writing a spec would be a -good goal but that doesn't seem to be what this is about. -<eae> Some very good points, this might not make sense as a set of -explicit goals. Let's talk about it offline and move along. -\[ O: Improve capabilities of the web platform. -\[ KR: Have an experimental out-of-tree node measure API. - jchaffraix \] -<eae> This might be a little bit too ambitious, might be blocked by -the high-level design re-architecture work. -<jchaffraix> The Q1 goals where scoped too narrow in this regard, I -think it is doable and want us to have stretch goals. -\[ O: Rationalize text rendering. \] -\[ KR: Make complex text as fast as simple text. - eae, szager, kojii \] -\[ KR: Remove the simple text code path. - eae, szager, kojii \] -<eae> Now this is a very ambitious set of goals, complex text is about -seven (7) times slower than complex at the moment. -<eae> Go big or go home, right? -<cbiesinger> Is this about making Arabic as fast as English? -<eae> No, it is about making English text going down the complex path -as fast as the same English text going down the simple path. -<cbiesinger> Ok, sounds more doable. -<eae> Still a ton of work and in practice this will significantly -narrow, if not completely close, the gap between scripts. Performance -will be more about whether ligatures are used or not. English can use -ligatures. -\[ O: Improve code health. \] -\[ KR: Move line layout to LayoutUnit. - szager, dsinclair \] -\[ KR: Finish root layer scrolling. - skobes \] -\[ KR: Fix 30% of clusterfuzz asserts. - cbiesinger \] -\[ KR: Ensure that bugs get automatically filed for clusterfuzz -asserts. - cbiesinger \] -<eae> Dan, do you want to take this one? -<dsinclair> Sure. As for line layout this KR is about finishing the -work we are doing now - carrying the Q1 goal forward. -<skobes> For root layer scrolling it is mostly things we are already -doing. -<jchaffraix> Sounds good. Moving on to clusterfuzz, is this work we -want to be doing? Should we continue with it? -<eae> I'm not sure. -<cbiesinger> Are you talking about stopping the work to fix asserts? -<jchaffraix> Is this work something we as a team thing is really -important? If not we should focus on broader team goals. Perf, -developer productivity and code health. -<cbiesinger> Debug builds are unusable due to assertions, hampers -developer productivity. Many of the asserts might be real bugs that we -don't know about. -<jchaffraix> We might have bigger fish to fry? -<christan> I want to keep doing it and think it is important. Perhaps -not at the highest priority? -<dsinclair> How about we drop fix 30% goal and file bugs for asserts -then fix them ad-hoc? -<christan> Good idea. -<eae> Sounds reasonable, I agree with Christian that it is important -and work we should be doing. Having Christian do all the work himself -and in bulk is not a good use of his time though. -\[ O: Improve web compatibility. -\[ KR: Update flexbox implementation to match latest version of -specification. - cbiesinger \] -<dglazkov> We should think about interoperability as function of -productivity, we need to thing about how much time a developer spends -on something like flexbox interoperability between implementations. -<jchaffraix> I raised the same problem, web compat can or cannot be -out of scope depending on impact on developer productivity. How do we -prioritize web compat vs other things we want to do. -<cbiesinger> I want to continue with flexbox spec changes, think they -are important. Firefox and IE are mostyl compatible now, we're very -different. -<eae> The other vendors are compatible, we are not. This makes life -hard for developers. I think this is really important, especially -since flexbox is one of the flagship layout primitives that we're -trying to push developers towards. -<jchaffraix> Sounds reasonable, just wanted to have the discussion. -<eae> I'm glad you bought it up, that is one of the key reasons we're -having these meetings. -\[ KR: Import w3c test suites. - cbiesinger \] -<jchaffraix> Could you explain this one Christian? -<cbiesinger> Relatively easy to do right now, we have a script that -does it. Need to figure out what to do about failing tests. -<cbiesinger> Perhaps we should just import with failures and add to -TestExpectations? -<eae> Josh might work on this so it could be out of scope for us. We -should sync up with him and his team. -\[ KR: Improve CJK vertical text support - kojii \] -\[ internal discussion, redacted \] -\[ KR: Raise the “Passed” rate of CSS Writing Modes Level 3 - kojii \] -<eae> Do you want to talk about writing mode as well? -<kojii> We do worse than most browsers, see -http://test.csswg.org/harness/results/css-writing-modes-3_dev/grouped/ -- webkit is 82% -<cbiesinger> Is WebKit Blink? -<kojii> We've asked the working group to split it, for now the WebKit -number mostly means Blink. -<jchaffraix> What would this work entail? We need something we could -measure. -<kojii> Firfox is behind a flag, should launch soon. IE we have not tested -much. -<eae> Do we want to support all? What would be a good goal to aim for -here? Specific properties we want to support? Increase the number by a -couple of percentage points? -<jchaffraix> Is unclear. How much are we passing right now? -<jchaffraix> Never mind, found it. We're at 80. -<kojii> We used to be at 60, in Q1 i raised it to 80. -<jchaffraix> Should we aim for 100? -<kojii> Coverage goes down as tests gets add. Is 85% too conservative? -\[ internal discussion, redacted \] -<eae> Makes sense. Let's aim for 85. -\[ KR: Build the plan to support updated Unicode Bidirectional \] -\[ Algorithm - kojii \] -<eae> Updating the UBA is something that we've been punting for years, -the i18n team is really pushing for it. -<kojii> Top priority for BIDI team. -<eae> Will be a lot of work given that we have a custom version for -speed. Whether we update our custom one or improve the performance of -the new one it'll be a lot of work. -<kojii> Need to investigate, goal is to have a plan. -<julien> So the deliverable is to have a plan, not to do the work? -<eae> Yes.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/thursday-june-4-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/thursday-june-4-2015/index.md deleted file mode 100644 index 22b8424bb84..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/thursday-june-4-2015/index.md +++ /dev/null @@ -1,265 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: thursday-june-4-2015 -title: 'Thursday, June 4, 2015: Mid-Q2 OKR Check-in' ---- - -Attendees: eae, cbiesinger, dsinclair, jchaffraix, nduca, skobes, szager - -Q2 OKRs: <https://www.chromium.org/blink/layout-team/okrs/2015q2> (updated - -with latest status, as is overview at team landing page - -<https://www.chromium.org/blink/layout-team/>) - -Q2 Mid-quarter check-in - ------------------------ - -<eae> Good morning/day/afternoon everyone. We're half way through the - -quarter so I figured a check-in was in order to see where we - -stand. - -<eae> Let's go through our list of key-results and see whether we're on - -track to achieve them by the end of the quarter. - -\[ Have a report characterizing layout performance for all layout \] - -\[ scenarios \] - -<eae> Ben isn't here this morning, I'll follow up with him offline. - -\[ Have design document for grand node measure refactoring \] - -<jchaffraix> So the grand node refactoring has been superseded by Moose. - -Moose has some design to it but not a finished design doc. - -<jchaffraix> I don't really know how we want to scope that. Or if we - -should just ignore it. - -<eae> I think it's fair to say that the grand refactoring has been - -superseded by Moose. At the same time the scope has also increased - -dramatically. - -<jchaffraix> We have early design ideas for Moose. Need to split it up - -into concrete proposals and sync up with esprehn and ojan. They took - -over the project when I went of vacation and ran with it, need to - -reclaim it and come up with a plan. - -<eae> The first phase of the moose work, to create an API, is - -relatively well defined, uncontroversial and limited in scope. - -<jchaffraix> The whole idea behind doing the API first is to avoid the - -hard questions about differences of opinion relating to the strategy. - -<eae> Yes. We need to figure that out but this is not the time nor the - -venue. We need to discuss this, with all stakeholders, prior to setting - -the Q3 OKRs. - -<nduca> Everyone should be there when we talk about it. - -<jchaffraix> Moose is more than required, lets continue this discussion - -offline and with all the relevant people. - -\[ List markers not modifying layout tree during layout (in dev). \] - -<dsinclair> Done! - -<eae> Awesome! - -<dsinclair> It's in beta even. - -<dsinclair> Turns out it _just_ missed beta, it's in dev though. - -<eae> That was the goal though, you're golden. - -\[ Initial implementation of menu item not modifying layout tree during \] - -\[ layout (in canary) \] - -<dsinclair> Done, also in dev. - -<eae> You're on fire! What are you going to do the rest of the quarter? - -<dsinclair> Code reviews. Tons of code reviews. - -\[ Have an experimental out-of-tree node measure API. \] - -<jchaffraix> This is from before I left on vacation. We want to push it - -out of the roster, not a priority any more. Gated on refactoring work. - -<jchaffraix> We have a prototype and a design but stopped working on it - -to focus on refactoring work. - -<eae> So we decided to focus on the broader scope refactoring work - -instead of the limited out-of-tree measure implementation? - -<jchaffraix> Yes, there where also concerns about supporting the API in - -the future given the narrow use cases for it. Not necessarily worth the - -complexity. - -<eae> Let's revisit this at the end of the quarter. - -<jchaffraix> Ok. - -\[ Update flexbox implementation to match latest version of \] - -\[ specification \] - -<cbiesinger> Some parts done, some parts to be done. - -<eae> On track? - -<cbiesinger> Should be possible to finish before EoQ. - -<ndcua> Did we make any progress on debugging? - -<cbiesinger> Haven't heard anything about it. - -<nduca> Can you follow up, the new behavior is really hard to debug (for - -web developers). - -<cbiesinger> I'm not quite sure how to shove it into the inspector. - -<nduca> Not super important but a nice side narrative and it might be a - -fun project. Would be be great for users. - -<cbiesinger> Agreed, not sure where to start though. - -<nduca> Only if you want to. Entirely up to you. Work with dev tools - -team and nudge them in right direction. No need to do any UI work. - -<cbiesinger> I'll put it on my todo list to reach out to the dev-tools - -team and expose the information. - -\[ Improve CJK vertical text support \] - -<eae> kojii isn't here which is understandable given that it's 2am in - -Tokyo at the moment. I'll follow up with him this afternoon. - -\[ Make complex text as fast as simple text \] - -<eae> So this is on me. I have a plan and have started working on it. - -Still think I'll be able to get the complex path to be at least as fast - -as the simple one by the end of the quarter, will by close though. - -Involves changing how we cache things are reducing repetitive and - -redundant work. - -\[ Remove the simple text code path \] - -<eae> This is obviously gated on the previous goal of getting complex - -text to be as fast as simple text. We're quickly running out of time - -this quarter so this is at risk of slipping. We should be able to at - -least have a flag to disable it but removing it entirely seems a bit - -optimistic at this point. - -\[ Build the plan to support updated Unicode Bidirectional Algorithm \] - -<eae> Also on kojii, will fallow up online. - -\[ Raise the “Passed” rate of CSS Writing Modes Level 3 to 85% \] - -\[ including new tests. \] - -<eae> Also on kojii, will fallow up online. - -\[ Move line layout to LayoutUnit \] - -<szager> Done! - -<eae> Want to expand on that? - -<sazager> No. It's in dev and so far it looks good. - -<eae> Congratulations and well done! - -\[ Finish root layer scrolling \] - -<skobes> Making good progress, with sazager helping out it should be - -possible to get pretty close to finish it this month. - -<eae> Any new unforeseen problems? It's grown in scope quite a bit since - -it started. - -<skobes> Nothing too major, just a lot of work. - -\[ Ensure that bugs get automatically filed for clusterfuzz asserts \] - -<cbiesinger> Done. - -<eae> Awesome. - -Wrapping up - ------------------------ - -<eae> Looks like we're on track or even ahead of the curve for the - -majority of our objectives. Well done everyone! Perhaps we need to have - -a bit more ambitious goals for Q3? - -<eae> Speaking of which, it would be great if everyone could start - -thinking about what they want to do next and what you want to work on - -for the next quarter or two. - -<eae> We have a big list of our backlog and potential projects at - -<https://www.chromium.org/blink/layout-team/potential-projects>, please - -add projects and tasks you think are missing and see what you think we - -should focus on next. - -<eae> We'll have a Q3 planning discussion in a few weeks. - -<eae> Any questions about our OKRs or concerns that we need to talk - -about? - -\* silence \* - -<eae> Thanks everyone!
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-february-16-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-february-16-2016/index.md deleted file mode 100644 index a4b662e9be4..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-february-16-2016/index.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: tuesday-february-16-2016 -title: Tuesday, February 16, 2016 ---- - -Updates since last meeting (on Monday, February 8th): -Scrolling (skobes, szager) -- Working on scroll anchoring, investigating a crash where it looks -we're holding stale pointers. (skobes) -\[[crbug.com/558575](http://crbug.com/558575)\] -- Smooth scrolling is under control one outstanding bug where -we're not handling the interaction between man and cc correctly. (skobes) -- Started looking at a scrollbar-renders-weirdly -bug, most likely it's the compositor pointing to a stale Scrollbar, -no fix yet. (szager) \[[crbug.com/553860](http://crbug.com/553860)\] -CSS Flexbox (cbiesinger) -- Have quite a few release blockers. All the same issue, related to -autoflow auto. Finally figured it all out. Stefan made a change to delay -overflow calculation to fix a scrollbar bug awhile ago. It turns out the -fix wasn't quite correct in regards to flexbox Working on a better -implementation of. Going to make a patch to do that and then to clear -the flexbox main cache which should be the right approach. -Specifically, flexbox has code, actually in LayoutBlock used for -flexbox, that handles overfow auto is after layout, called something -like updateOverflorAfterLayout. That then checks if we overflow and if -auto then adds scrollbars and triggers another layout. But if flexbox -we don't do it for every flexbox change as that wouldn't work for -nested flexboxes, we delay until after last flex. The new fix is to -do relayout without updating the cache for the flebox. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- No update since last week - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No update since last week - -CSS Houdini (ikilpatrick) -- Last week was working on Worklet stuff, working with AudioWG to see -how it interacts with audioWorklet and their needs. -- This week will start on PaintRenderingContext2d, which is the subset -of canvas for custom paint. -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Removed remaining uses of deprecated InlineBox::layoutObject() -accessor and made it private. (dgrogan) -- Had to add many methods to the API. (dgrogan) :( -- Started removing uses of shim-like LayoutObject\* LineLayoutItem:: -operator(). (dgrogan) -- Started working on next part of api work, have a little like starter -patch out, just need to hit CQ button. (leviw) -- Going to work on a poof of concept work to see if we can build -LayoutNG and have it co-exitst with and interact with our current -layout code. Will do work on branch but in public. (leviw) -- Have a patch out for for LineLayoutTextSVG class. Dave identified as -necessary, working through Levi's feedback. (pilgrim) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- Style containment landed this morning, yay! -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Trying to get the spec solid so we can get feedback from other -browser vendors. Getting other browsers on board is going to be the -long pole in shipping. (szager) -- Probably not going to make M50. Spec work needs to occur. Not getting -reviews as quickly as I'd like. (szager) -Text (eae, drott, kojii) -- Fixed orthogonal writing mode issue, working on following fixes. -(kojii) -- Support accept-language in font fallback for Windows and Android. -(kojii) -- Investigating snap-height property. (kojii) -- Investigated Chrome's coverage of font-variant-\* sub properties. Only -font-variant-ligatures supported, the rest rather looks like CSS 2.1. -Filed bugs about font-variant being in a state of a very old version -of the spec. (drott) -- Experimented and started a true small-caps implementation (non- -synthesized), checked for AAT small-caps feature in fonts on Mac. -(drott) -- Sent Intend to Implement for font-variant-caps. (drott) -- Review of Koji's multi-locale font-fallback Android CL. (drott) -- Working on an issue involving the handling of combining emoji (two or -more emoji joined together with a zero with joiner) where the metrics -cache has incorrect measurements causing extra line wrapping. (eae) -- Various layout release blockers. (eae) -HTML Tables (dgrogan) -- Fixed regression around width:50% handling for tables. -\[[crbug.com/244182](http://crbug.com/244182)\] -- Fix incorrect handling of percentage heights inside table cells, -cased a small issue for hangouts but got them to fix it on their end. -\[[crbug.com/353580](http://crbug.com/353580)\] -- Fixed a renderer crash. \[[crbug.com/570139](http://crbug.com/570139)\] -Misc -- Next week or two will take stab at flipped blocks approach. -News at 11! (wkorman) -- Correctness fix for paint performance with regards to VisibleRect. We -added VisibleRect which is used for paint performance, not yet live. -VisibleRect is essentially the CullRect but in the space of the -backing graphics layer. Needed for CC interaction. It didn't correctly -handle subpixel accumulation before. (wkorman) -- Tons of release blockers (leviw), will try to rebalance. (eae) -- Beginning to look at forced layout, (potentially reducing time spent -in forced layout / number of forced layouts). (cbiesinger)_ -Logistics -- drott going to Tokyo on Thursday. drott/kojii/behdad plus people from -Mozilla meeting for a text workshop.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-june-16-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-june-16-2015/index.md deleted file mode 100644 index b16aa81888d..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-june-16-2015/index.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: tuesday-june-16-2015 -title: Tuesday, June 16, 2015 ---- - -We had Sergio Villar (svillar@igalia.com) from Igalia join us this week. - -Sergio is a long term contributor working primarily on CSS Grid Layout. - -Updates since last meeting (on Monday, June 8th): - -Scrolling (skobes, szager) \[[crbug.com/417782](http://crbug.com/417782)\] - -- Fixed hit testing by making the LayoutView absolute-positioned. - -(skobes) \[crbug.com/495856\] - -- working on HitTestRequest::IgnoreClipping -\[[crbug.com/499053](http://crbug.com/499053)\] - -and the zoomed-out viewport issue. - -CSS Flexbox (cbiesinger) \[[crbug.com/426898](http://crbug.com/426898)\] - -- Continuing to update to match spec, progress according to plan. - -CSS Grid Layout (svillar) \[[crbug.com/79180](http://crbug.com/79180)\] - -- Fixed a regression caused by the recent migration from parenthesis - -to brackets. - -- Working on adding a new step to the track sizing algorithm. - -- We need to find someone to help with grid layout reviews to unblock - -further work. - -Region-based multi-column support (mstensho) -\[[crbug.com/334335](http://crbug.com/334335)\] - -- Fixing multicol fuzzers. Looks like the fuzzer storm has finally - -calmed down this week. - -Isolate core/fetch (japhet) \[[crbug.com/458222](http://crbug.com/458222)\] - -- Improved API between core/fetch and the rest of core. - -- A bunch of small crash/use-after-free fixes. - -Text (eae, kojii) - -- Fixed a long-standing issue in positioned objects layout ordering. - -(kojii) - -- Unicode variation selectors support in progress, waiting for reviews. - -(kojii) - -- Investigating orthogonal writing modes issues. (kojii) - -- Investigating abspos issues in vertical flow. (kojii) - -- Investigating/triaging failures of imported CSS Writing Modes tests, - -also working with external contributors to fix in upstream. (kojii) - -- Working on CSS Writing Modes spec issues, primarily to simplify rarely - -used features. (kojii) - -- Working on shaping word-by-word, initial prototype shows very - -promising results. (eae) - -Misc - -- Added option to dump line box tree when dumping layout tree. (szager) - -Layout Bugs: - -We currently have 1592 open bugs for the Cr-Layout label. - -- Untriaged: 475 - -- Priority 0: 0 - -- Priority 1: 135 - -- Priority 2: 958 - -- Priority 3: 19 - -We need to get the number of bugs down so from now on each weekly update - -will include the number of bugs for each category and the delta from the - -week before. - -Logistics: - -- skobes OOO 6/17-6/22 - -- drott getting up to speed. - -- szager OOO next week. - -- drott OOO Thu-Fri this week. - -- eae gardener Wed-Thu next week.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-march-15-2016/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-march-15-2016/index.md deleted file mode 100644 index a04ae37d593..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-march-15-2016/index.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: tuesday-march-15-2016 -title: Tuesday, March 15, 2016 ---- - -Updates since last meeting (on Monday, March 7): -Scrolling (skobes) -- Fixed a smooth scrolling RTL bug and a smooth scroll text selection -bug. -- Fixed how we reset state between layout tests. -- Reached out to conops and came up with a plan to monitor and address -user feedback and concerns. -- This week, working through a few minor smooth scrolling bugs. -- Plan to resume work on scroll anchoring, getting it to work correctly -with different position attributes. -CSS Flexbox (cbiesinger) -- Been working on flexbox, big surprise, turns out that when I through I -had finally fixed all the scrolling issues I had not, in fact, fixed -all the scrolling issues. \*collective expression of sadness\* -There are a number of new regressions and release blockers that I'm -working to burn down. The bug that keeps on giving. -- Almost done with percentage children, patch out for review. -CSS Grid Layout (svillar, jfernandez, rego, javif) -\[[crbug.com/79180](http://crbug.com/79180)\] -- See mail to blink-dev for an update on Grid - -CSS Multi-column (mstensho) \[[crbug.com/334335](http://crbug.com/334335)\] -- No update since last week - -CSS Houdini -- Devtools for main thread worklets. (ikilpatrick) -- Landed initial paint() function, (this does nothing, just parsing -code). (ikilpatrick) -- Plan to finally send out the patch for PaintRenderingContext2D for -review. (ikilpatrick) -- Might get to the Paint API class/instance management CL. (ikilpatrick) -- Started making progress on resize observer. (atotic) -Add API for layout (leviw, pilgrim, dgrogan) -\[[crbug.com/495288](http://crbug.com/495288)\] -- Layout API skeleton is done, looks like a bigger project than we -thought. LayoutView alone has over 100 references that need -converting. Have started migrating first HTML element class to serve -as a template for future work. (pilgrim) -LayoutNG \[[crbug.com/591099](http://crbug.com/591099)\] -- We're doing a prototype for layoutNG inside of out current layout -engine. Part of the motivation here is to address big architectural -issues in the layout engine itself and part of it is to support the -houdini effort to implement custom layout. Shoehorning custom layout -into out existing legacy layout would be very hard and require a lot -of hacks and isn't really something we want to do. Especially since we -already know that our layout architecture needs quite a bit of work. -Essentially we're trying a new approach to achieve many of the goals -identified during the big layout refactoring discussion (a.k.a. Moose) -last year. -What we're trying to see is if embedding layoutNG within the legacy -system is practical, determining whether we can support both in -parallel and use the new system for certain sub-trees. -Made more progress than expected, have a prototype that builds and -supports very basic block layout and paints. Will keep working for the -rest of the week, should have data to share by the end of the week. -Work is on a [chromium.org](http://chromium.org/) experimental branch, see bug -for URI. -(leviw, dgrogan, ikilpatrick, shanestephens) -CSS Containment (leviw) \[[crbug.com/312978](http://crbug.com/312978)\] -- No update since last week - -Intersection Observer (szager, mpb) -\[[crbug.com/540528](http://crbug.com/540528)\] -- Intersection observer work is dragging on for much longer than -originally anticipated. Got a bunch of feedback on the intent to ship -that will be incorporated into the feature before shipping. (szager) -- Wrap up intersection observer work leading up to the branch point. -(szager) -Text (eae, drott, kojii) -- Landed two emoji fixes for line breaking and for skin tone modifiers, -these are now enabled and work fine on Android. Works with line -breaking and shrink-wrapping too. One remaining issue flagged by the -android team is with backspacing in content-editable where we delete -character by character rather than glyph by glyph. (drott) -- Helped out with font regression, tracked down the issue and worked -with windows team and testers to resolve it. (drott) -- Resuming work to fixing shaping across unicode ranges, should have -a patch ready by EoD. (drott) -- Resume small-caps work. (drott) -- Looking into line breaking performance, working on an implementation -that would take advantage of per glyph measurements to find the ideal -position and then scan backwards for the first preceding breaking -opportunity. Should performance a lot better than our current -implementation which always scans from the front of the string and -considers each break opportunity up until the end of the line. -Handling of collapsible white-space might be a problem, it's currently -implemented as a part of both the measure, line break and paint steps -rather than as a separate stage. (eae) -HTML Tables (dgrogan) -- Landed first patch, Table cell background painting. (atotic) -Misc -- Asyncathon last week, bringing together all the rendering leads to -discuss our strategy around async for the next year. See separate -update from Dru for details. (eae, ikilpatrick) -- Fixed rebaseline bot and re-worked it to run as a separate service as -opposed to as a client app on a desktop machine. (wkorman, szager) -- Helped the pain team diagnose a couple of top crashers. All have now -been resolved. More lifecycles issues. (leviw) -- Talked to julien and told him about my work on collapsed borders, he -liked what I did and agreed to review it. (atotic)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-may-26-2015/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-may-26-2015/index.md deleted file mode 100644 index 4170ac3a1f9..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/tuesday-may-26-2015/index.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: tuesday-may-26-2015 -title: Tuesday, May 26, 2015 ---- - -Highlights - -- New multicol implementation shipped! - -- Line layout in layout units landing this week! - -Updates since last meeting (on Monday, May 18th): - -Performance Tracking (benjhayden) - -- Continuing work on trace viewer. - -Scrolling (skobes) \[crbug.com/417782\] - -- Root layer scrolling broke <body> stretching to viewport in quirks - -mode; fix is waiting on code review. - -- Page scale factor is a bigger concern: page scaling changes - -content size relative to scroll bounds, which doesn't work with root - -layer scrolling as currently implemented. Need to teach LayoutView / - -DPLScrollableArea how to apply the page scale factor, which could get - -messy. - -Line Boxes (szager) \[crbug.com/321237\] - -- Ready to land, will require a ton of rebaselines. - -Flexbox (cbiesinger) \[crbug.com/426898\] - -- Discussions around absolut positioning within flexbox. - -- Updated handling of min-width/min-height. - -List marker refactoring (dsinclair) \[crbug.com/370461\] - -- List marker patches in M44 branch. Yay! - -Menu list refactoring (dsinclair) \[crbug.com/370462\] - -- Menu list changes landed, with hack to use empty text node instead - -of BR for line breaks to ensure proper alignment. - -Fullscreen (dsinclair) \[crbug.com/370459\] - -- Taking over work to update fullscreen implementation to not modify - -layout tree during layout. Building on previous work by Julien and - -James among others. - -Misc Warden (dsinclair, pilgrim) - -- Contining work to slim-dopwn LayoutObject. (pilgrim) - -- Plan to start helping with WTF to Base conversion this week. (pilgrim) - -Region-based multi-column support (mstensho) \[crbug.com/334335\] - -- New multicol implementation shipped! - -Text - -- Working on justification crash issue. (kojii) - -- Investigating orthogonal writing modes issues. (kojii) - -- Unicode variation selectors support. (kojii) - -- Shaping AAT fonts broken on Mac for certain scripts. (eae) - -- Continuing work on complex text performance. (eae) - -Importing CSS Test Suites (kojii) - -- Investigating importing CSS Writing Modes test suites - -Removing DeprecatedPaintLayer (chadarmstrong) - -- Intern Chad Armstrong started, is going to be working on killing - -DeprecatedPaintLayer. - -- Design doc: -https://docs.google.com/document/d/1YApHVA0hJDWeFGxHPpJ6J5JM5Wcz2h3s24KPSFp8VMg/edit?usp=sharing
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/meeting-notes/wednesday-february-18/index.md b/chromium/docs/website/site/teams/layout-team/meeting-notes/wednesday-february-18/index.md deleted file mode 100644 index 91fbce880e6..00000000000 --- a/chromium/docs/website/site/teams/layout-team/meeting-notes/wednesday-february-18/index.md +++ /dev/null @@ -1,246 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/meeting-notes - - Layout Team Meeting Notes -page_name: wednesday-february-18 -title: Wednesday, February 18, 2015 ---- - -Attendees: benjhayden, cbiesinger, dsinclair, eae, jchaffraix, nduca, szager, -skobes, slightlyoff, hartmanng - -Status updates: - -Performance Tracking (benjhayden) - -- Finished profiling most of the key silk test cases on android, added - -more graphs and information to the profiling doc. - -- Next up, classifying types of layout. - -Scrolling (skobes) \[crbug.com/417782\] - -- Smooth scrolling enabledd for RenderLayerScrollableArea. - -- Fixed position elements. - -win_blink flakiness (dsinclair) - -- win_blink_rel now among the better bots in terms of flakiness. - -- Slowly re-enabling tests, monitoring flakiness. - -Rename Rendering -> Layout \[crbug.com/450612\] (dsinclair) - -- Trying to rename RendereBlock to LayoutBlock. Involves 30k files which - -rietveld does not like. Uploading for reviews cases the upload command - -to crash. - -List markers (dsinclair) - -- Trying to figure out how to deal with an ancestor being moved. - -Measure API (jchaffraix) - -- Working on a number of prototypes for measure together with Ian - -Kilpatrick. - -- github repo for prototypes. To allow layout callbacks a script - -execution context might be needed. Runs js in snadbox since we cannot - -modify the DOM. Would not have even read-only access to the DOM. - -Needs to be able to access render tree in a safe way. - -- Defining an API for the render tree, houdini style. - -- slightlyoff would prefer to not add a new execution context that is - -not workers. jchaffraix and slightlyoff to talk offline. - -Line Boxes (hartmanng, szager) \[crbug.com/321237\] - -- No real progress last week. Blocked on higher priority work to fix - -high profile regressions. - -Flexbox (cbiesinger) \[crbug.com/426898\] - -- Working on updating flexbox implementation to match latest spec - -revision. - -Text (kojii, eae) - -- Made RenderCombinedText less obstructive. 4 if-RenderCombinedText - -removed, 1 moved to less frequent path. (kojii) - -- Worked with dominik.rottsches to make vertical flow performance - -test. (kojii) - -- Started analyzing complex path performance. It looks like - -characteristics varies by scripts and values of properties. I'll look - -into CJK vertical flow first. (kojii) - -- Fixed two text regressions on Mac causing incorrect rendering and/or a - -render crash (due to an ASSERT). Required a Harfbuzz change and roll. - -(eae, behdad) - -- Added support for emoticons and emoji on Windows. (eae) - -Line layout (szager) - -- Fixed bug where shrink-wrapping of some content failed on Facebook, - -caused by imprecision in LayoutUnit to floating point conversions. - -Writing a test for this was tricky as layout tests run without - -subpixel text on most platforms. (szager) - -Going over the list of OKRs and discussing each one: - -\[ Have telemetry benchmark suite running key_silk_cases monitoring layout times -with less than 1% variation between runs. \] - -\[ Add 3 real-world pages with lots of layout to key_silk_cases. At least two of -which are mobile oriented. \] - -<benjhayden> A couple of cases with large variance, most have low -variance. - -<benjhayden> Layout measurement should fix this in most cases. Some tests -have a bi-modal behavior, triggering an extra layout in some cases. - -<nduca> We want a link on the layout team site to a set of graphs by the -end of the quarter. - -<eae> So we're looking pretty good, do we think we can get there by the -end of the quarter? - -<benjhayden> Yes. - -\* on track \* - -\[ Speed up some key_silk_cases tests. \] - -<eae> We've made a number of small improvements to complex text -performance and have ongoing work that should result in a 10% improvement. - -<eae> Any other ongoing performance work? - -\* at risk \* - -\[ Create a Measure API prototype and write-up of lessons learned. \] - -<jchaffraix> On second or third prototype, have a better understanding -since the Sydney convergence. - -<jchaffraix> Github repo with prototype, working on write-up. - -\* on track \* - -\[ Support natural layout animations (subpixel layout during animation) \] - -<eae> No real progress, have rough proof of concept prototype but nothing -concrete. - -<eae> Might miss. - -<nduca> Should be explicit if it wasn't a priority and what we did -instead. - -\* at risk \* - -\[ Finish root layer scrolling. \] - -<skobes> Making progress, fixing issues as discovered. - -<skobes> Handful of hard problems, some risk of slipping into Q2. - -\* on track \* - -\[ Move line layout to LayoutUnit. \] - -<hartmanng> Distracted by P1 bugs, have made some progress. - -<hartmanng> Complications with full-page zoom implementation. - -<hartmanng> Should be possible if we get time to work on it. - -<szager> Agreed. - -\* on track \* - -\[ Triage all clusterfuzz asserts and fix 50% of them. \[cbiesinger\] - -<cbiesinger> Starting to realize that 50% might have been a bit -optimistic. Not all are reproducible. - -<cbiesinger> Without minimized test cases it is really hard, given up on a -subset of them (without test cases). - -<eae> What would a realistic goal be for Q1? - -<cbiesinger> Triaging all reproducible ones and fixing the ones with -minimal test cases would be feasible. - -\* at risk \* - -\[ Have bugs automatically filed for new clusterfuzz asserts. \] - -<cbiesinger> Need to work with someone on the clusterfuzz team, should be -easy. - -\* on-track \* - -\[ Render tree modifications during layout. \] - -<dsinclair> first-letter is stabilized, list-marker is a lot closer. - -<dsinclair> One tricky outstanding issue regarding descendants -(list-marker). - -<jchaffraix> Full screen is a road block. Re-attach destroys renderer, -restarts plugins. Currently we do no reattach. We need to add a hoisting -mechanist to make it work. Prototype patch among those lines but it does break -plugins. Needs more work and is complicated. - -<jchaffraix> Have not had time to dig into it, need to fix path. - -<dsinclair> single-item-menu won't be done this quarter. - -<dsinclair> On track according to plan, decent amount of risk. - -\* on track \* - -High level discussion: - -<dsinclair> Renaming rendering to layout has been sucking up a lot of time -for everyone. - -<eae> As has dealing with regressions and blocking bugs. - -<nduca> Are we spending more or less time on work not captured in the OKRs -than expected? - -<eae> Was expecting about a 50%/50% split between OKR work and -high-priority bug fixes. So for this quarter we've spent a bit more time on -bugs/regressions than expected. - -<nduca> For Q2 OKRs should capture that work.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/okrs/2015q1/index.md b/chromium/docs/website/site/teams/layout-team/okrs/2015q1/index.md deleted file mode 100644 index 13a9f986311..00000000000 --- a/chromium/docs/website/site/teams/layout-team/okrs/2015q1/index.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/okrs - - Objectives and Key Results -page_name: 2015q1 -title: 2015 Q1 ---- - -List of objectives and key results for the first quarter of 2015. - -## Overview - -* Key Result Owner(s) Score -* [Have telemetry benchmark suite running key_silk_cases monitoring - layout times with less than 1% variation between runs.](#kr0) - \[benjhayden\] 0.6 -* [Add 3 real-world pages with lots of layout to key_silk_cases. At - least two of which are mobile oriented.](#kr1) \[benjhayden\] 0.7 -* [Speed up some key_silk_cases tests.](#kr2) \[*everyone*\] 0.0 -* [Create a Measure API prototype and write-up of lessons - learned.](#kr3) \[jchaffraix, eae\] 1.0 -* [Support natural layout animations (subpixel layout during - animation).](#kr4) \[eae\] 0.0 -* [Finish root layer scrolling.](#kr5) \[skobes\] 0.5 -* [Move line layout to LayoutUnit.](#kr6) \[hartmanng, szager\] 0.7 -* [Triage all clusterfuzz asserts and fix 50% of them.](#kr7) - \[cbiesinger\] 0.2 -* [Have bugs automatically filed for new clusterfuzz asserts.](#kr8) - \[cbiesinger\] 0.0 -* [Render tree modifications during layout.](#kr9) \[dsinclair\] 0.7 -* [Speed up complex text by a factor of 2.](#kr10) \[kojii, eae\] 1.0 - -## Details - -### Have telemetry benchmark suite running key_silk_cases monitoring layout times with less than 1% variation between runs - -Owner(s):benjhayden -Score:0.6 - -The variation between runs is about 3% overall for tests running with the new -layout_avg telemetry metric. Down from about 10% for existing webkit performance -tests. - -The variation between runs is about 3% overall, though avg and variation vary -widely between pages. - -It looks like there's a couple hundred ms variation in the average of all pages' -layout_avg, though I'm not sure what the take-home number should be. The average -over all the pages' layout_avg is about 5.4ms after I added Masonry, and the -stddev in that line looks to be about 200ms, which is about 3-4% variation. -Masonry's layout_avg is usually around 70ms, and the stddev in its layout_avg -between runs is about 1-2ms, which is about 3% variation. Several pages have a -layout_avg that is consistently below 1ms, so normal variation can be 100% or -more. - -One way to reduce variation would be to rewrite the pages to perform -significantly more layout, i.e. boost the signal above the noise. - -Perhaps this OKR should have been about making sure that there aren't any -easily-fixable sources of noise in any page's layout_avg, e.g. non-deterministic -load order. I fixed one issue of that nature. The noise in most of the rest of -the pages looks like expected white noise, with a few pages exhibiting rare -spikes that may warrant further investigation, though nothing as troublesome as -that non-deterministic load order. - -I'm rewriting the LayoutMetric, so these numbers will change and expose more -detailed information. - -### Add 3 real-world pages with lots of layout to key_silk_cases. At least two of which are mobile oriented - -Owner(s):benjhayden -Score:0.7 - -Added two new tests, Polymer Topeka and Masonry. - -### Speed up some key_silk_cases tests - -Owner(s):everyone -Score:0.0 - -We've speed up quite a few of the blink layout perf tests but seemingly none of -the silk cases. - -It turns out that all the key_silk_cases tests were already pretty fast when it -comes to layout. - -* [chapter-reflow](https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nexus7v2%2Cchromium-rel-mac9%2Cchromium-rel-win7-gpu-nvidia%2Clinux-release&tests=blink_perf.layout%2Fchapter-reflow&checked=chapter-reflow%2Cchapter-reflow%2Cref%2Cchapter-reflow%2Cref%2Cchapter-reflow%2Cref) - tests speed up by 5-12% depending on platform. -* [line-layout](https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nexus7v2%2Cchromium-rel-mac9%2Cchromium-rel-win7-gpu-nvidia%2Clinux-release&tests=blink_perf.layout%2Fline-layout&checked=line-layout%2Cline-layout%2Cref%2Cline-layout%2Cref%2Cline-layout%2Cref&start_rev=318673&end_rev=322609) - tests 4-15% depending on platform. - -### Create a Measure API prototype and write-up of lessons learned - -Owner(s):jchaffraix, eae -Score:1.0 - -Split Measure into Element, Text and Custom Layout measure. - -* jchaffraix has several prototypes and - [write-up](https://docs.google.com/a/chromium.org/document/d/1hGuLzcY8uFcP4fQw2HiwnpnI6SmygqErvYQMxkObONs/edit) - for Element measure, with key conclusions about the API and what - people expect. -* eae has a proposal and some write-up for text. -* jchaffraix was involved in Custom Layout but ikilpatrick is the main - driver. - -### Support natural layout animations (subpixel layout during animation) - -Owner(s):eae -Score:0.0 - -No real progress, was deprioritized in favor of performance and code health -work. Questionable whether it makes sense without some sort of layout/style -containment as we cannot give any performance guarantees without it. - -### Finish root layer scrolling - -Owner(s):skobes -Score:0.5 - -Main-thread, impl-thread, and script-driven frame-level scrolls now work through -LayerScrollableArea codepath with --root-layer-scrolls. Iframes, position: -fixed, and scroll animations work. Need to expand test coverage and look at -potential interactions with other features (pinch viewport, fractional scroll -offsets, top controls, overhang, slimming paint, scroll customization etc). - -### Move line layout to LayoutUnit - -Owner(s):hartmanng, szager -Score:0.7 - -Great progress but not quite there yet. Need to solve the performance issue. -Still need to go through all tests on Windows to determine if any of the changes -are due to regressions or if we just need to rebaseline the tests. Mac and Linux -both close. - -### Triage all clusterfuzz asserts and fix 50% of them - -Owner(s):cbiesinger -Score:0.2 - -Clusterfuzz now does produce assertion errors. \[restricted link\] If that link -does not show results, click "Toggle experimental testcases". - -Triaged most asserts, but so far only on paper. Not fixed because focused more -on Flexbox. Need to continue in Q2 with bug filing and fixing. - -### Have bugs automatically filed for new clusterfuzz asserts - -Owner(s):cbiesinger -Score:0.0 - -Not done because not done triaging. However, when it's time to do this it's just -a matter of asking the clusterfuzz team to do it. All code and logic is already -in place. - -### Render tree modifications during layout - -Owner(s):dsinclair -Score:0.7 - -Landed first-letter but the list markers change is stuck on finishing the patch, -especially editing. Dan is pulled in other directions (LayoutObject renaming, -unflaking win bot etc) - -### Speed up complex text by a factor of 2 - -Owner(s):kojii, eae -Score:1.0 - -Speed up by over 2x at a minimum and up to 40x in some cases. - -* [ArabicLineLayout](https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nexus7v2%2Cchromium-rel-mac9%2Cchromium-rel-win7-gpu-nvidia%2Clinux-release&tests=blink_perf.layout%2FArabicLineLayout&checked=ArabicLineLayout%2CArabicLineLayout%2Cref%2CArabicLineLayout%2Cref&start_rev=318673&end_rev=322609) - 2-2.5x depending on platform. -* [latin-complex-text](https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nexus7v2%2Cchromium-rel-mac9%2Cchromium-rel-win7-gpu-nvidia%2Clinux-release&tests=blink_perf.layout%2Flatin-complex-text&checked=latin-complex-text%2Cref%2Clatin-complex-text%2Clatin-complex-text%2Cref%2Clatin-complex-text%2Cref&start_rev=318673&end_rev=322609) - 8-40x depending on platform. -* [vertical-japanese-kokoro-insert](https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nexus7v2%2Cchromium-rel-mac9%2Cchromium-rel-win7-gpu-nvidia%2Clinux-release&tests=blink_perf.layout%2Fvertical-japanese-kokoro-insert&checked=vertical-japanese-kokoro-insert%2Cvertical-japanese-kokoro-insert%2Cref%2Cvertical-japanese-kokoro-insert%2Cref%2Cvertical-japanese-kokoro-insert%2Cref&start_rev=318673&end_rev=322609) - 2-5x depending on platform.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/okrs/2015q2/index.md b/chromium/docs/website/site/teams/layout-team/okrs/2015q2/index.md deleted file mode 100644 index 5a89cfcd65b..00000000000 --- a/chromium/docs/website/site/teams/layout-team/okrs/2015q2/index.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/okrs - - Objectives and Key Results -page_name: 2015q2 -title: 2015 Q2 ---- - -List of objectives and key results for the second quarter of 2015. - -## Overview - -* Objective / Key Result Owner(s) Status -* Gain insight into real world layout performance - * [Have a report characterizing layout performance for all layout - scenarios.](#o0r0) \[benjhayden\] 0.0 -* Improve high-level layout design - * [Have design document for grand node measure - refactoring.](#o1r0) \[jchaffraix\] 0.3 - * [List markers not modifying layout tree during layout (in - dev).](#o1r1) \[dsinclair\] 1.0 - * [Initial implementation of menu item not modifying layout tree - during layout (in canary).](#o1r2) \[dsinclair\] 1.0 -* Improve capabilities of the web platform - * [Have an experimental out-of-tree node measure API.](#o2r0) - \[jchaffraix\] 0.0 - * [Update flexbox implementation to match latest version of - specification.](#o2r1) \[cbiesinger\] 0.8 - * [Improve CJK vertical text support \[redacted, internal - metric\].](#o2r2) \[kojii\] 0.9 -* Rationalize text rendering - * [Make complex text as fast as simple text.](#o3r0) \[eae\] 1.0 - * [Remove the simple text code path.](#o3r1) \[eae\] 0.0 - * [Build the plan to support updated Unicode Bidirectional - Algorithm.](#o3r2) \[kojii\] 0.2 - * [Raise the “Passed” rate of CSS Writing Modes Level 3 to 85% - including new tests.](#o3r3) \[kojii\] 1.0 -* Improve code health - * [Move line layout to LayoutUnit.](#o4r0) \[szager\] 1.0 - * [Finish root layer scrolling.](#o4r1) \[skobes\] 0.7 - * [Ensure that bugs get automatically filed for clusterfuzz - asserts.](#o4r2) \[cbiesinger\] 1.0 - -## Details - -### Have a report characterizing layout performance for all layout scenarios. - -Owner(s):benjhayden -Status:0.0 - -Abandoned to focus on telemetry. Ben moved to telemetry team to ensure that the -larger blink team has access to the performance data we need to ensure that RAIL -is a success. - -### Have design document for grand node measure refactoring. - -Owner(s):jchaffraix (dsinclair, cbiesinger, skobes, eae) -Status:0.3 - -Superseded by larger layout refactoring proposal (“moose”). Part of the -refactoring work could still be relevant/applicable in isolation and has been -broken out into specific design documents; unrooted layout, removing deprecated -paint layer. - -### List markers not modifying layout tree during layout (in dev). - -Owner(s):dsinclair -Status:1.0 - -Done - -### Initial implementation of menu item not modifying layout tree during layout (in canary). - -Owner(s):dsinclair -Status:1.0 - -Done. - -### Have an experimental out-of-tree node measure API. - -Owner(s):jchaffraix -Status:0.0 - -Abandoned due to the high implementation complexity, high maintenance costs and -relatively low level of enthusiasms from prospective clients. Does not -necessarily make sense in isolation and should be considered as a part of a -bigger layout refactoring or work to support custom layout. Most prospective use -cases can be satisfied with a text metrics API. - -### Update flexbox implementation to match latest version of specification. - -Owner(s):cbiesinger -Status:0.8 - -Mostly done, will drag into Q3. Initial estimate was a little bit too -optimistic. - -### Improve CJK vertical text support \[redacted, internal metric\]. - -Owner(s):kojii -Status:0.9 - -We unblocked all existing blockers. The metric is stalled for other problems, -and one topic is still under discussions, but Blink is no longer the blocker at -this point and the failure to meet the goal is outside the control of the blink -team. - -### Make complex text as fast as simple text. - -Owner(s):eae (szager, kojii, behdad) -Status:1.0 - -Done. Complex path speed up by between 3.5x and 30x, as fast or faster than -simple path on benchmarks. - -### Remove the simple text code path. - -Owner(s):eae -Status:0.0 - -Was gated on making complex text as fast as simple. Was a bit too ambitious -perhaps, should be doable early Q3. - -### Build the plan to support updated Unicode Bidirectional Algorithm - -Owner(s):kojii -Status:0.2 - -Work under way, will carry over into Q3. - -### Raise the “Passed” rate of CSS Writing Modes Level 3 to 85% including new tests - -Owner(s):kojii -Status:1.0 - -86% as of early June. - -### Move line layout to LayoutUnit. - -Owner(s):szager (dsinclair) -Status:1.0 - -Done! - -### Finish root layer scrolling. - -Owner(s):skobes -Status:0.7 - -Fixed various things such as anchor scrolling, quirks mode, hit testing. Partial -coverage of unit tests with RLS enabled. Some issues remain with pinch viewport, -custom scrollbars, etc. Aiming to finish in Q3. - -### Ensure that bugs get automatically filed for clusterfuzz asserts. - -Owner(s):cbiesinger -Status:1.0 - -Done!
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/okrs/2015q3/index.md b/chromium/docs/website/site/teams/layout-team/okrs/2015q3/index.md deleted file mode 100644 index dd07c5d21a6..00000000000 --- a/chromium/docs/website/site/teams/layout-team/okrs/2015q3/index.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/okrs - - Objectives and Key Results -page_name: 2015q3 -title: 2015 Q3 ---- - -List of objectives and key results for the third quarter of 2015. - -## Overview - -* Objective / Key Result Owner(s) Status -* Interop (Interoperability, Compatibility, Conformance) - * [Update flexbox implementation to match latest version of - specification](#o0r0) cbiesinger - * [Remove page zoom](#o0r1) eae, blink-style - * [Updated Unicode Bidirectional Algorithm](#o0r2) kojii - * [Unprefix CSS Writing modes](#o0r3) kojii - * [Improve font fallback](#o0r4) drott - * [Spec work for houdini block & line custom layout](#o0r5) - ikilpatrick -* Improve code health - * [Have all calls into block layout go through well defined - API](#o1r0) leviw - * [Have a clear understanding of the cost/complexity of custom - layout.](#o1r1) leviw, ikilpatrick - * [Finish root layer scrolling](#o1r2) skobes, szager - * [Remove simple text code path](#o1r3) eae,drott - * [Improve integration between Blink and Harfbuzz](#o1r4) drott -* Bug Health - * [Triage all incoming layout bugs within one week](#o2r0) eae - * [Reduce bug count by 30%](#o2r1) eae -* RAIL (Measuring User Experience) - * [Reduce unnecessarily forced layouts](#o3r0) - * [Add UMA tracking & monitoring for different types of - layout](#o3r1) - * [Brainstorm/plan devtools/rail score/layout integration](#o3r2) - * [Trace layout on some popular websites in US, Europe, Brazil, - India](#o3r3) -* Spin up effort around spatial - * [Make progress on viewability/measure for the ads use - case](#o4r0) - -## Details - -### Update flexbox implementation to match latest version of specification - -Owner(s):cbiesinger -Score: - -### Remove page zoom - -Owner(s):eae, blink-style -Score: - -(shared with style team) - -### Updated Unicode Bidirectional Algorithm - -Owner(s):kojii -Score: - -### Unprefix CSS Writing modes - -Owner(s):kojii -Score: - -### Improve font fallback - -Owner(s):drott -Score: - -### Spec work for houdini block & line custom layout - -Owner(s):ikilpatrick -Score: - -### Have all calls into block layout go through well defined API - -Owner(s):leviw -Score: - -### Have a clear understanding of the cost/complexity of custom layout. - -Owner(s):leviw, ikilpatrick -Score: - -### Finish root layer scrolling - -Owner(s):skobes, szager -Score: - -### Remove simple text code path - -Owner(s):eae,drott -Score: - -### Improve integration between Blink and Harfbuzz - -Owner(s):drott -Score: - -### Triage all incoming layout bugs within one week - -Owner(s):eae -Score: - -### Reduce bug count by 30% - -Owner(s):eae -Score: - -### Reduce unnecessarily forced layouts - -Owner(s): -Score: - -### Add UMA tracking & monitoring for different types of layout - -Owner(s): -Score: - -(initial vs lifecycle) - -### Brainstorm/plan devtools/rail score/layout integration - -Owner(s): -Score: - -### Trace layout on some popular websites in US, Europe, Brazil, India - -Owner(s): -Score: - -### Make progress on viewability/measure for the ads use case - -Owner(s): -Score:
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/okrs/2015q4/index.md b/chromium/docs/website/site/teams/layout-team/okrs/2015q4/index.md deleted file mode 100644 index 4973ea6b1c6..00000000000 --- a/chromium/docs/website/site/teams/layout-team/okrs/2015q4/index.md +++ /dev/null @@ -1,250 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/okrs - - Objectives and Key Results -page_name: 2015q4 -title: 2015 Q4 ---- - -List of objectives and key results for 2015 Q4. - -## Overview - -* Objective / Key Result Owner(s) Score -* RAIL (Measuring User Experience) - * [Ship CSS containment to beta](#o0r0) leviw 0.60 - * [Smooth scrolling for wheel and keyboard scrolls in Win/Linux - enabled on trunk](#o0r1) skobes, ymalik 1.00 - * [Intersection observer on trunk](#o0r2) szager 0.95 - * [Integrate font related memory consumption to - memory-infra](#o0r3) drott 1.00 -* Interop (Interoperability, Compatibility, Conformance) - * [Have fullscreen implementation not modify layout tree](#o1r0) - bokan 0.00 - * [Have flexbox match latest version of spec](#o1r1) cbiesinger - 0.80 - * [Work with other vendors to nail down Custom Layout API](#o1r2) - ikilpatrick 0.90 - * [Support Blink/Android hyphen design work](#o1r3) szager 1.00 - * [Replace flexbox tests with W3C ones](#o1r4) cbiesinger 1.00 - * [Unprefix CSS Writing modes](#o1r5) kojii 0.70 - * [CSS font-feature-settings](#o1r6) kojii 0.00 -* Code health - * [Have root layer scrolling pass all unit tests](#o2r0) skobes, - szager 0.50 - * [Have prototype of ruby on top of custom layout \[kojii, - houdini-dev\]](#o2r1) blink-houdini, kojii 1.00 - * [Remove simple text](#o2r2) eae, drott 0.90 - * [Ship improved font fallback to stable](#o2r3) drott 0.75 - * [Finish wrapping block layout in an API](#o2r4) leviw, pilgrim - 0.70 - * [Add class level documentation to all key layout classes](#o2r5) - jchaffraix 1.00 - * [Feasibility study for replacing flipped flocks writing mode - implementation](#o2r6) wkorman 0.00 -* Bug Health - * [Continue to triage all bugs within one week](#o3r0) eae 1.00 - * [Fix all (new) P0/P1 within one release](#o3r1) eae 0.80 - * [Reduce untriaged bug count by 50%](#o3r2) eae, jchaffraix 1.00 - * [Reduce total bug backlog by 15%](#o3r3) eae 1.00 - -## Details - -### Ship CSS containment to beta - -Owner(s):leviw -Score:0.60 - -Editor’s Draft https://drafts.csswg.org/css-containment/ \[mid quarter\] On -track, intent to implement has been sent. Patch up for review. \[end of -quarter\] CSS and Paint containment implemented and available as experimental -web platform features. We're further along implementation wise than expected -however behind on shipping as CSS contain has yet to ship to beta. - -### Smooth scrolling for wheel and keyboard scrolls in Win/Linux enabled on trunk - -Owner(s):skobes, ymalik -Score:1.00 - -http://crbug.com/575 \[mid quarter\] On track, looking good. \[end of quarter\] -Enabled on trunk in time for the M49 branch. - -### Intersection observer on trunk - -Owner(s):szager -Score:0.95 - -\[mid quarter\] On track, harder and more time consuming than estimated. \[end -of quarter\] More work and much harder than originally estimated. Implementation -has been ready for over a month but delayed due to difficulties in getting it -reviewed and difficulties around agreeing on a memory model that'll make sense -in a post oil-pan world. Work completed about ten days after the end of quarter. - -### Integrate font related memory consumption to memory-infra - -Owner(s):drott -Score:1.00 - -\[mid quarter\] On track. \[end of quarter\] Memory instrumentation added for -key font metrics. - -### Have fullscreen implementation not modify layout tree - -Owner(s):bokan -Score:0.00 - -\[mid quarter\] De-staffed. At risk. \[end of quarter\] De-staffed as bokan -wasn't available to layout-dev to work on fullscreen or layout in general. Needs -new owner. - -### Have flexbox match latest version of spec - -Owner(s):cbiesinger -Score:0.80 - -\[mid quarter\] On track. \[end of quarter\] ? - -### Work with other vendors to nail down Custom Layout API - -Owner(s):ikilpatrick -Score:0.90 - -\[mid quarter\] On track. \[end of quarter\] Several meetings and discussions -with other vendors., Have broad consensus and expect us to be able to spec it in -Sydney. - -### Support Blink/Android hyphen design work - -Owner(s):szager -Score:1.00 - -\[mid quarter\] On track. \[end of quarter\] Sufficient support for design work -provided. drott/szager up to speed. - -### Replace flexbox tests with W3C ones - -Owner(s):cbiesinger -Score:1.00 - -\[mid quarter\] On track. \[end of quarter\] Done? - -### Unprefix CSS Writing modes - -Owner(s):kojii -Score:0.70 - -\[mid quarter\] On track. \[end of quarter\] - -### CSS font-feature-settings - -Owner(s):kojii -Score:0.00 - -\[mid quarter\] At risk. \[end of quarter\] ? - -### Have root layer scrolling pass all unit tests - -Owner(s):skobes, szager -Score:0.50 - -\[mid quarter\] De-emphasized to focus on intersection observer. Still making -solid progress though. \[end of quarter\] Some progress, but less than expected -due to Stefan being pulled of to do Intersection Observer. Steve fixed at least -one of the unit tests and a few of the layout tests, and added infrastructure -for tracking future progress on the layout tests via flag-specific expectations. - -### Have prototype of ruby on top of custom layout \[kojii, houdini-dev\] - -Owner(s):blink-houdini, kojii -Score:1.00 - -\[mid quarter\] Rough prototype exists, needs further work. \[end of quarter\] -Two independent prototypes created using slightly different APIs. Successfully -demonstrated that it is viable to re-implement ruby on top of a custom layout -API. Neither are production ready and both depend on a polyfil, as planned. - -### Remove simple text - -Owner(s):eae, drott -Score:0.90 - -\[mid quarter\] Always use complex text enabled on trunk. Plan is to remove code -for M50. \[end of quarter\] Harder than anticipated due to a number of -compatibility and perf issues, most severe being a perf regression in Mac AAT -backend due to n squared font fallback which took awhile to resolve. Patch to -remove simple text uploaded and approved. Will commit as soon as M49 has been -branched. Missing end of Q4 goal by two weeks. - -### Ship improved font fallback to stable - -Owner(s):drott -Score:0.75 - -\[mid quarter\] Shipped to beta. On track. \[end of quarter\] In 48 which goes -to stable in Jan 26. Missing end of Q4 goal by one month. - -### Finish wrapping block layout in an API - -Owner(s):leviw, pilgrim -Score:0.70 - -\[mid quarter\] At risk. \[end of quarter\] Still not quite done but getting -closer. - -### Add class level documentation to all key layout classes - -Owner(s):jchaffraix -Score:1.00 - -\[mid quarter update\] On track. \[end of quarter\] Comprehensive class level -documentation added as header comments to all key layout classes. - -### Feasibility study for replacing flipped flocks writing mode implementation - -Owner(s):wkorman -Score:0.00 - -http://crbug.com/535637 \[mid quarter\] Delayed to focus on paint performance. -At risk. \[end of quarter\] De-emphasized to focus on slimming paint which is -higher performance. Will carry over to Q1. - -### Continue to triage all bugs within one week - -Owner(s):eae -Score:1.00 - -\[mid quarter\] On track \[end of quarter\] All bugs triaged within one week of -filing (for new bugs) or one week of having the CR-Blink-Layout label added (for -old bugs, working down the backlog). - -### Fix all (new) P0/P1 within one release - -Owner(s):eae -Score:0.80 - -\[mid quarter\] On track \[end of quarter\] Still some ambiguity aroud the -definition of a P1 bugs. All P0 and release-blockers fixed within one release. -75% of all P1s, majority of remaining ones should like have been classified as -P2. - -### Reduce untriaged bug count by 50% - -Owner(s):eae, jchaffraix -Score:1.00 - -\[mid quarter\] On track to exceed goal. Reduced by 60% thus far. \[end of -quarter\] Reduced by over 70%, far exceeding goal of 50%. Down to 180 -unconfirmed/untriaged from 690 at the start of the quarter. - -### Reduce total bug backlog by 15% - -Owner(s):eae -Score:1.00 - -\[mid quarter\] On track to exceed goal. Reduced by 16% thus far. \[end of -quarter\] Reduced total open bug count by over 25%, exceeding goal of 15%. Down -to 1688 open bugs from 2310 at the start of the quarter.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/okrs/2016q1/index.md b/chromium/docs/website/site/teams/layout-team/okrs/2016q1/index.md deleted file mode 100644 index 6bcd1ae7195..00000000000 --- a/chromium/docs/website/site/teams/layout-team/okrs/2016q1/index.md +++ /dev/null @@ -1,215 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -- - /teams/layout-team/okrs - - Objectives and Key Results -page_name: 2016q1 -title: 2016 Q1 ---- - -List of objectives and key results for 2016 Q1. - -## Overview - -* Objective / Key Result Owner(s) Status -* Measure and improve performance - * [Ship CSS Containment as experimental feature to stable.](#o0r0) - leviw - * [Gather data on number of third party iframes loaded but never - viewed.](#o0r1) szager - * [Collect metrics and do analysis on forced layouts.](#o0r2) - cbiesinger - * [Stretch: Reduce number of forced layouts for one common - trigger.](#o0r3) cbiesinger - * [Ship intersection observer to stable.](#o0r4) ojan, szager -* Interop (Interoperability, Compatibility, Conformance) - * [Spec for custom layout.](#o1r0) blink-houdini, ikilpatrick - * [Finish up worklet implementation.](#o1r1) blink-houdini, - ikilpatrick - * [Socialize resize observers specification.](#o1r2) atotic - * [Collect data on percentage margin usage.](#o1r3) eae - * [Ship updated absolute position behavior for flexbox to - stable.](#o1r4) cbiesinger - * [Upstream 75% of our flexbox test to w3c.](#o1r5) cbiesinger - * [Make progress on text autosizing spec](#o1r6) pdr - * [Evangelize CSS containment and get another browser to commit to - it.](#o1r7) leviw, shanestephens -* Code health - * [Root layer scrolling passing all unit tests.](#o2r0) skobes - * [Design doc for internal layout api](#o2r1) leviw - * [Line layout API analysis document](#o2r2) dgrogan, pilgrim - * [Stretch: Ruby on top of custom layout as experimental web - platform feature on trunk.](#o2r3) kojii - * [Ship emoji & punctuation fallback overhaul on all - platforms.](#o2r4) drott - * [Feasibility study for replacing flipped blocks writing mode - implementation.](#o2r5) wkorman -* Product excellence - * [Ship improved web typography to beta.](#o3r0) drott - * [Triage all incoming bug reports within one week and eliminate - backlog.](#o3r1) eae - * [Fix all new P1 bug reports within one release.](#o3r2) eae - * [Start to make vertical rhythm on the web easier.](#o3r3) kojii - * [Prototype scroll anchoring on layout.](#o3r4) skobes - -## Details - -### Ship CSS Containment as experimental feature to stable. - -Owner(s):leviw -Score: - -### Gather data on number of third party iframes loaded but never viewed. - -Owner(s):szager -Score: - -### Collect metrics and do analysis on forced layouts. - -Owner(s):cbiesinger -Score: - -### Stretch: Reduce number of forced layouts for one common trigger. - -Owner(s):cbiesinger -Score: - -Common triggers include: - I'm an iframe and need to know my size -(clientHeight/width) - I'm an iframe or component and need to know if i'm -visible. (scrollTop, etc) - I want to lazyload images or components when the -user gets closer (scrollTop) - I'm a metrics script and need to report the -window size (window.clientWidth, etc) - I need to set my dimensions based on the -computed width/height of something else. (clientHeight/Width) - Need to set -focus(), because new component is active. (elem.focus()) - I'm jQuery or -Modernizr and use computed style to identify features or bugs. - -### Ship intersection observer to stable. - -Owner(s):ojan, szager -Score: - -Stretch: pay down technical depth by moving things to use the intersection -observer infrastructure, such as: - render throttling for offscreen - video auto -play - -### Spec for custom layout. - -Owner(s):blink-houdini, ikilpatrick -Score: - -### Finish up worklet implementation. - -Owner(s):blink-houdini, ikilpatrick -Score: - -Help Audio & CW folks transition as needed. - -### Socialize resize observers specification. - -Owner(s):atotic, blink-houdini -Score: - -### Collect data on percentage margin usage. - -Owner(s):eae -Score: - -### Ship updated absolute position behavior for flexbox to stable. - -Owner(s):cbiesinger -Score: - -### Upstream 75% of our flexbox test to w3c. - -Owner(s):cbiesinger -Score: - -### Make progress on text autosizing spec - -Owner(s):pdr -Score: - -(20% project) -https://docs.google.com/document/d/1hlg1TworBMsvSMdLz4n5DxFr8Bex7S8eB_p0GpFrdVU/edit - -### Evangelize CSS containment and get another browser to commit to it. - -Owner(s):blink-houdini, leviw, shanestephens -Score: - -### Root layer scrolling passing all unit tests. - -Owner(s):skobes -Score: - -### Design doc for internal layout api - -Owner(s):leviw -Score: - -Including feasibility study for supporting a custom-layout style API in -conjunction with our legacy layout implementation. - -### Line layout API analysis document - -Owner(s):dgrogan, leviw, pilgrim -Score: - -Have an analysis document detailing the current organic API and a plan for -transitioning towards the API we'd like. Make decision, based on document, -whether the exercise was useful and if so if we should continue with the rest of -the layout API. - -### Stretch: Ruby on top of custom layout as experimental web platform feature on trunk. - -Owner(s):kojii -Score: - -### Ship emoji & punctuation fallback overhaul on all platforms. - -Owner(s):drott -Score: - -### Feasibility study for replacing flipped blocks writing mode implementation. - -Owner(s):wkorman -Score: - -### Ship improved web typography to beta. - -Owner(s):drott -Score: - -- OpenType Enabling - smcp, - Enable all font-feature-settings and -font-variant-\* CSS - CSS font-synthesis attribute (faux bold & italics control) - -### Triage all incoming bug reports within one week and eliminate backlog. - -Owner(s):eae -Score: - -### Fix all new P1 bug reports within one release. - -Owner(s):eae -Score: - -This is a bit o a stretch given that we don't yet have a team-wide definition of -a P1 bug but nevertheless it is something we really should try to do! - -### Start to make vertical rhythm on the web easier. - -Owner(s):kojii -Score: - -https://github.com/kojiishi/snap-height - -### Prototype scroll anchoring on layout. - -Owner(s):skobes -Score: - -crbug.com/558575 - user facing feature and a prerequisite for many potential -user agent interventions.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/okrs/index.md b/chromium/docs/website/site/teams/layout-team/okrs/index.md deleted file mode 100644 index d9c8eb1b82d..00000000000 --- a/chromium/docs/website/site/teams/layout-team/okrs/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -page_name: okrs -title: Objectives and Key Results ---- - -This page holds our quarterly objectives and a set of key results for each -objective. At the beginning of each quarter the OKRs from the preceding quarter -are evaluated and graded and the ones for the coming quarter are agreed upon. - -* [2016 Q1](/teams/layout-team/okrs/2016q1) -* [2015 Q4](/teams/layout-team/okrs/2015q4) -* [2015 Q3](/teams/layout-team/okrs/2015q3) -* [2015 Q2](/teams/layout-team/okrs/2015q2) -* [2015 Q1](/teams/layout-team/okrs/2015q1)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/layout-team/potential-projects/index.md b/chromium/docs/website/site/teams/layout-team/potential-projects/index.md deleted file mode 100644 index b32e870e822..00000000000 --- a/chromium/docs/website/site/teams/layout-team/potential-projects/index.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/layout-team - - Layout Team -page_name: potential-projects -title: Roadmap / Potential Projects ---- - -List of potential future projects (aka wishlist) for the layout team. -Relative priority in square brackets, based on impact, cost of implementing and -feedback from real-world web sites and web app teams. - -## In Scope Projects - -The backlog is now maintained in monorail, please see the -[layout-backlog](https://bugs.chromium.org/u/3593919584/hotlists/layout-backlog) -hotlist. - -## Out of Scope - -Potential projects that have been considered and rejected as being out-of-scope, -either due to the projects itself being premature, due to it being better suited -for a different team, or not considered important enough at the moment. - -* Viewporting and Infinite lists - Too early, silk TLs need to discuss this further. -* String of HTML into Fragment - This is job of scheduler team. -* When layout happens, calcDrawProps and sendInvalidations runs long - Falls onto the [paint team](/teams/paint-team). -* Repaint storm elimination & invalidation - Tackled by [Slimming Paint](/blink/slimming-paint). -* UIWorker / Animation Proxy - Too early, silk TLs need to discuss this further. -* Expose what triggered a layout in devtools - Show in devtools which line of JS caused a layout, which nodes generated an - invalidation, why it took as long as it did. Falls on the devtools team. -* Element - [onPaint](https://docs.google.com/a/chromium.org/document/d/1BmS4vT5RtTxg_HH_33bU1PNwVZR4ZsNpOagWjEsETA8/edit) - callback - Falls on the [paint team](/teams/paint-team). -* HTML Canvas - Falls on the GPU or graphics team.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/paint-team/canvas-okrs/index.md b/chromium/docs/website/site/teams/paint-team/canvas-okrs/index.md deleted file mode 100644 index a4d49fff440..00000000000 --- a/chromium/docs/website/site/teams/paint-team/canvas-okrs/index.md +++ /dev/null @@ -1,273 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/paint-team - - Paint Team (paint-dev) -page_name: canvas-okrs -title: Canvas team OKRs ---- - -## Q4 2016 - -Ship OffscreenCanvas -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) -[#wp-ergonomics](https://easyokrs.googleplex.com/search/?q=wp-ergonomics) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[junov](https://easyokrs.googleplex.com/view/junov/), -[xidachen](https://easyokrs.googleplex.com/view/xidachen/), -[xlai](https://easyokrs.googleplex.com/view/xlai/) - -* Lead: xlai - -* implement convertToBlob -* Owner: [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Make placeholder canvas elements work as image sources (drawImage, - toBlob, etc) -* Owner: [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Ship it in M57 -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/) -* This includes achieving full spec conformance. -* Make a convincing performance demo, and support devrel with launch - PR -* Owner: [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Land the specification against whatwg -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Get canvas filters to work in a Worker -* Owner: [fserb](https://easyokrs.googleplex.com/view/fserb/) -* Make OffscreenCanvas commit flow works in the Android WebView -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Write tests that verify that it works, fix if necessary. - -<img alt="Copy" src="https://easyokrs.googleplex.com/images/copy.svg">[<img -alt="Link" -src="https://easyokrs.googleplex.com/images/link.png">](https://easyokrs.googleplex.com/o/2361706/) - -OffscreenCanvas testing and tracking -[#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[junov](https://easyokrs.googleplex.com/view/junov/), -[xidachen](https://easyokrs.googleplex.com/view/xidachen/), -[xlai](https://easyokrs.googleplex.com/view/xlai/) - -* Lead: xidachen - -* Contribute to web platform tests -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Achieve complete test coverage: Each statement in the spec should be - covered by tests, with xrefs to the spec. - Upstream the tests to web platform tests repo, test other implementations - for conformance - Main owner/coordinator is xidachen. xlai and junov are contributors. -* Add telemetry performance tests for OffscreenCanvas -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Must cover commit() and ImageBitmap flows, cover all permutations of - GPU/CPU rendering and compositing, run on GPU bots. -* Add usage metrics histograms. -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Must track: - \* OffscreenCanvas feature usage - \* mode of operation (commit vs transferToImageBitmap) - \* commit() code path - \* CPU run time for each commit() code path (on the thread where commit is - called) - \* commit() latency (time elapsed from commit() call to UI compositor - update) -* Have the fastest implementation -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Write animometer-style benchmarks for OffscreenCanvas (commit and - imageBitmap flows, 2D and WebGL). Compare to other implementations. - Stay on top - Main owner/coordinator: xidachen. junov and xlai to contribute to fixing - perf issues. - -requestAnimationFrame in Workers -[#wp-ergonomics](https://easyokrs.googleplex.com/search/?q=wp-ergonomics) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[junov](https://easyokrs.googleplex.com/view/junov/) - -* Implement it -* Spec it -* Ship it in M57 - -Product excellence -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[xidachen](https://easyokrs.googleplex.com/view/xidachen/), -[xlai](https://easyokrs.googleplex.com/view/xlai/) - -* Lead: xidachen - -* Weekly product excellence report -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Publish weekly report to chrome-canvas mailing list. - Bug stats: outstanding bug count (number fixed, number of new bugs), list of - high-profile outstanding bugs (crashers, security, regressions, highly - starred, p0-p1), high profile bugs resolved since last report. Keep report - history in a google doc. - Delegate reporting when on leave. -* Performance metrics report -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Twice in the quarter, present to paint team show salient - fluctuations in key performance metrics. -* Prevent bug count from creeping up. -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/), - [zakerinasab](https://easyokrs.googleplex.com/view/zakerinasab/) -* (104 outstanding bugs as of October 5 2016) -* Refactor Canvas and OffscreenCanvas dependencies on cc -* Owners: [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/) - -Misc canvas features -[#wp-ergonomics](https://easyokrs.googleplex.com/search/?q=wp-ergonomics) - -Owner: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/) - -* Make experimental implementation of canvas colorspace work -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [zakerinasab](https://easyokrs.googleplex.com/view/zakerinasab/) -* Experimental implementation of text rendering in workers (stretch) -* Owner: - [zakerinasab](https://easyokrs.googleplex.com/view/zakerinasab/) -* 0.5 for getting text to render using only the default font. -* Ship DOMMatrixInit-based canvas APIs (stretch) -* Owner: [xlai](https://easyokrs.googleplex.com/view/xlai/) - -## Q3 2016 - -OffscreenCanvas feature complete -[#wp-future](https://easyokrs.googleplex.com/search/?q=wp-future) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[junov](https://easyokrs.googleplex.com/view/junov/), -[xidachen](https://easyokrs.googleplex.com/view/xidachen/), -[xlai](https://easyokrs.googleplex.com/view/xlai/) - -* 0.80P2commit() flow working for 2D canvas -* Owner: [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Mid-quarter status: Stalled for about 3 weeks due to dependency on - mojo improvements. Still on track for EOQ - EOQ status: Mostly implemented except software compositing cases -* 0.80P2commit() flow working for WebGL -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Mid-quarter status: Not started, still possible by EOQ. - EOQ status: Mostly implemented except software compositing cases -* 1.00P3GPU-accelerated 2D canvas in a worker -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Mid-quarter status: WIP CL almost done. On track. - EOQ status: done. -* 0.50P1Finish specification for OffscreenCanvas (rolled over from Q2) -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Mid-quarter status: iterated on proposal some more, still attainable - by EOQ, moderate risk of slipping. - EOQ: Draft complete, not yet publicly shared. -* 0.80P3Canvas readback APIs + tainting for 2D -* Owner: [xlai](https://easyokrs.googleplex.com/view/xlai/) -* getImageData + toBlob + toDataURL working on OffscreenCanvas on main - thread + Workers (stretch) - Mid-quarter status: WIP, tainting for 2D completed, the rest partially - implemented, at risk of slipping into Q4 - EOQ status: done, except for toBlob which is not yet implemented - -<img alt="Copy" src="https://easyokrs.googleplex.com/images/copy.svg">[<img -alt="Link" -src="https://easyokrs.googleplex.com/images/link.png">](https://easyokrs.googleplex.com/o/2239617/) - -0.10P3Canvas color space support -[#wp-future](https://easyokrs.googleplex.com/search/?q=wp-future) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[junov](https://easyokrs.googleplex.com/view/junov/) - -* Mid-quarter: Slow progress so far this Q, work on colorspace - implementation is ramping up with - [zakerinasab@](https://teams.googleplex.com/zakerinasab) - -* 0.00P2Converge spec proposal -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Close all unresolved issues about the proposal on the W3C WICG forum - Mid-quareter status: No progress. Still attainable this Q -* 0.00P3Write spec (stretch) -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Commit CanvasColorSpace spec against WHATWG HTML spec. - Mid-quarter status: No progress, not likely this quarter. -* 0.30P4Prototype/experimental implementation in Blink -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Mid-qarter status: Partially landed. Experimental API is there, - color space plumbing in the compositor is there, not functional due - to several missing pieces in skia, blink and compositor. - -0.74P1Product Excellence -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -Owners: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/), -[junov](https://easyokrs.googleplex.com/view/junov/), -[xidachen](https://easyokrs.googleplex.com/view/xidachen/), -[xlai](https://easyokrs.googleplex.com/view/xlai/) - -* 0.80P2Reduce bug count -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Go from 121 to under 100 open bugs (Type = Bug + Bug-Regression + - Bug-Security) - Mid-quarter status: 106 outstanding bugs. On track! - EOQ status: 104 bugs. -* P1Resolve all memory leak-like issues related to canvas -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Mid-quarter status: Out of our hands: dependency on V8 team GC - triggers. -* 0.80P12 week SLA on fixing crashers and security bugs -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/), - [xlai](https://easyokrs.googleplex.com/view/xlai/) -* Mid-quarter status: On track. - EOQ status: crasher 624718 is lagging behind. Otherwise we did good. -* 1.00P21 week SLA on triage -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Mid-quarter status: on track - EOQ: done. -* 0.50P3Be the best browser for all canvas-related Animometer - benchmark scores -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* (Includes work by intern sebastienlc) - Mid-quarter status: implemented but not enabled. Not on track because no one - is currently owning follow-up on intern's work. Postponing. - EOQ status: some heuristic for falling back to SW have been implemented, - thus preventing critical performance cliffs. Global approach is not ready to - ship. -* 0.60P2Fix top starred issues -* Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* crbug.com/618324 - Experimental \`imageSmoothingQuality\` property - doesn't provide expected quality - crbug.com/7508 - We don't anti-alias <canvas> drawImage - Mid-quarter status: 7508 is fixed, 618324 has been investigated but will - probably not be fixed this quarter. - EOQ status: 1/2 bugs fixed + bonus bug 424291 - -Misc Features [#wp-future](https://easyokrs.googleplex.com/search/?q=wp-future) -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) - -Owner: [chrome-canvas](https://easyokrs.googleplex.com/view/chrome-canvas/) - -* 0.70P3Ship ImageBitmap resize -* Owner: [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Mid-quarter status: on track - EOQ staus: implementation complete, but not shipped -* 0.90P2Ship ImageSmoothingQuality -* Owner: [junov](https://easyokrs.googleplex.com/view/junov/) -* Mid-quarter status: done, but there are outstanding complaint about - the quality of the mipmaps used for high quality filtering.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/paint-team/index.md b/chromium/docs/website/site/teams/paint-team/index.md deleted file mode 100644 index 4ee4b1b63a7..00000000000 --- a/chromium/docs/website/site/teams/paint-team/index.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: paint-team -title: Paint Team (paint-dev) ---- - -The paint team has been subsumed into the new [rendering -core](//chromium.org/teams/rendering) team. Please see the rendering core page -for details about ongoing paint and canvas work.
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/paint-team/okrs/index.md b/chromium/docs/website/site/teams/paint-team/okrs/index.md deleted file mode 100644 index ce09502005f..00000000000 --- a/chromium/docs/website/site/teams/paint-team/okrs/index.md +++ /dev/null @@ -1,1217 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/paint-team - - Paint Team (paint-dev) -page_name: okrs -title: Paint team OKRs ---- - -## Q1 2017 - -Code health -[#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* P1# of open bugs did not increase during the quarter -* Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* Starting point: 1350 on Jan 3, 2017 -* P2Reduce # of failing layout tests, layout test fix SLA -* Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* Starting point: 58 on Jan 3, 2017 -* P1No regressions reach the M57 or later stable channel -* Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* Should this be M56 and later, given it has not gone to stable yet? - -Improve quality of implementation -[#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) -[#wp-architecture](https://easyokrs.googleplex.com/search/?q=wp-architecture) - -* P2Top-starred bugs fixed -* Fix at least the following" - \* White flash: <http://crbug.com/470669> (chrishtr) - \* Blurry fractional posn text: <http://crbug.com/521364> (trchen) - \* Jittery images: <http://crbug.com/608874> (schenney) - \* border-radius children: <http://crbug.com/157218> (schenney) - \* imageSmoothingQuality not right: <http://crbug.com/618324> (junov) - \* flickering dithered content: <http://crbug.com/226753> (fmalita) - \* raster scale heuristics: <http://crbug.com/652448> (chrishtr) - \* SVGTextContentElement.getSubStringLength(): <http://crbug.com/622336> - (pdr) - \* Mac controls painting bugs: 607438, 611753, 158426 (schenney) -* P2Remove need for FrameView::forceLayoutParentViewIfNeeded in SVG -* Owner: fs@opera.com - -Understand, maintain and improve performance -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* P1Measure performance and prevent any performance regressions from - reaching the stable channel -* Owner: [wkorman](https://easyokrs.googleplex.com/view/wkorman/) - -Improve paint/compositing interfaces -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) -[#wp-architecture](https://easyokrs.googleplex.com/search/?q=wp-architecture) - -Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), -[chrishtr](https://easyokrs.googleplex.com/view/chrishtr/), -[paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), -[wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/), -[wkorman](https://easyokrs.googleplex.com/view/wkorman/) - -* P1SPv2 works for all effects, including mask -* Owner: [trchen](https://easyokrs.googleplex.com/view/trchen/) -* P1SPv2 works for scrolling and scrollbars -* Owner: [pdr](https://easyokrs.googleplex.com/view/pdr/) -* P1SPv2 works for animation metadata and touch event regions -* Owner: [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* P1PaintArtifactCompositor layerization as good as - PaintLayerCompositor -* Owners: [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/), - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* P1Finish removing target knowledge from clip and transform trees -* Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), - [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* P1Cache dynamically-determined clips -* Owner: [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* P1Stop requiring a cc::Layer for any property tree nodes -* P2Build the RenderSurfaceLayerList from effect trees -* Owner: [ajuma](https://easyokrs.googleplex.com/view/ajuma/) -* P1Launch SlimmingPaintInvalidation -* Owner: - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* P1Design and prototype implementation of border-radius clipping in - SPv2 -* Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), - [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/) -* Stretch additional goal: implement & land it - -Support other teams' work - -Owners: [chrome-gpu](https://easyokrs.googleplex.com/view/chrome-gpu/), -[paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* Promote more opaque scrollers and fixed-position elements in the - presence of LCD text -* Owners: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [threaded-rendering](https://easyokrs.googleplex.com/view/threaded-rendering/) -* threaded-rendering: implement - paint-dev: support - Fix discovered compositing bugs, re-enable fixed position promotion. Promote - scrollers with border-radius, box shadow, and scrollers/sticky/fixed - elements containing no text. -* P1Apply border radius clipping to non-stacking descendants -* Owners: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [threaded-rendering](https://easyokrs.googleplex.com/view/threaded-rendering/) -* crbug.com/157218 - paint-dev: implement feature - threaded-rendering: implement tiled masks for efficiency -* P2Implement color correction in blink -* Owners: - [chrome-gpu](https://easyokrs.googleplex.com/view/chrome-gpu/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* ccameron: implementation - paint-dev: support -* P3Fully threaded scrolling with touch-action -* Owners: - [input-dev-eventing](https://easyokrs.googleplex.com/view/input-dev-eventing/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* paint-dev, input-dev: design for touch-action in SPv2 -* P3Simplify paint usage of Sk\*Shaders -* Owners: - [chrome-gpu](https://easyokrs.googleplex.com/view/chrome-gpu/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* This is to support easier implementation of custom display lists - -Code Health and Future Design - -Owner: -[input-dev-eventing](https://easyokrs.googleplex.com/view/input-dev-eventing/) - -* P3Touch-action hit testing -* Owners: [dtapuska](https://easyokrs.googleplex.com/view/dtapuska/), - [flackr](https://easyokrs.googleplex.com/view/flackr/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* [#wp-architecture](https://easyokrs.googleplex.com/search/?q=wp-architecture), - [#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) - Have a concrete design of how SPV2 will information necessary for - touch-action hit testing on the compositor. - -Support other teams' work - -Owners: [chrome-gpu](https://easyokrs.googleplex.com/view/chrome-gpu/), -[paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* Promote more opaque scrollers and fixed-position elements in the - presence of LCD text -* Owners: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [threaded-rendering](https://easyokrs.googleplex.com/view/threaded-rendering/) -* threaded-rendering: implement - paint-dev: support - Fix discovered compositing bugs, re-enable fixed position promotion. Promote - scrollers with border-radius, box shadow, and scrollers/sticky/fixed - elements containing no text. -* P1Apply border radius clipping to non-stacking descendants -* Owners: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [threaded-rendering](https://easyokrs.googleplex.com/view/threaded-rendering/) -* crbug.com/157218 - paint-dev: implement feature - threaded-rendering: implement tiled masks for efficiency -* P2Implement color correction in blink -* Owners: - [chrome-gpu](https://easyokrs.googleplex.com/view/chrome-gpu/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* ccameron: implementation - paint-dev: support -* P3Fully threaded scrolling with touch-action -* Owners: - [input-dev-eventing](https://easyokrs.googleplex.com/view/input-dev-eventing/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* paint-dev, input-dev: design for touch-action in SPv2 -* P3Simplify paint usage of Sk\*Shaders -* Owners: - [chrome-gpu](https://easyokrs.googleplex.com/view/chrome-gpu/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* This is to support easier implementation of custom display lists - -## Q4 2016 - -Code health [#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* 1.00P1# of open bugs did not increase during the quarter -* Owners: [schenney](https://easyokrs.googleplex.com/view/schenney/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* Mid-quarter update: on track. 1383 -> 1385, including addition of - a new component. - End of quarter: 1383 on Sept 29, 2016 to 1350 on Jan 3, 2017. -* 0.70P1No regressions reach the M55 or later stable channel -* Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* Still on track. - End of quarter update: - 2 Regression reached M54, not really part of OKR: - <https://bugs.chromium.org/p/chromium/issues/detail?id=655941>, - <https://bugs.chromium.org/p/chromium/issues/detail?id=662378> - One regressions reached M55 specifically. - M56 not to stable yet. -* 0.10P2Reduce # of failing layout tests, layout test fix SLA -* Owners: [schenney](https://easyokrs.googleplex.com/view/schenney/), - [xidachen](https://easyokrs.googleplex.com/view/xidachen/) -* 1. Reduce # of steady-state failing layout tests by 50% - 2. Fix all new layout test regressions within 2 weeks - Directories: - LayoutTests/paint/... - LayoutTests/compositing/... (except compositing/animations) - LayoutTests/svg/... - LayoutTests/hittesting/... - LayoutTests/fast/images/... - LayoutTests/css3/images/... - LayoutTests/canvas/... - Mid-quarter-update: Negligible overall reduction this quarter. - TODO(schenney) check lifetime of new regressions - End of Quarter: No significant reduction, total count increased - significantly due to random order test flakiness. Regression tracking - process failed. - Non-zero score because we did go down except for factors beyond our control. - 35 -> 34 before random-order jump. - -<img alt="History" src="https://easyokrs.googleplex.com/images/history.png"><img -alt="Copy" src="https://easyokrs.googleplex.com/images/copy.svg">[<img -alt="Link" -src="https://easyokrs.googleplex.com/images/link.png">](https://easyokrs.googleplex.com/o/2336130/) - -0.56P2Improve quality of implementation -[#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* 0.56P2Top-starred bugs fixed -* Owner: [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/) -* Fix at least these: 521364, 470669, 608874, 157218, 618324, 226753, - 652448, 468497, 622336 - Mid-quarter update: some progress, but needs work. 468497 is done. Review - for 470669 currently in review. 521364 still in progress. 157218 in - progress, close to patches landing. 652448 in progress, vmpstr doing good - work to support. - End of quarter: - \* 521364: CLs in review - \* 470669 fixed, bug blocked on fix for crbug.com/21798. - \* 608874 no progress - \* 157218 landed Dec 12, reverted Dec 13, re-landed January 5, perf issues - and 2 bugs still open. - \* 618324 no progress - \* 226753 investigated, no longer repros on later OS X updates. Probably not - going to fix. - \* 652448 prototyped, but concluded design proposal is not feasible in SPv1 - \* 468497 fixed - \* 622336 no progress - Fixed/close to fixed: 3 - mostly there: 2 - WontFix: 1 - No progress: 3 - Total score: (1.0\* 3 + 0.75 \* 2 + 0 \* 3) / 8 = 0.56 -* 1.00P2SVG filter hack in FrameView is gone -* Owner: fs@opera.com - Mid-quarter: on track! Code in review. -* 0.00P2Remove need for FrameView::forceLayoutParentViewIfNeeded in - SVG -* Owner: fs@opera.com - Mid-quarter: ? -* 0.00P2Widget hierarchy is gone -* Owners: [szager](https://easyokrs.googleplex.com/view/szager/), - [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* crbug.com/637460 - Mid-quarter: not yet started. - EOQ: no progress - -1.00P1Understand, maintain and improve performance -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* 1.00P1Measure performance and prevent any performance regressions - from reaching the stable channel -* Owner: [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* Mid-quarter update: on track. Only thing being tracked is the Linux - regression on M54 stable. - EOQ: still going well -* 1.00P1Composited opaque scrolling for low-DPI screens -* Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* Mid-quarter update: basically done. Launching with M56. - End of quarter: Landed for M56. Paint update time drops evident in UMA data. - No outstanding open issues. - -0.58P2Improve paint/compositing interfaces -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) -[#wp-architecture](https://easyokrs.googleplex.com/search/?q=wp-architecture) - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* 0.25P1SPv2 works all effects, including mask -* Owner: [trchen](https://easyokrs.googleplex.com/view/trchen/) -* Mid-quarter update: needs more work. implemented for filters. Masks - not done. - Overall, also blocked on creating render surfaces in SPv2. - EOQ: some progress, but still a ways to go. Some design thought about masks. -* 0.00P1SPv2 works for scrolling and scrollbars -* Owner: [pdr](https://easyokrs.googleplex.com/view/pdr/) -* Mid-quarter update: needs attention. no progress this quarter. - EOQ: no progress. -* 0.50P1SPv2 works for animation metadata and touch event regions -* Owner: [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* Mid-quarter update: needs attention. no progress this quarter. - EOQ: design investigation, early implementation. -* 1.00SPv2 compatible ancestor-dependent and descendant-dependent - PaintLayer values -* Owner: [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/) -* Mid-quarter update: needs attention. no progress this quarter. - EOQ: done! Design and implementation in place. -* 0.75P2SPv2 paint invalidation test infrastructure -* Owner: [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/) -* Mid-quarter update: landed changes to unify paint invalidation - output format between SPv1 and SPv2. Tests not converted yet. - EOQ: done! Design and implementation in place. Tests not converted yet, but - that wasn't in the KR description. -* 0.60P1PaintArtifactCompositor property tree optimization -* Owner: [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/) -* Passes all compositing tests with equivalently performant - layerization - Mid-quarter update: needs attention. no progress this quarter. - EOQ: designed implemented the optimizations. But not all compositing tests - passing yet. - -0.46P1Finish cc property tree implementation -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), -[jaydasika](https://easyokrs.googleplex.com/view/jaydasika/), -[paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), -[sunxd](https://easyokrs.googleplex.com/view/sunxd/) - -* 0.75P1Finish removing target knowledge from clip and transform trees -* Owner: [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* Mid-quarter update: transforms done! Calculating clips done (behind - a flag), just needs caching implementation.' - EOQ: transforms done, clips getting close. -* 1.00P1Cache dynamically-determined transforms -* Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), - [sunxd](https://easyokrs.googleplex.com/view/sunxd/) -* Mid-quarter update: done! TODO(ajuma): check if property update UMA - metrics moved due to this.'' - EOQ done. -* 0.50P1Stop requiring a cc::Layer for any property tree nodes -* Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), - [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* Mid-quarter update: on track. some progress, but work to do. - EOQ: not done. still several references. -* 0.00P1Build the RenderSurfaceLayerList from effect trees -* Owner: [ajuma](https://easyokrs.googleplex.com/view/ajuma/) -* Mid-quarter update: at risk. no progress yet, still consumed with - other work. - EOQ: no progress -* 0.50Cache dynamically-determined clips -* Owner: [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* Mid-quarter update: no progress yet, work starting soon. - EOQ: implementation getting close -* 0.00P2Simplify transform property nodes -* Owner: [ajuma](https://easyokrs.googleplex.com/view/ajuma/) -* 1. Only one transform per node - 2. No caching (tracked via "Cache dynamically-determined transforms" - however) - Mid-quarter update: no progress. - EOQ: no progress - -P2New features - -Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* 0.10P2Drive tentative standards agreement on a raster scale spec - [#wp-ergonomics](https://easyokrs.googleplex.com/search/?q=wp-ergonomics) -* Raster scale defines the scale at which to raster composited layers - Note: crbug.com/652448 tracks doing this automatically for background - images, and is tracked in another - KR. - Mid-quarter update: no progress. - EOQ: prototyping of automatic version for images didn't work out. Going to - revert code. No progress - any standards discussion. -* 0.00P2Fix all bugs blocking backdrop-filter launch - [#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) -* Owner: [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* All dependent bugs of crbug.com/497522 fixed. - Mid-quarter update: no progress so far. - EOQ update: no progress. - -0.93P1Improve paint invalidation correctness and performance -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) - -Owners: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), -[wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) - -* Mid-quarter update: on track. lots of progress simplifying the code - and fixing bugs. - -* 0.75P1Launch slimmingPaintInvalidation -* Owner: - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* Mid-quarter update: on track. Close to a complete implementation. - EOQ: launched to experimental status -* 1.00P1Implement incremental paint property tree update -* Owners: [pdr](https://easyokrs.googleplex.com/view/pdr/), - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* Mid-quarter update: on track. Code mostly done and design complete. - EOQ: done! -* 1.00P1Implement all SPv1 invalidation features in - slimmingPaintInvalidation mode, or deprecate them if obsolete -* Owner: - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* Mid-quarter update: on track. Lots of progress. - EOQ: done! - -## Q3 2016 - -## Code health [#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -## Owners: [junov](https://easyokrs.googleplex.com/view/junov/), -[paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), -[schenney](https://easyokrs.googleplex.com/view/schenney/) - -* ## 1.00P2# of open bugs did not increase during the quarter -* ## Owners: [junov](https://easyokrs.googleplex.com/view/junov/), - [schenney](https://easyokrs.googleplex.com/view/schenney/) -* ## Baseline starting point: 1323 open bugs as of July 8 2016 for - these labels: - ## Blink>Paint, Blink>Paint>Invalidation, Blink>Compositing, - Blink>SVG, Blink>Canvas, Blink>Image - ## Mid-quarter update: on track. Bugs down to 1295 (2.1% decrease) - ## EOQ update: 1311 as of 9/29 (plus 54 for the new HitTesting component) -* ## 1.00P17-day SLA for triaging all incoming bugs -* ## Owners: - [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/), - [junov](https://easyokrs.googleplex.com/view/junov/), - [schenney](https://easyokrs.googleplex.com/view/schenney/) -* ## Another owner: fs@opera.com - ## Mid-quarter update: on track. Holding around zero. - ## EOQ update: met goal. -* ## 0.75P1No regressions reach the M52 or later stable channel. -* ## Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* ## Definition: bug is a regression that ends up bisected to a commit - after the M52 branch point, yet made its way - ## to the stable channel. - ## Mid-quarter update: at risk. We already have one; crbug.com/635724 might - leak to M53 stable. - ## EOQ update: crbug.com/646363 made it to stable M53. crbug.com/637556 made - it to M52 stable. No bug reached stable due to a triage failure. Problem was - late reporting of the bug. -* ## 1.00P3Monitor # of failing layout tests -* ## Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* ## Directories: fast/repaint/\*, paint/\*, compositing/\*, svg/\*, - fast/canvas/\*, canvas/\* - ## Mid-quarter update: on track. - ## EOQ update: met -* ## 1.00P2Document an official triage process -* ## Owners: - [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/), - [schenney](https://easyokrs.googleplex.com/view/schenney/) -* ## Mid-quarter update: on track. - ## EOQ update: met - -## 0.40Improve quality of implementation -[#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -## Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* ## 0.40P1Top-starred bugs fixed -* ## Owner: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* ## Fix at least these: 521364, 470669, 608874, 157218, 618324, - 226753, 409868, 470608 - ## Update: at risk. Only one of these bugs is fixed so far. - ## EOQ update: - ## - 521364 is close to done - ## - 470669 unblocked by dependent bug a few days ago - ## - 608874 no progress - ## - 157218 has a prototype fix - ## - 618324 not clear how to fix yet - ## - 226753 no progress - ## - 409868 WontFixed - ## - 470608 Fixed. - ## Score: 2/8 done, 2/8 close to done, 4/8 not done: 2/8 \* 1 + 2/8 \* 0.75 - = 0.43 ~ 0.4 -* ## 0.60P2SVG filter hack in FrameView is gone -* ## Owner: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* ## Ref: Document::hasSVGFilterElementsRequiringLayerUpdate - ## Owner: fs@opera.com - ## Update: at risk. More work upcoming. - ## EOQ update: patch to finish it coming very soon; some good preparatory - refactoring done. -* ## 0.20P2Remove need for FrameView::forceLayoutParentViewIfNeeded in - SVG -* ## Owner: - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) -* ## Owner: fs@opera.com - ## Update: at risk. trchen is also helping with this one. - ## EOQ update: some promising prototyping, but a ways t go. -* ## 0.40P2Geometry code for layout and paint better-written and - documented -* ## Owners: - [blink-layout](https://easyokrs.googleplex.com/view/blink-layout/), - [szager](https://easyokrs.googleplex.com/view/szager/), - [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* ## - [#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) - [#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - ## Shared between the paint and layout teams. - ## Update: at risk. Plan in place for removing the Widget hierarchy, but not - much progress yet. - ## EOQ update: reworked flipped-block logic in - mapToVisualRectInAncestorSpace(); initial exploration to rework - Widget/FrameView trees; documentation of writing modes in layout/README.md - in flight. - -## 0.97Understand, maintain and improve performance -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) - -## Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* ## 1.00P1Measure performance and prevent any performance regressions - from reaching the stable channel -* ## Owner: [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* ## Mid-quarter update: on track. - ## EOQ: met -* ## 1.00P2Composited scrolling for low-DPI screens -* ## Owner: [schenney](https://easyokrs.googleplex.com/view/schenney/) -* ## Mid-quarter update: on track. Lots of progress. Should be able to - turn it on for M55. - ## EOQ: met -* ## 1.00P1Use compositor RTrees rather than cached SkPictures -* ## Owner: [wkorman](https://easyokrs.googleplex.com/view/wkorman/) -* ## Mid-quarter update: done! - ## EOQ: met -* ## 0.80Partial repaint telementry test implemented -* ## Mid-quarter update: at risk. No progress yet, work upcoming this - quarter. - ## EOQ: in code review. - -## 0.67Improve paint/compositing interfaces -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -## Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* ## 0.40P1New (SPv2) compositing integration works for scrolling and - non-mask effects -* ## Owners: - [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/), - [pdr](https://easyokrs.googleplex.com/view/pdr/), - [trchen](https://easyokrs.googleplex.com/view/trchen/) -* ## All scrolling (assuming root layer scrolls) and compositing tests - pass up to masking. - ## Mid-quarter update: on track for scrolling, at risk for effects. - ## EOQ update: scrolling almost done. No progress yet on effects. -* ## 1.00P1Paint invalidation tree walk within the pre-paint tree walk - fully implemented -* ## Owners: - [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/), - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* ## Mid-quarter update: done! - ## EOQ update: met -* ## 0.60P1GeometryMapper implements fast paint invalidation, paint - clip rects, and interest rects. -* ## Owner: [chrishtr](https://easyokrs.googleplex.com/view/chrishtr/) -* ## Mid-quarter update: on track. Lots of progress. - ## EOQ update: done for paint invalidation, CL almost done for paint clip - rects. Interest rests not yet done. - -## 0.58Finish cc property tree implementation -[#wp-performance](https://easyokrs.googleplex.com/search/?q=wp-performance) -[#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -## Owner: [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/) - -* ## 0.90P1Finish removing target knowledge from clip and transform - trees -* ## Owners: - [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/), - [weiliangc](https://easyokrs.googleplex.com/view/weiliangc/) -* ## Mid-quarter update: On track for transforms, at risk for clips. - Computation of transforms without in-tree target knowledge has been - implemented behind a flag; for clips, there are unit test failures - to sort out (where the "correct" answer isn't necessarily what the - test currently expects), and work is being transitioned to new - owners. - ## EOQ update: done for transforms (1.0), nearly done for clips (0.8), so - 0.9 overall. -* ## 0.40P1Cache dynamically-determined draw properties -* ## Owner: [sunxd](https://easyokrs.googleplex.com/view/sunxd/) -* ## Mid-quarter update: On track for transforms, at risk for clips. - Currently evaluating performance for transforms, but clips are - blocked on the previous KR. - ## EOQ update: nearly done for transforms (0.8) and not started for clips - (0) so 0.4 overall. -* ## 0.00P3(stretch) RenderSurface determination on the impl thread -* ## This depends on the previous two KRs being finished, but is not a - lot of additional effort. - ## Mid-quarter update: no progress. - ## EOQ update: not done - ## EOQ update: ? -* ## 0.60P1Stop requiring a cc::Layer for any property tree nodes -* ## Owners: [ajuma](https://easyokrs.googleplex.com/view/ajuma/), - [jaydasika](https://easyokrs.googleplex.com/view/jaydasika/) -* ## Mid-quarter update: On track. Most of the dependencies have been - removed. - ## EOQ update: Work for routing animation updates directly to property trees - is nearly done; most of the direct dependencies of render surfaces on owning - layers have been removed, but RSLL iteration still needs to be converted to - use layer lists and effect nodes. - -## 1.00New features - -* ## 1.00P2Support custom paint - [#wp-future](https://easyokrs.googleplex.com/search/?q=wp-future) -* ## Code reviews, design reviews, etc. - ## Mid-quarter update: on track. (nothing to do) - ## EOQ update: met -* ## 1.00P2Unprefix -webkit-clip-path - [#wp-predictability](https://easyokrs.googleplex.com/search/?q=wp-predictability) -* ## owner:fs@opera.com - ## Mid-quarter update: on track, code complete already. Sending an intent to - ship soon. - ## EOQ update: met - -## Code health [#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - -## Owner: [blink-layout](https://easyokrs.googleplex.com/view/blink-layout/) - -* ## P2Reduce life cycle violations -* ## Owners: [atotic](https://easyokrs.googleplex.com/view/atotic/), - [paint-dev](https://easyokrs.googleplex.com/view/paint-dev/), - [wangxianzhu](https://easyokrs.googleplex.com/view/wangxianzhu/) -* ## [#wp-health](https://easyokrs.googleplex.com/search/?q=wp-health) - ## Reduce life cycle violations in the rendering pipeline. - ## Shared between the paint and layout teams. - -## Q2 2016 - -Code health - -Owner: paint-dev - -* 0.50P2Reduce total open bugs by 2% -* Owners: chrishtr, junov, schenney -* Mid-quarter update: actual result is up by 1%. Wont Meet. - EOQ grading notes: actual is up by 1.8%. Score=0.6 for doing ok at fixing - bugs, but lots more bugs keep coming in via triage from other labels. -* 0.90P1Triage all legacy bugs, and triage all new bugs within a 1 - week SLA. Enforce priority 1 meaning. -* Mid-quarter update: triaging SLA is On Track. Priority 1 bug hygiene - Needs Work. - EOQ grading notes: we met the SLA almost every week. Blink>Compositing in - particular slipped a couple of times. -* 0.70P1Prevent any regressions from reaching the M51 or above stable - channel -* Mid-quarter update: M51 just went to stable, so no direct evidence - yet of success or failure. Therefore On Track. - EOQ notes: still not sure about M51. needs some bug digging. Tentative score - of 0.7 -* 0.66P2High-priority / most-starred bugs fixed -* Fix at least these: - <http://crbug.com/596382> - <http://crbug.com/521364> - <http://crbug.com/470669> - Mid-quarter update: 596382 is fixed (with followup to re-enable safely). The - other two bugs have some progress - but Need Work. - EOQ update: 596382 is fixed. 521364 is halfway done. 470669 is halfway done. - Final score: 0.66 (averaging). - -0.40P1Measure performance - -Owner: paint-dev - -* 0.00P1Implement a partial repaint Telemetry test -* <http://crbug.com/527189> - Mid-quarter update: no progress. Needs Work. - EOQ update: nothing done. -* 0.80P1Monitor UMA stats for paint, raster, paint invalidation and - compositing. Don't allow regressions into the stable channel. -* Owner: wkorman -* Mid-quarter update: monitoring is On Track, not allowing regressions - Needs Work. - EOQ update: Stats monitored on regular basis, no currently known stable - channel regressions M51 (may need more investigation to be 100% sure?) - -1.00Performance and complexity improvements - -Owner: paint-dev - -* 1.00P2Re-implement reflection using filters -* Owner: jbroman -* Launch by end of quarter - Mid-quarter update: implemented and pretty much working. On Track. - EOQ update: done, in M53. Score 1.0. -* 0.70P2Composite scrolling on low-DPI screens when possible -* Owner: schenney -* Launch by end of quarter. Tracked in crbug.com/381840 - Mid-quarter update: partially implemented. Need to fix bugs in current - implementation and commit it. Needs Work. - EOQ update: All the necessary work done to set the layer as composited, and - resulting Blink bugs fixed, but blocked on enabling background and - foreground painting into the same composited layer when the background is - opaque in order to actually get LCD text on the layer. -* 1.00P1New DOM-order-based paint invalidation tree walk -* Owner: wangxianzhu -* Launch by end of quarter - Mid-quarter update: finished on current PaintInvalidationState. Needs work - to migrate to PrePaintTreeWalk (PaintPropertyTreeBuilder). On Track. - EOQ update: Done. Score 1.0. - -P1Property trees / SPv2 plumbing - -Owners: paint-dev, pdr, trchen - -* 0.50P1Property trees in Blink are complete up to the deficiencies of - the paint artifact compositor. -* Owners: pdr, trchen -* Transform trees are complete (including backface visibility, - flattening, and transform-style). - Effect trees are complete (including reflection, clip-path, mask). - Root layer scrolling supported using unittests. - All of compositing/, fast/, svg/ passing or failing for known&labeled - reasons like paint artifact compositor deficiencies. - This includes multicolumn. - Implement the scroll tree. - Mid-quarter update: Needs Work. Some progress on transform tree semantics - and SVG clip paint properties, but a lot more work to do. - EOQ update: lots of measurable progress was made (transform edge-cases, - filter tree preparation, html and svg difficult cases) but we still fail a - significant number of tests (~3100/16728 of fast/ & compositing/ & svg/). -* 1.00P1All direct dependencies in cc on the cc::LayerImpl tree are - gone, replaced with property trees -* Owners: jaydasika, sunxd, vollick -* Mid-quarter update: On Track. Lots of great progress. - EOQ update: Done! -* 0.30P2RenderSurface determination is on the impl thread -* Owners: vollick, weiliangc -* Update render target info and draw properties after render surface - determination. - Mid-quarter update: Partial work. Rest blocked by target information still - on clip/transform tree. Wont Meet - EOQ update: blocked on other KRs, but also not done. -* 0.60P1Transformed layers can be sent as a layer list with property - trees, rather than a hierarchical layer tree -* Owners: ajuma, jbroman -* Mid-quarter update: progressing, with a partial implementation. On - Track. - EOQ update: blink-side: score 0.5 can do trivial translations with a layer - list (and trivial trees), but I'm still working on building non-trivial - ones. cc side: 1.0. Total: 0.5 (most work is in Blink) -* 0.40P2SPv2 paint invalidation is in place and works behind the - feature flag for SPv2 -* Owner: wangxianzhu -* Mid-quarter update: no progress yet. Needs Work. - EOQ update: Plumbed SPv2 paint invalidation onto spv1 paint invalidation and - it basically works, but it's still far from the goal of spv2 paint - invalidation. -* 0.50P1Remove target knowledge from Clip tree and Transform tree -* Owner: weiliangc -* Remove target_id and \*_in_target_space in Clip and Transform tree. - Remove main thread cc's use to to_target transform, use to_screen transform - instead (including visible rects calculation, sublayer scale, snapping) - Dynamically calculate draw properties with target info from Effect tree. - Blocks both Blink/cc API and RenderSurface determination on impl thread. - Mid-quarter update: Progressing. Needs Work. - EOQ update: progressing, but still needs plenty of work. -* 0.20P3Cache dynamically calculated draw properties -* Owner: weiliangc -* Blocked by Clip and Transform tree clean up and Render Surface - determination on impl thread. - Critical for performance, do not block API implementation. - Mid-quarter update: Still blocked by dynamic calculation. Wont Meet. - EOQ update: Only moved a small part of properties. - -1.00P2Support goals of other teams - -* 1.00Support custom paint -* Mid-quarter update: On Track. All custom paint patches are - committed. - EOQ update: Done. Score 1.0. -* 1.00Support Blink -> Chromium style change, and Onion Soup - cleanups -* Mid-quarter update: On Track. We're reviewing everything coming our - way. - EOQ update: Done. Score 1.0. - -0.40P1Geometry code improvements for performance, less redundancy, simplicity -and correctness - -Owner: paint-dev - -* 0.70P1RTrees used to optimize layer rasterization, instead of - SkPicture replay -* Owners: chrishtr, wkorman -* Mid-quarter update: down to about 12 failing layout tests, plus a - small unknown regression in raster time. On Track. - EOQ update: Close to landing for M53, work still underway on < 10 failing - layout tests. -* 0.40P2GeometryMapper implemented and used to implement features in - Blink -* Owners: chrishtr, wkorman -* 1. SPv2-compatible - 2. PaintLayerClipper - Mid-quarter update: prototype partial implementation of GeometryMapper in - progress. Needs Work. - EOQ update: First patch committed. Still plenty to do. Score 0.4. -* 1.00P1Partial raster for Blink launched -* Mid-quarter update: done, On Track. - EOQ update: On track. Score 1.0. - -0.30Improve SVG integration into the document lifecycle - -* 0.50P2SVG filter hack in FrameView is gone -* Ref: Document::hasSVGFilterElementsRequiringLayerUpdate - Owner: fs@opera.com - Mid-quarter update: some progress. Needs Work. - EOQ update: some progress, but not quite there. -* 0.10P2Remove need for FrameView::forceLayoutParentViewIfNeeded in - SVG -* Owner: fs@opera.com - Mid-quarter update: no real progress. Wont Meet. - EOQ update: some analysis performed, but no work yett - -## Q1 2016 - -Code health - -Owner: paint-dev - -* Reduce total open bugs by 5% -* Owners: chrishtr, junov, schenney -* Document all new features in Markdown and in the code, as we write - it -* Implement pixel capture on Cluster Telemetry -* Owner: pdr -* crbug.com/536285 -* Triage all legacy bugs, and triage all new bugs within a 1 week SLA -* Owners: chrishtr, junov, schenney - -Measure and improve performance - -Owner: paint-dev - -* Implement a partial repaint Telemetry test -* Owner: weiliangc -* crbug.com/527189 -* Improve performance of paint aggregated across Cluster Telemetry by - a total of 10% -* Owner: wangxianzhu -* Monitor existing UMA stats at the bi-weekly meeting -* Owner: wkorman - -Progress towards Slimming Paint v2 - -Owner: paint-dev - -* Move RenderSurface determination to the impl thread -* Owner: weiliangc -* Finish by M51 branch point -* Replace all direct dependencies in cc on the cc::LayerImpl tree with - property trees -* Owners: jaydasika, sunxd -* Finish by M51 -* Complete implementation of paint property trees -* Owners: pdr, trchen -* Passes most compositing/ layout tests. - Passes multicolumn tests. - Passes scrolling tests for the root frame. -* Implement a correct (but not yet performance-optimized) version of a - new Blink compositing integration -* Owner: jbroman -* Passes most compositing/ layout tests. - Passes multicolumn tests. - Passes scrolling tests for the root frame. - Passes video tests. -* Common implementation of property trees -* Owner: chrishtr -* Designdoc completed. Code implemented and working integration with - cc (may not yet be committed) -* Make use of RTrees to optimize layer rasterization, instead of - SkPicture replay -* Owner: wkorman -* Implement a SPv2-compatible paint invalidation tree walk -* (..that is integrated into the paint properties or paint tree walk) - -Support goals of other teams - -Owner: paint-dev - -* Support custom paint implementation -* Owner: chrishtr -* Support paint-related loading metrics -* Owner: chrishtr -* Investigate OOPIF to see if there are paint-related design problems - or bugs -* Owner: pdr -* Support conversion of Blink to Chromium style - -Code quality and cleanup - -Owner: paint-dev - -* Delete CDP -* Owner: weiliangc -* Delete selection gap code -* Owner: wkorman - -## Q4 2015 - -## Improve bug triage and fix rate (grade: 0.46) - -* ## This objective apples to the following labels: - Cr-Blink-Paint-Invalidation, Cr-Blink-Paint, Cr-Blink-Canvas, and - Cr-Blink-Compositing. - -* ## Reduce open bug count by 10% -* ## Triage 100% of all new bugs with a 1-week SLA -* ## Note: this goes along with a web-platform-wide OKR with the same - goal. -* ## Triage or re-triage 50% of all bugs filed before Q3 2015 -* ## Note: this goes along with a web-platform-wide OKR with the same - goal. -* ## Define and agree upon an ongoing triage process and standards for - the paint team -* ## This includes instructions on how to treat priority, Type, Cr - labels, etc. - -## <img alt="Revision History" -src="https://easyokrs.googleplex.com/images/history.png"><img alt="copy" -src="https://easyokrs.googleplex.com/images/copy.svg"> - -## Improve documentation of paint code (grade: 0.13) - -* ## Migrate all feature documentation on the sites page to Markdown - files -* ## Add Markdown files describing clearly major architectural pieces - of Paint -* ## This includes forward-looking documentation of the SPv2 - implementation, and important codebase-wide conventions. - -## Launch components of SlimmingPaintV2 (grade: 0.68) - -* ## All KRs below are met if they are done and launched in M49. - -* ## Launch SlimmingPaintSynchronizedPainting -* ## Launch SlimmingPaintSubsequenceCaching -* ## Launch SlimmingPaintOffsetCaching -* ## Launch compositor thread property trees -* ## Includes deleting all of CDP -* ## Launch removal of DisplayItemList->SkPicture replay -* ## Launch the cc effect tree - -## Implement the new compositing path for Slimming Paint v2 (grade: 0.2) - -* ## Implement the paint properties design -* ## crbug.com/537409 - ## Includes: paint properties tree walk, definition and generating of - property trees, and homogeneous DisplayItemList with just drawings. -* ## Implement layer compositing in Blink on top of paint properties - and paint chunks -* ## (Stretch) Implement squashing and overlap testing in the - compositor thread - -## canvas.toBlob, callback version of the API (grade: 0.8) - -* ## Have an async implementation that has its scheduling controlled - by Blink -* ## Refactor the png encoder integration into skia (SkCodec) in a way - that allows the workload to be divided into small units of work for - the purpose of Idle scheduling. -* ## Stress test should show that a long-running png image encode does - not interfere with a lightweight 60fps animation on a low spec - device (2 core CPU). -* ## (Stretch) Refactor JPEG and WebP encoder integrations into skia, - and pass the same test described above with these encoders. -* ## (Stretch) Ship it - -## ImageBitmap (grade: 0.94) - -* ## ImageBitmap is transferable to Workers -* ## ImageBitmaps can be created on Workers -* ## Calls to createImageBitmap always < 5ms for 1k-by-1k canvas on - Android One -* ## Async response always < 300ms for 1k-by1k canvas with no - animation running (network delays notwithstanding) on Android One -* ## (Stretch) Ship it - -## Ship Display List 2D canvas everywhere (grade: 0.7) - -* ## Use Display lists in cases where GPU-acceleration is available -* ## Google Sheets triggering display list mode on all platforms -* ## (Stretch) Google Sheets stays in display list mode while - scrolling the document - -## OffscreenCanvas feature implementation (grade: 0.35) - -* ## ImageBitmapRenderingContext capable of displaying an ImageBitmap - without making a copy of the image data -* ## OffscreenCanvas can be created -* ## (Stretch) 2D context can be created on an offscreen canvas -* ## (Stretch) Functional ImageBitmap flow: OffscreenCanvas on a - worker can transfer rendered content to an - ImageBitmapRenderingContext on main thread - -## Canvas product stability (grade: 0.40) - -* ## Eliminate all OOM crashes caused ImageData APIs -* ## Reduce by 50% 2D context losses caused by GPU context resets - -## Support work to start implementing custom paint (grade: 1.0) - -* ## Review code and designs for a new canvas rendering context - interface for custom paint -* ## (Stretch) Review code for implementation of custom paint -* ## The Houdini team does not expect to do any work along these lines - until December at the earliest. - -## Support work to define time-to-first paint (grade: 1.0) - -* ## This is an OKR to support work by the loading team to improve - time-to-first-paint metrics. Tracked in crbug.com/520410 - -## Improve telemetry testing of paint (grade: 0.0) - -* ## Add a telemetry test for incremental paint -* ## Tracked in crbug.com/527189. -* ## Add a telemetry benchmark to capture pixels -* ## This will allow us to run pixel diff tests on the top 10k sites - in Cluster Telemetry. Tracked in crbug.com/536285. - -## Q3 2015 - -Launch compositor thread property trees (grade: 0.5) - -* Tracked in crbug.com/481585 - -* CalcDrawProps not used at runtime -* Launch in Chrome <=47 -* Stretch: Delete CalcDrawProps and fix unit test dependencies -* There is a substantial amount of cleanup here, which we should not - block launch on. - -Major progress finishing implementation of Slimming Paint phase 2 (grade: 0.24) - -* Tracked in crbug.com/471333 - Fully achieving this OKR will be a stretch! - -* New Blink->cc API complete -* Tracked in crbug.com/481592 -* Implementation of basic layerization -* Tracked in crbug.com/472842 - \*Not\* included: smart code to only re-raster or re-build only the parts of - the layer tree that are needed. -* Implement "full" display lists in Blink -* Tracked in crbug.com/472782. Includes property trees, diff - representation, pixel refs interest rects and RTrees. -* LayoutObject-based invalidation - -Product excellence: improve bug triage and fix rate (grade: 0.6) - -* Triage all paint bugs (with label Cr-Blink-Paint or - Cr-Blink-Paint-Invalidation or paint-related compositor code) -* Reduce number of unfixed paint bugs by 10% - -Remove selection gap painting (grade: 0.40) - -* Implement representation of newlines in selection -* Tracked in crbug.com/474759 -* Remove selection gap painting, & resulting code cleanup - -Support implementation of stopping rAF / lifecycle for non-visible, cross-domain -iframes (grade: 1.0) - -* Tracked in crbug.com/487937. Primary implementation seems likely to - come from scheduler-dev. - -Implement OffscreenCanvas (grade: 0.13) - -* Synchronous mode of operation (using ImageBitmap) functional for 2D - contexts. -* Ship behind experimental flag in M47 - -Ship canvas filters (stretch) (grade: 0.38) - -* Can be used by Swiffy to improve efficiency of Flash->JS - conversion of Flash code that uses filters. - -* No longer experimental in M47 -* Optimized to apply filter only on the region of interest, in all - applicable use cases - -Refactor 2D canvas (grade: 0.9) - -* Remove >1000 lines of code by eliminating dependency on - SkDeferredCanvas and simplifying ImageBufferSurface -* Start using display lists for GPU-accelerated canvases by M47 - -Ship ImageBitmap (stretch) (grade: 0.15) - -* ImageBitmap no longer experimental -* ImageBitmap is transferable to workers -* ImageBitmap creation is truly async - -Accelerate the use of fonts in 2D canvas (grade: 1.0) - -* When font was previously used (cache hit), setting the 'font' - attribute should take < 1 microsecond on all platforms, for all - use cases - -## Q2 2015 - -Launch Slimming Paint phase 1 (grade: 0.9) - -* Tracked in crbug.com/471332 - -* Launched on all platforms, with no performance regressions -* Makes the Chrome 45 cut. - -Working implementation of Slimming Paint phase 2 (grade: 0.0) - -* Tracked in crbug.com/471333 - -* Complete implementation of display lists -* Complete crbug.com/472782 and crbug.com/471264. -* Implement a working version of layerization in the compositor -* Complete crbug.com/472842 -* Passing 90% of layout tests - -Launch property trees for all cc main-thread computation (grade: 1.0) - -* M45 or die - -* Launched on all platforms, with no performance regressions -* Complete crbug.com/386810 - -Design for Custom Paint (grade: 0.8) - -* Produce design document -* Shared with Paint team - (<https://easyokrs.googleplex.com/view/paint-dev/2015/q2/>). This - should specify the API, its integration into Blink, fully worked out - use cases, and an explanation of how it will benefit performance. -* Flesh out implementation on a branch - -Collaborators: blink-houdini, paint-dev - -## Q1 2015 - -Overall Score - -* Solid progress towards a well-implemented Phase 1 launch in Q2. - Phase 2 deliverables were way too aggressively stated. - -0.50Implement DisplayItemList backing of existing cc::layers - -* 0.60No performance regressions relative to prior system -* (Score comment: raster performance appears to match, but recording - is still 25% slower.) -* 0.00On by default in the Chrome Canary channel for at least the last - week of the quarter -* (Score comment: we didn't get this far.) -* 0.90Passes all layout tests -* (Score comment: almost all layout tests actually pass, though we - don't have all of them enabled yet.) - -0.43Use property trees for all cc main-thread computation - -* 0.00On by default in the Chrome Canary channel for at least one week - at the end of the quarter -* (Score comment: we didn't get there yet.) -* 0.30Finalized design of integration of property trees into display - list representation -* (Score comment: we have a design and partial implementation of - transform trees.) -* 1.00Passes all layout tests -* (Score comment: they all pass!) - -0.00Make all composited layer decisions in cc - -* Stretch: include DisplayItemList diffs from Blink -> cc - (Score comment: we didn't get there.) - -* 0.00Implement initial design behind a flag -* We didn't get there. -* 0.00Pass layout tests in the compositing/ directory -* We didn't get there. - -1.00Consider proposals for paint callbacks and decide whether to support -implementation - -* Paint callbacks are part of the "explain css" proposals that are - part of Glitter.) - (Score notes: we discussed with the Houdini team about it, and now have much - better clarity about its design and justification for ergonomics and - potential performance, along with a Q2 OKR to create a detailed design - document for the feature. - -0.70DevTools timeline invalidation tracking ready for UI review - -* (Score comment: implemented but not yet committed.)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/paint-team/paint-team-members/index.md b/chromium/docs/website/site/teams/paint-team/paint-team-members/index.md deleted file mode 100644 index 8c484e79c48..00000000000 --- a/chromium/docs/website/site/teams/paint-team/paint-team-members/index.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/paint-team - - Paint Team (paint-dev) -page_name: paint-team-members -title: Paint team members ---- - -Chris Harrelson (chrishtr@) TL - -Philip Rogers (pdr@) - -Walter Korman (wkorman@) - -Tien-Ren Chen (trchen@) - -Xianzhu Wang (wangxianzhu@) - -Stephen Chenney (schenney@) - -Weiliang Chen (weiliangc@) - -Canvas subteam: - -Justin Novosad (junov@) TL - -Ali Juma (ajuma@) - -Olivia Lai (xlai@) - -Xida Chen (xidachen@) - -Adjuncts: - -Fredrik Söderquist (fs@opera.com) - -Florin Malita (fmalita@)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/rendering/index.md b/chromium/docs/website/site/teams/rendering/index.md deleted file mode 100644 index bfd53978cae..00000000000 --- a/chromium/docs/website/site/teams/rendering/index.md +++ /dev/null @@ -1,440 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: rendering -title: Rendering Core ---- - -The rendering core team is a long-term engineering team that owns the overall -[rendering pipeline](/developers/the-rendering-critical-path) and most of the -core rendering stages. Specifically style, layout, compositing, and paint. The -team is also responsible for text, fonts, editing, canvas, images, hit testing, -and SVG. - -The team is made up of contributors from many different companies and see -regular contributions from many more as well as from individual contributors. - -Last updated: Thu Oct 29, 2019 by [Chris](mailto:chrishr@chromium.org) - -## Team Charter - -The rendering core team is focused on the architectural principles of -reliability, performance and extensibility of the core rendering technologies of -the web: HTML, DOM and CSS. We also make sure to satisfy top requests from -customers. Our primary customers are web developers and other teams within -Chrome which build features on top of rendering. - -## Priorities - -### Scalable Performance - -* Rendering update performance is proportional to the amount of - change, and “amount of change” has an intuitive explanation. -* Rendering performance of a component need not depend on where it's - put within a containing document, or the size of that document. -* Rendering performance of a document need not depend on the size of - components contained within it. -* Same goes for encapsulation - a component can be included without - breaking a containing page, and a containing page cannot break a - component. - -### Reliability - -* Rendering features work correctly and have rational, understandable - definitions. -* Rendering features work the same on all platforms, and on all - browsers. - -### Extensibility - -* Web developers can extend the capabilities of Rendering in novel - ways without performance or ergonomic penalties. -* Chromium developers can extend or embed the Rendering code in new - and novel ways without excessive effort or performance penalties. - -## Ongoing Projects - -List of ongoing major projects owned by the team or involving multiple team -members. - -* **CSS Containment** - Ongoing work to optimize performance isolation for CSS containment. -* **[LayoutNG](/blink/layoutng)**, issue - [591099](https://bugs.chromium.org/p/chromium/issues/detail?id=591099). - A new layout system for Blink designed with fragmentation, extensibility and - interruptibility in mind. - Phase 1 (block flow) launched in M77. - Further layout modes (tables, flexbox, grid) and block-fragmentation support - targeted for 2020. -* **[Composite After - Paint](https://docs.google.com/document/d/114ie7KJY3e850ZmGh4YfNq8Vq10jGrunZJpaG6trWsQ/view)** - (CAP), issue - [471333](https://bugs.chromium.org/p/chromium/issues/detail?id=471333). - Previously known as Slimming Paint v2. Project to re-implement the - Blink<->CC picture recording API to work in terms of a global display - list rather than a tree of cc::Layers. It will result in a drastic - simplification of the way that composited layers are represented in Blink - and cc, which in turn will yield improved performance, correctness and - flexibility. -* **src: local() matching**, issue - [627143](https://bugs.chromium.org/p/chromium/issues/detail?id=627143). - Font matching and IPC improvements to allow for spec compliant font matching - and improved web font performance. - -## Organization - -Team organization and communication. - -### Mailing lists - -We use a set of public mailing list for technical discussions, questions, and -announcements. Access is currently limited to subscribers but anyone may join by -posting to the relevant list or following the web archives links below. Once -subscribed the full historic archives are available. - -* [rendering-core-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/rendering-core-dev) - Primary list for the team. Used for non-technical and generic technical - discussions as well as for announcements. -* [dom-dev@chromium.org](mailto:dom-dev@chromium.org) -* DOM team-specific list for technical and standards discussions. -* [style-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/style-dev) - Style (CSS) specific list for technical and standards discussions. -* [layout-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/layout-dev) - Layout, text, and font specific list for technical and standards - discussions. -* [paint-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/paint-dev) - Paint, Compositing, and SVG specific list for technical and standards - discussions. Also see [this site](/teams/paint-team). - -### Weekly Meeting - -There is weekly meeting held over video conference on Mondays open to all team -members, the meeting notes of which are available below and sent out to the -public mailing list. If you're interested in participating please talk to -[Chris](mailto:chrishtr@chromium.org) and he'll share instructions. - -**Current schedule:** - -* Tuesday 10:00 PDT (13:00 EDT, 18:00 BST, 19:00 CEST; Wednesday 02:00 - JST, 03:00 AEST). - -Meeting notes are public and are sent to *rendering-core-dev*, they're also -available in this document: [Meeting -notes](https://docs.google.com/document/d/1J1E_cAAPVEuwTOEN7nCs8YcDAWclQboV4bfrMG8wBn4/edit?usp=sharing). - -### Slack - -There is also a set of dedicated slack channels for the team. For logistical -reasons these are limited to team members and collaborators. Please talk to one -of the team members and they'll get you added as needed. - -### IRC - -Many of the team members may also be found in the #chromium channel on freenode. - -## Team Members - -**Adenilson Cavalcanti** adenilson.cavalcanti - ARM San Jose - Performance - -Aleks Totic atotic - Google Mountain View Layout, Paint - -Anders Hartvoll Ruud andruud - Google Oslo - Style, Houdini - -Chris Harrelson (lead) chrishtr - Google - San Francisco - All areas - -David Baron - dbaron - Google Maryland (Remote) - Paint - -David Grogan - dgrogan Google San Francisco Layout, Tables, Flexbox - -Dominik Röttsches - drott Google Helsinki - Text, Fonts - -Fredrik Söderquist fs - Opera Linköping - SVG - -Frédéric Wang - fwang - Igalia Paris - Layout, MathML - -Ian Kilpatrick (lead) ikilpatrick - Google Mountain View - Layout - -Javier Fernandez jfernandez Igalia - A Coruña - Style, Layout, Grid - -Joey Arhar jarhar - Google San Francisco - DOM - -Kent Tamura tkent - Google Tokyo - Layout, Form controls - -Koji Ishii kojii - Google Tokyo - Layout, Text, Fonts - -Manuel Rego rego - Igalia Vigo - Layout, Grid - -Mason Freed (lead) masonf - Google San Francisco - DOM - -Morten Stenshorne mstensho - Google Oslo - Layout, Fragmentation, MultiCol - -Oriol Brufau obrufau - Igalia Barcelona - Style, Layout, Grid - -Philip Rogers pdr - Google San Francisco - Paint - -Richard Townsend richard.townsend - ARM San Jose - Layout, Performance - -Rob Buis rbuis - Igalia Hamburg - Layout, MathML - -Rune Lillesveen (lead) futhark - Google Oslo - Style - -Stefan Zager szager - Google San Francisco - Paint - -Steinar H. Gunderson sesse - Google Oslo - Style - -Stephen Chenney schenney - Google Atlanta - Paint - -Vladimir Levin vmpstr - Google Waterloo - Async - -Xianzhu Wang wangxianzhu - Google Mountain View - Paint - -Xiaocheng Hu xiaochengh - Google Mountain View - Style - -Yoshifumi Inoue yosin - Google Tokyo - Layout - -## Contributing - -If you're interested in getting involved and contributing to rendering there are -many ways you could help and we'd love to have you. These range from filing good -bug reports to creating test cases, reducing and triaging failures, fixing bugs -and implementing new functionality. - -Please see the chromium [getting involved](/getting-involved) guide for generic -advice and to help you get set up. - -A good way to get started is to fix an existing bug. Bug fixes tend to be -limited in scope, uncontroversial, and easy to evaluate. - -Going through the bug database to find a suitable bug is quite a daunting task -though. To make it a little easier we try to maintain a list of bugs that we -think are suitable starter bugs. Those bugs are marked with a *GoodFirstBug* -label. Use the following queries to see *GoodFirstBug* in the [style & -layout](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Component%3ABlink%3ECSS%2CBlink%3EFonts%2CBlink%3EFullscreen%2CBlink%3ELayout%2CBlink%3ETextAutosize+Hotlist%3DGoodFirstBug+&colspec=ID+Pri+M+Stars+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=tiles) -and [paint & -compositing](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Component%3ABlink%3EPaint%2CBlink%3ECanvas%2CBlink%3ECompositing%2CBlink%3ESVG%2CBlink%3EImage%2CBlink%3EHitTesting%2CBlink%3EGeometry+Hotlist%3DGoodFirstBug+&colspec=ID+Pri+M+Stars+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=tiles) -components respectively. -If you prefer, the following queries will show all open bugs in the respective -bucket: [style & -layout](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Component%3ABlink%3ECSS%2CBlink%3EFonts%2CBlink%3EFullscreen%2CBlink%3ELayout%2CBlink%3ETextAutosize&colspec=ID+Pri+M+Stars+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=tiles), -[paint & -compositing](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Component%3ABlink%3EPaint%2CBlink%3ECanvas%2CBlink%3ECompositing%2CBlink%3ESVG%2CBlink%3EImage%2CBlink%3EHitTesting%2CBlink%3EGeometry&colspec=ID+Pri+M+Stars+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=tiles). - -## Documentation - -For a high-level overview of the rendering pipeline please see the [Life of a -Pixel](https://www.youtube.com/watch?v=w8lm4GV7ahg) ([slide -deck](http://bit.ly/lifeofapixel)) talk that Steve Kobes gave a little while -ago. It gives a very good overview and explains how the different steps in the -pipeline work and interact with each other. - -For more in-depth documentation about specific rendering stages see the relevant -markdown files checked into the main source tree. The README.md file in each top -level directory is a good starting point. Some of the key documents are linked -below. - -* [renderer/core/css/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/core/css/README.md) -* [renderer/core/dom/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/core/dom/README.md) -* [renderer/core/layout/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/core/layout/README.md) -* [renderer/core/layout/ng/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/core/layout/ng/README.md) -* [renderer/core/paint/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/core/paint/README.md) -* [platform/graphics/paint/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/platform/graphics/paint/README.md) -* [platform/fonts/README.md](https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/renderer/platform/fonts/README.md) - -[Debugging Blink -objects](https://docs.google.com/document/d/1vgQY11pxRQUDAufxSsc2xKyQCKGPftZ5wZnjY2El4w8/edit#heading=h.8x8n9x5rkr0) - -[Debugging Firefox/Gecko -objects](https://docs.google.com/document/d/1TMckMPNHk_XGZJUCUQi8IW3rtr03-6LHs_4UGSG4H_M/edit) - -## Design Documents - -Each new feature and all major projects require a design document before the -implementation work may commence. These documents are updated during the -implementation phase and provides a detailed explanation of the feature or -project as well as the history and the motivation. - -Please add new design documents to the bottom of this list. Make sure they're -world readable and, if possible, grant comment privileges to -*edit-bug-access@chromium.org* rather than *Anyone with a chromium.org account* -as not all contributors have *chromium.org* accounts. - -* [LayoutUnit & Subpixel - Layout](https://trac.webkit.org/wiki/LayoutUnit) (2012) -* [Line Box float -> LayoutUnit transition - plan](https://docs.google.com/a/chromium.org/document/d/1fro9Drq78rYBwr6K9CPK-y0TDSVxlBuXl6A54XnKAyE/edit) - (2014) -* [Blink Coordinate - Spaces](/developers/design-documents/blink-coordinate-spaces) (2015) -* [Eliminating Simple - Text](/teams/layout-team/eliminating-simple-text) (2015) -* [LayoutObject Tree API - Proposal](https://docs.google.com/document/d/1qc5Ni-TfCyvTi6DWBQQ_S_MWJlViJ-ikMEr1FSL0hRc/) - (2015) -* [Using Zoom to Implement Device Scale - Factor](https://docs.google.com/document/d/1CZSCPzOYujdUMyChocwzOBPKxYAoTsEoezMye30Hdcs/) - (2015) -* [Unprefix CSS Writing - Modes](https://docs.google.com/document/d/1lGrcTSlKMDeOEKZbHqvdLnW_Soywn7oICci2ApBXB00/edit?usp=sharing) - (2015) -* [Slimming Paint](/blink/slimming-paint) (2016) -* [LayoutNG](https://docs.google.com/document/d/1uxbDh4uONFQOiGuiumlJBLGgO4KDWB8ZEkp7Rd47fw4/) - (2016) -* [Scroll Anchoring](http:////bit.ly/scroll-anchoring) (2016) -* [Shaper Driven Line - Breaking](https://docs.google.com/document/d/1eMTBKTnWEMDu00uS2p8Xj-l9Pk7Kf0q5y3FbcCrWYjU/) - (2016) -* [Hyphenation in - Blink](https://docs.google.com/document/d/1ZgMnNxYxvPJYMOeyxJs8MsfGMNFiDKrz64AySxlCzpk/edit?usp=sharing) - (2016) -* ["system-ui" generic font - family](https://docs.google.com/document/d/1BI0OiWRUvsBOuPxPlF5J-_xtUZ49eVDUEXZXoF32ZcM/edit?usp=sharing) - (2016) -* [Using ICU BiDi in - LayoutNG](https://docs.google.com/document/d/1GXtjMXE46IFDXUdzyUAY2_yzZ3tJoiuYPV15e5xtGeE/edit?usp=sharing) - (2016) -* [Root Layer - Scrolling](https://docs.google.com/document/d/137p-8FcnRh3C3KXi_x4-fK-SOgj5qOMgarjsqQOn5QQ/) - (2017) -* [Baseline in LayoutNG](/) (2017) -* [Offset Mapping between DOM/Canonical - Text](https://docs.google.com/document/d/1voI52vA1_UdaDxJ0QNzbXKeu4MQQcsgaCKdWyECvwq8/) - (2018) -* [IntersectionObserver](https://docs.google.com/document/d/1MWXTJhtvB7FvF3SrlOD7IwLMVyj5zx_0NLDWNe0qYmI/) - (2018) -* [Style Update - Roots](https://docs.google.com/document/d/1aMwREBUbPr-eE1_M4XuBGWZs3GuFrxWBr8f6o9-HaOs/) - (2018) -* [Caret Position Bidi - Affinity](https://docs.google.com/document/d/1SyryaZ304uxVgwW2Hf3gGnq4_h1QqT3Jz9h-etqud1o/) - (2018) -* [Style Memory - Improvements](https://docs.google.com/document/d/1cgtF8VVNGdXQmCdvOs34vLLA1bFWHPfZRZtm5nEY7bs) - (2018) -* [Paint Touch-Action - Rects](https://docs.google.com/document/d/1ksiqEPkDeDuI_l5HvWlq1MfzFyDxSnsNB8YXIaXa3sE/view) - (2018) -* [Blink-generated property trees - (BlinkGenPropertyTrees)](https://docs.google.com/document/u/1/d/17GKr2uIH2O5GthdTyvJpv1qZjoHYoLgrzvCkbCHoID4/) - (2019) -* [Unified ComputedStyle - Storage](https://docs.google.com/document/d/12c8MKqitZBdhSORSVJuQOrar-XdY8VERthLKAO7muUk/) - (2019) -* [Flat Tree Order Style - Recalc](https://docs.google.com/document/d/1tjKznu6K-B3TfRHxApsPYXYM7FyIXg9Xg2wWcOmStNU) - (2019) -* [StyleResolver - Cascade](https://docs.google.com/document/d/1HrmPmcQBTUMouqQQG3Kww43I5aFW9-Q9tr-DEKZk09I) - (2019) -* [Skip Forced Style Update on Parsing - Finished](https://docs.google.com/document/d/1KdMCXjHP6ynCV2vP84mJIBmnWPS5y99uDq7Fed3ogQA/edit#heading=h.v9as6odlrky3) - (2019) -* [Paint Non-fast Scrollable - Regions](https://docs.google.com/document/d/1IyYJ6bVF7KZq96b_s5NrAzGtVoBXn_LQnya9y4yT3iw/view) - (2019) -* [LayoutNG block - fragmentation](https://docs.google.com/document/d/1EJOdFesZKspvrU7uWtGl-8ab2jIrzRF6NKJhwYOs6hU/) - (2019) -* [Moving out from - NGPaintFragment](https://docs.google.com/document/d/1O6u2BWhvjsT_dkqQZPftmqZ-qgBqxGlA2ZyLh_xBpgQ/edit?usp=sharing) - (2019) -* [NGFragmentItem](https://docs.google.com/document/d/10vJ6wdyEdeGkmcotKBZ9h3YtDzw5FIpDksa8rCHVFuM/) - (2019) -* [CSS min/max](http://bit.ly/31Yfkm6) (2019) -* [MathML](https://docs.google.com/document/d/1biGEaWN8ThNTDtAbT1M5GIf6N5uQLWdxh2QhrG9uN5c/edit) - (2019) -* [@font-face Loading and Full Document Style - Invalidation](http://bit.ly/35JjPmq) (2020) -* [Jankless ‘font-display: optional’](https://bit.ly/36E8UKB) (2020) -* [Reduce MediaQuery RuleSet - changes](https://docs.google.com/document/d/1TMqAq4k3aTHNH1m2sYoj-5QAndNmEXLI1QeD-oQ7jWE/edit#heading=h.6kknmf22ixwc) - (2020) -* [FastBorderRadius](https://docs.google.com/document/d/1bYuKa_X9faxHTs6B5OjE4n92ytP8CrEToeuBE4Mr7hI/edit) - (2019/2020) -* [Improving UKM Client - Counts](https://docs.google.com/document/d/1P49GrDe3mDDV9Q1yUm27ioWE4m1_Zz1FwRwVwGQh-ZI/edit?usp=sharing) - (2020) -* [Ensuring Rendering of Sub-pixel - Borders](https://docs.google.com/document/d/1fAYkOFxp2Luh6OOoXxtwOehmvNRGNss58ibQtVXL0Tw/edit?usp=sharing) - (2020) -* [Metrics for HTML - Parsing](https://docs.google.com/document/d/1zWlnQELDePFJBz105RgjjgPCkDN7quiVOHSWzNMf-DU/edit?usp=sharing) - (2020) -* [Improving Tracking of Web Test - Changes](https://docs.google.com/document/d/1SCKmT1S7HmoaZFYThqXiqrQJvQPikUfV6mwwXbW7Bk4/edit?usp=sharing) - (2020) -* [Dependency-Aware - MatchedPropertiesCache](https://docs.google.com/document/d/1uJSpTD9mAgFGljMaQzTvjFKzsvAv1yRJ15M0ZPzAVbo) - (2020) -* [Tree-scoped names in - CSS](https://docs.google.com/document/d/1NY1GmSeAhpYMdZ2Jd581aT-Dr3DDIb8-pc5YGiBTm5E/) - (2020) -* [Base background for - color-scheme](https://docs.google.com/document/d/1yTsrWTf5qWS7rVytSunSBEXrVO_j5gYu7xlzFsPENxk/) - (2020) -* [Interleaved Style and - Layout](https://docs.google.com/document/d/1mpN2I0KYVmIoB8LfSV3pzPAoqGBIrubybHPzrhc2dxA) - (2020) -* [Resolving Container - Queries](https://docs.google.com/document/d/17pymtoSq1WIP6mSQj-fSPU_3EdeB0AfjdTq38bYW574) - (2020) -* [SVG Text - NG](https://docs.google.com/document/d/1GOPKXsAMyKBCcTlByEwGHdu6QuG6YTd_mDwOX8z9S2c/edit?usp=sharing) - (2021) - -Presentations - -* [Display - Locking](https://docs.google.com/presentation/d/12IOGoBZS5kSX6CYb01904ZKuMhjKS2Q6O-hx9jTmvA8/edit#slide=id.p) - (vmpstr, Jan 2020) -* [Font - performance](https://docs.google.com/presentation/d/123_mQWrDoNbpMQ4bXiHaJT_lli-Vy2DLY8aRp1aC2jU/edit#slide=id.p) - (xiaochengh, Feb 2020) -* [Canvas](https://docs.google.com/presentation/d/12nR0gKSynGIfmeT5iIEU9LOg-4nXe8xgQ9Q8VAFqL8w/edit) - (fserb, Feb 2020) -* [Compositing - memory](https://docs.google.com/presentation/d/1_8PLdXVUPclq7aiWnTU7UES43NMjaUnRBbQYypmqrQQ/edit#slide=id.p) - (pdr, Feb 2020) -* [Portals](https://docs.google.com/presentation/d/1UYQe9jOysS2zX1yyiqP-LOxJdo-elC0grP-xUbVBtxY/edit?usp=sharing) - (lfg, Feb 2020) -* [FlexNG](https://docs.google.com/presentation/d/10e7bnBrkpNJj8aQXiofCJCslWpPtlxZyt7wZIw9NQrg/edit) - (dgrogan, Mar 2020) -* [Scrolling](https://docs.google.com/presentation/d/1cQZLTKzUWD2O0fUQhwaL4DbRckPPNiOjDqwfPYQzoDc/edit?usp=sharing) - (samfort@microsoft, Mar 2020) - -Google-internal design documents (aim is to migrate them to the list above; on -request we can try to make part/all public) - -[Font Matching by Full Font -Name](https://docs.google.com/document/d/1yCZwVIF39S8WOgCUraT5OuUUaLSqWrxoG3mqdtnHnhs/edit#) -(2019) - -## Bug & Triage Policy - -The rendering core team is responsible for all bugs for the components listed -below, including sub-components . Our policy is that all new bugs are to be -triaged within a week of being filed and all P-0 and P-1 bugs are to be fixed in -time for the next release. Failures to meet the policy is tracked in our weekly -meeting and shared as part of the meeting notes - -### Policy - -1. Triage all bugs within 7 days. -2. Fix P0 bugs within 15 days. -3. Fix P1 regression bugs within 15 days. -4. Re-triage all bugs every 365 days. - -### Links - -* [Tracking - Spreadsheet](https://docs.google.com/spreadsheets/d/1mQ4b1cpy78wFKahKfzJl-4LUYeygAHyGaMGoZKnD_0U/) -* [Process & - Metrics](https://docs.google.com/document/d/1KncD2BSs9YnPt90DHSkoxttxyvG3yT79_9MXyMWN1Ok/edit#heading=h.mlb5a7a4vqj0) -* [Test - Flakiness](https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests) -* [Working with release branches](/developers/how-tos/drover) - -## Related Teams - -* [Input](/teams/input-dev) -* [Animations](/teams/animations)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/rendering/okrs/2020-q1/index.md b/chromium/docs/website/site/teams/rendering/okrs/2020-q1/index.md deleted file mode 100644 index 4fb26cc0885..00000000000 --- a/chromium/docs/website/site/teams/rendering/okrs/2020-q1/index.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/rendering - - Rendering Core -- - /teams/rendering/okrs - - OKRs -page_name: 2020-q1 -title: 2020-q1 OKRs ---- - -* Avoid double rendering and layout shift for ‘font-display: - optional’. crbug.com/1040632 - * EOQ score: 0.7 -* Reduce style invalidation/recalc on @font-face loading. Ship - improvements in M82. crbug.com/441925 - * EOQ score: 0.8 -* Fix remaining test failures for BlockHTMLParserOnStyleSheets. - crbug.com/891767. - * EOQ score: 0.95 -* Prototype relaxing parser yielding heuristics. crbug.com/1041006 - * EOQ score: 0.95 -* Add UMA metrics for cumulative parsing time, broken down by C++ and - JS, and cumulative amount of time spent hit testing or - forced-layout-ing before FCP - * EOQ score: 0.95 -* Experimentally determine impact of compositing cross-origin iframes. - Use results to decide next steps for isInputPending and Multiple - Blink Isolates - * EOQ score: 0.7 -* Add UMA and UKM for shaper font stack traversal depth. - crbug.com/1045571 - * EOQ score: 0 -* Decide whether we can ship prefer-compositing-to-lcd-text. - crbug.com/984346 - * EOQ score: 0.5 -* Support directly composited images with CompositeAfterPaint. - crbug.com/875110 - * EOQ score: 0.8 -* Ship smarter RuleSet media query invalidation in M83. Fix issues - 1014920 and 589083 - * EOQ score: 1 -* Fix all remaining test failures when CompositeAfterPaint is on. This - includes the remaining paint-related. crbug.com/471333 - * EOQ score: 0.7 -* Improve perf of subsequence caching, removing CompositeAfterPaint - paint regression. crbug.com/917911 - * EOQ score: 0 -* Add support to IntersectionObserver for clipping an explicit root. - crbug.com/1015183 - * EOQ score: 1 -* Reduce failures to zero for FragmentItem. crbug.com/982194 - * EOQ score: 1 -* Enable LayoutNG for form controls. crbug.com/1040826, - crbug.com/1040828 - * EOQ score: 0.7 -* Implement and ship PaintArtifactSquashing in M83. Fix - https://crbug.com/548184. - * EOQ score: 0.5 -* Ship text-decoration-width & text-underline-offset in M83. - crbug.com/785230 - * EOQ score: 0.1 -* Remove all DisableCompositingQueryAsserts for CompositeAfterPaint. - crbug.com/1007989 - * EOQ score: 0.6 -* Compute correct wheel event handler regions for cc. - crbug.com/841364. - * EOQ score: 0 -* Fix Mac OS 10.15 system font narrow rendering regression, ship to - M81. crbug.com/1013130 - * EOQ score: 0.8 -* Reliable layout testing for new Mac OS versions, fonts tests - rebaselined for 10.14 bot. crbug.com/1028242 - * EOQ score: 1 -* Ship plan to navigate in M82. crbug.com/1013385 - * EOQ score: 0.9 -* Refactor of the line-breaking logic to allow breaking after spaces -* Change CSS transform implementation and spec to match Firefox's - implementation. crbug.com/1008483 - * EOQ score: 0.25 -* Spec ink overflow concept for IntersectionObserver. - crbug.com/1045596 - * EOQ score: 0 -* GridNG: design doc, commits landed. crbug.com/1045599 - * EOQ score: 0.1 -* Ship Root element compositing changes in M81 - * EOQ score: 1 -* Ship Style Cascade project in M82. crbug.com//947004 - * EOQ score: 1 -* Ship color-scheme CSS property and meta tag in M81 - * EOQ score: 1 -* Ship selector() for @supports. crbug.com/979041 - * EOQ score: 1 -* Ship ::marker pseudo element.crbug.com/457718 - * EOQ score: 0.9 -* Implement and ship imperative slotting API in M83. crbug.com/869308 - * EOQ score: 0. -* Declarative shadow DOM. crbug.com/1042130 - * EOQ score: 0.9 -* Form Controls Refresh - * EOQ score: 0.75 -* TablesNG. crbug.com/958381 - * EOQ score: 0.75 -* FlexNG. crbug.com/845235 - * EOQ score: 1 -* FragmentationNG. crbug.com/829028 - * EOQ score: 0.7 -* Ship contain-intrinsic-size CSS property in M82. crbug.com/991096 - * EOQ score: 1 -* Ship render-subtree: invisible & render-subtree: invisible - skip-activation in M82 - * EOQ score: 0.5 -* Origin Trial for render-subtree: skip-viewport-activation and - activation event in M82 - * EOQ score: 0.5 -* Bug, triage, stars metrics - * EOQ score: 0.4 -* Ship pixel-snapped ResizeObserver rects for Canvas - * EOQ score: 0.5 -* Prototype composited clip path animations. crbug.com/686074 - * EOQ score: 0 -* Ship @property in M82. crbug.com/973830 - * EOQ score: 0.1 -* Ship multiple parts in ::part() in M82 - * EOQ score: 1 -* Fix font cache lifecycle, runaway font memory consumption during - animation, stable variable font animations without OOM in M82. - crbug.com/1045667 - * EOQ score: 0.8 -* Ship minimal named pages support in M83 - * EOQ score: 0.5 -* Prototype aspect-ratio CSS property. Partner with AMP and - render-subtree project on use-cases. crbug.com/1045668 - * EOQ score: 0.6 -* Ship CSS filters on SVG. crbug.com/109224 - * EOQ score: 0.6 -* Ship clip-path etc via external SVG resource. crbug.com/109212 - * EOQ score: 0.6 -* Ship ‘revert’ keyword. crbug.com/579788 - * EOQ score: 0.9 -* Incremental progress implementing custom Layout API. - crbug.com/726125 - * EOQ score: 1 -* Implement flexbox row-gap and column-gap in legacy and NG. - crbug.com/762679 - * EOQ score: 0.1 -* Investigate possible APIs and solutions to container queries - * EOQ score: 0.1 -* Implement input.rawValue prototype, and send Intent-to-Prototype. - crbug.com/1043288 - * EOQ score: 0.75 -* Finish CSS Scoping study. Finish the “problem statement” document, - the “proposals” document, and gather feedback on both. - crbug.com/1045645 - * EOQ score: 0.7
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/rendering/okrs/2020-q2/index.md b/chromium/docs/website/site/teams/rendering/okrs/2020-q2/index.md deleted file mode 100644 index be5e7cb98eb..00000000000 --- a/chromium/docs/website/site/teams/rendering/okrs/2020-q2/index.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/rendering - - Rendering Core -- - /teams/rendering/okrs - - OKRs -page_name: 2020-q2 -title: 2020-q2 OKRs ---- - -* Avoid double rendering and layout shift for ‘font-display: - optional’. crbug.com/1040632 -* Reduce invalidation/recalc on @font-face loading. Ship improvements - in M83. crbug.com/441925 -* Ship BlockHTMLParserOnStyleSheets. crbug.com/891767 -* Try to relax parser yielding heuristics. crbug.com/1041006 -* Find out why PaintHolding is faster. crbug.com/1069799 -* Add Tests for Input-Suppression. https://crbug.com/1001189, https:// - crbug.com/1014110 -* Align default font timeouts with LCP goal. crbug.com/1065508 -* Optimize stylesheet RuleSet invalidation. crbug.com/1065381 -* Composited clip path animations. crbug.com/686074 -* Remove DisableCompositingQueryAsserts for CompositeAfterPaint. - crbug.com/1007989 -* Land directly composited images with CompositeAfterPaint. - crbug.com/875110 -* Decide whether we can ship prefer-compositing-to-lcd-text. - crbug.com/984346 -* On-track to launch AssumeOverlapAfterFixedOrStickyPosition in M84. - crbug.com/752756 -* CompositeAfterPaint: fix all remaining test failures. - crbug.com/471333 -* MatchedPropertiesCache optimizations. crbug.com/1057072 -* Understand post-load friction metrics for style. -* Independent inheritance for custom properties. crbug.com/1056209 -* Fix font cache lifecycle, runaway font memory consumption during - animation. -* Reliable measurement of shaper font stack traversal depth -* Use experiment to determine impact of compositing cross-origin - iframes. https://crbug.com/1062432, https://crbug.com/1060452 -* Optimize imperative slot distribution algorithm for adding slots. - crbug.com/985652 -* Ship FragmentItem. crbug.com/982194 -* Compute correct wheel event handler regions for cc. crbug.com/841364 -* Complete implementation of plan to navigate. crbug.com/1053679 -* Get consensus on unifying <select> popup on Mac and non-Mac. - crbug.com/1009905, and crbug.com/422960 -* Web Components v0 Removal -* Get resolution on ::part() and :state() syntax -* TablesNG. crbug.com/958381 -* Grid refactoring -* Move 6 cc::Layer setters post-paint. crbug.com/1069546 -* Turn on use-zoom-for-dsf by default on MacOS. crbug.com/716231 -* Spec ink overflow -* Adopt Gecko semantics for 3D CSS rendering. crbug.cm/1008483. -* Remove @import support from CSSStyleSheet.replace() and - replaceSync(). crbug.com/1055943 -* EditingNG. crbug.com/707656 -* FlexNG. crbug.com/845235 -* Fix Mac OS 10.15 system font rendering regression. crbug.com/1057654 -* Ship imperative slotting. crbug.com/869308 -* Declarative shadow DOM. crbug.com/1042130 -* Form Controls Refresh. crbug.com/1042127, crbug.com/1051552 -* Form Controls Refresh Android / Dark Mode. crbug.com/970285 -* Implement and ship beforematch. eventcrbug.com/1055002 -* More stylable form controls -* Constructable stylesheets -* AdoptedStyleSheets use ObservableArray -* Spec and implement cross-tree-scope handling of @-rules. - https://github.com/w3c/csswg-drafts/issues/1995 -* Ship @property. crbug.com/973830 -* attr(). crbug.com/246571 -* Ship ::marker pseudo element. crbug.com/457718 -* RubyNG. crbug.com/1069817 -* Custom state pseudo class -* FragmentationNG. crbug.com/829028 -* Ship minimal named pages support, plus page-orientation descriptor. - crbug.com/1053768 -* Aspect-ratio layout. crbug.com/1045668 -* Review and design collaboration for Font Enumeration and Table - Access -* Implement and ship to Beta text-decoration-width & - text-underline-offset (+ support MVAR variable font underline - metrics) -* Prototype usage and content rendering of COLR-gradient font -* Improve text quality by using more LCD text. crbug.com/642885 -* Ship CSS filters for SVG. crbug.com/109224Ship clip-path, filter, - mask, etc via external SVG resource. crbug.com/109212 -* Implement ParentNode.prototype.replaceChildren. crbug.com/1067384 -* Other things for frameworks. Re-parenting iframes? -* Resolve whether to implement or drop input.rawValue. - crbug.com/1043288 -* Get public feedback on CSS Scoping proposal. -* Unify StyleForElement and PseudoStyleForElement -* LayoutNG ratio metrics. crbug.com/1067527 -* Easier usage of Noto Color Emoji on Linux. crbug.com/767754 -* Reduce paint test flakiness by 50%
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/rendering/okrs/index.md b/chromium/docs/website/site/teams/rendering/okrs/index.md deleted file mode 100644 index 61521e8f115..00000000000 --- a/chromium/docs/website/site/teams/rendering/okrs/index.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -- - /teams/rendering - - Rendering Core -page_name: okrs -title: OKRs ---- - -[Q1 2020](/teams/rendering/okrs/2020-q1)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/speed-metrics-team/index.md b/chromium/docs/website/site/teams/speed-metrics-team/index.md deleted file mode 100644 index 9c8d068f746..00000000000 --- a/chromium/docs/website/site/teams/speed-metrics-team/index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: speed-metrics-team -title: Speed Metrics Team ---- - -## Our site has moved to <https://chromium.googlesource.com/chromium/src/+/HEAD/docs/speed_metrics/README.md>
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/style-team/index.md b/chromium/docs/website/site/teams/style-team/index.md deleted file mode 100644 index b42d5a5e36c..00000000000 --- a/chromium/docs/website/site/teams/style-team/index.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: style-team -title: Style Team ---- - -The style team has been subsumed into the new [rendering -core](//chromium.org/teams/rendering) team. Please see the rendering core page -for details about ongoing style work. -This page is preserved for posterity and will no longer be updated. - -Primary contacts: meade@chromium.org, suzyh@chromium.org - -## Team Charter - -The Style team is a group of engineers, working at Google (Sydney and Tokyo), -Opera (Oslo) and Samsung. We are tasked with improving the style engine in -Blink. Our responsibility is to maintain and improve style resolution and -application (core/css/resolver, core/style), as well as the other parts of CSS -(core/css). -The Style Team triages bugs with the components Blink>CSS. - -## 2017 Goals - -* Explore and improve performance predictability -* Refactor style engine to be more feature oriented -* Ship CSS Typed OM -* Improve interoperability of Web Animations with Mozilla - -## Eternal goals - -* Maintain ‘code health’ by improving and optimizing style components - (CH). -* Maintain ‘feature health’ (FH). - * Interface with the rendering steering team to help decide - whether to either accept and implement, or reject proposed CSS - features. -* Triage CSS issues as they arise (and eliminate the - [backlog](https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DBlink-CSS+&colspec=ID+Pri+M+Week+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=tiles)). -* Maintain existing features as necessary. -* Improve knowledge of feature usage and deprecate rare and expensive - feature. - -**Team members** - -meade@chromium.org, suzyh@chromium.org (TLs and OWNERs) -alancutter@chromium.org (OWNER) - -bugsnash@chromium.org, shend@chromium.org, nainar@chromium.org, -jiameng@chromium.org, ericwilligers@chromium.org, rjwright@chromium.org - -**Links** - -[Docs](http://blink.style/docs) - -[CL best -practices](https://docs.google.com/document/d/1Zk3y699NTmH96qEDvofiUHbTckHJbkT8t3vY6ker3z0/edit?ts=590a6e7b#) - -Last updated: May 2017
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/web-capabilities-fugu/index.md b/chromium/docs/website/site/teams/web-capabilities-fugu/index.md deleted file mode 100644 index fe47edb9a01..00000000000 --- a/chromium/docs/website/site/teams/web-capabilities-fugu/index.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: web-capabilities-fugu -title: "Web Capabilities (Project Fugu \U0001F421)" ---- - -**Overview** - -Project Fugu 🐡 is an effort to close gaps in the web's capabilities enabling new -classes of applications to run on the web. The developer-friendly landing page -of the project is <https://web.dev/fugu-status/>. The list of in-process APIs is -available at <https://goo.gle/fugu-api-tracker>. -APIs that Project Fugu is delivering enable new experiences on the web while -preserving the web's core benefits of security, low-friction, and cross-platform -delivery. All Project Fugu API proposals are made in the open and on the -standards track. -Fugu is organized as Chromium project, open to all Chromium contributors and -organizations. Today, that includes Microsoft, Intel, Samsung, and Google (among -others). Fugu Leads triage incoming requests from partners, determine demand, -prioritize them, find champions, track development, and help organize the -release and documentation for the capability. - -#### Bridging the native app gap (Chrome Dev Summit 2019) - -**Contacts** - -Mailing List: -[fugu-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/fugu-dev) - -Slack Channel: #fugu on [@chromium](https://chromiumdev.slack.com/) - -**Capability Process** - -[Guideline and -template](https://docs.google.com/document/d/1kzNch5P6lLcHm2ER7YOCJQG4OGY4XttJ42FDn-2vdO0/edit#heading=h.hsplb8xxfif5): -This is the guideline and template to be used by Chrome developers who are about -to introduce a new capability. It outlines the process and when to reach out to -specific people. - -[DevRel Process for Fugu -Capabilities](https://docs.google.com/document/d/1qy-XmiCIu6QP1bbEAqfCAZQ65q5F9I6OJKvUgYLQ4GU/edit#): -A guide on how we will approach Fugu capabilities, including how we gather -developer demand, externalize our steps, and generate blog posts / tutorials. - -[Developer Updates Status -page](https://developers.google.com/web/updates/capabilities): Public list -showing the status of current capabilities. - -**Specific Capabilities & Prioritization model** - -We prioritize capabilities by which partners we enable or improve by a given -capability. - -[Full list of -capabilities](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=proj-fugu&sort=pri&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids): -Every capability that is currently considered as part of Fugu - -[Bug Tracking -Process](https://docs.google.com/document/d/1bAcLkqbEQJEphmjvnguB7WxltT_zEEXrUlwawpbrCNQ/edit?usp=sharing): -Information on how we track bugs & partners through crbug, as well as the -meaning of different labels - -**Monthly Meetings** - -To share updates on capabilities work and discuss opportunities and priorities, -we have monthly video chat meetings. The meetings are open to all Chromium -contributors working on Fugu capabilities, regardless of affiliation. Note that -these meetings tend to be high level, and don't dive into technical details. For -an invite to the meeting ask on the #fugu channel on chromium.slack.com or email -fugu-dev@chromium.org. Agendas for upcoming meetings and notes for past meetings -are captured in a shared [Notes -Doc](https://docs.google.com/document/d/1vC2IRBel2PIahJLE1Mrnd4nm0OMvWDQcKUQSsfxMFBY/edit#)
\ No newline at end of file diff --git a/chromium/docs/website/site/teams/worker-team/index.md b/chromium/docs/website/site/teams/worker-team/index.md deleted file mode 100644 index 8359b444db2..00000000000 --- a/chromium/docs/website/site/teams/worker-team/index.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: worker-team -title: Worker Team ---- - -The Blink Worker team works on Worker Threads in Blink, including [Service -Worker](/blink/serviceworker), Shared Worker, and Dedicated Worker. - -**Charter** - -Our team's responsibility is to own, evolve and maintain -(Dedicated/Shared/Service)Worker and Worklet infrastructure: - -* core/workers/\* -* modules/serviceworker/\* -* content/\*/\*worker\* - -**Docs** - -* [Web Workers in Blink (Google - Doc)](https://docs.google.com/document/d/1i3IA3TG00rpQ7MKlpNFYUF6EfLcV01_Cv3IYG_DjF7M/edit#heading=h.7smox3ra3f6n) -* [Service Workers: deep dive (BlinkOn4 - slides)](https://docs.google.com/presentation/d/15bHnAocAoSxYJAsF5JET34zMbzlxkc_NKGmP9BamqsM/edit#slide=id.g9e4def4c1_0_35) - -**Mailing list** - -worker-dev@chromium.org
\ No newline at end of file |