wg-performance Status Update 2022-02-28

[erwinmombay]

cc @ampproject/wg-performance

What was accomplished

Lessons Learned

What's Next

[samouri]

What was accomplished

• 🐛 compiler.js buildDoms: ensure behavior matches browser amphtml#37671
• [in progress] Storage: fix clear and removeItem worker-dom#1136
• amp-script: warn with zero width or height amphtml#37747
• build fix: build-system types amphtml#37694

[erwinmombay]

What was accomplished

• launched inlining of CSS for amp-stories
• increased amp-geo ssr experiment proportion
• fix normalization of amp-geo related classes
• perf

Lessons Learned

What's Next

• amp e2e use mjs files
• inline amp-story translations strings as part of an experiment

[jridgewell]

What was accomplished

• Sourcemaps
  • Switch to trace-mapping package error-tracker#138
  • Fix build for windows amphtml#37660
  • Include sourcesContent while running tests amphtml#37720
  • Avoid sourcesContent when remapping esbuild output amphtml#37725
  • Fix infinite recursion when merge sourcemaps babel/babel#14274
  • Fix merging sourcemaps on Windows babel/babel#14282
• TAP Fixes
  • cl/429585083
  • cl/429628720
  • cl/429643044
• Perf

Lessons Learned

What's Next

[alexnj]

What was accomplished

• Mostly reading about perf, perf itself, and catching up on GTI training backlog.

Lessons Learned

• Chrome is working on a new script attribute that blocks only rendering and frees up document parsing.

What's Next

• Prepare a deck for W3PerfWG presentation of Client A/B.
• Pursue the block="rendering" script attribute spec details and its potential usage for Client A/B script deployment.
• Move parts of document at go/client-ab to open source repository prior to W3 meeting.