Chrome+Polymer bi-weekly sync notes, 2/2/2016
Dan Beam
2 February
Polymer team going to SYD
Will meet up with History team, hopefully help avoid mistakes earlier
Meeting with CSS variable folks for Blink
CSS Variables
Polymer shims it all -- regex
Looking into using Polymer 2.0 as a chance to remove shims
Maybe package shims separately…
Polymer compilation
Would like to have Chrome & Polymer use the same flags
dbeam@ spending hours getting things to compile over past day
Can we make Polymer’s flags stricter?
tjsavage@ looking into stricter release process for elements
AI: tjsavage -- include stricter compilation tests in Polymer component process guides
Polymer + readability
Polymer updates
Inheritance coming -- backpedals on composition > inheritance argument
Polymer future
Align with native webcomponents
Probably some performance benefits from not needing certain systems
Slots instead of content selection
Make elements simpler
Re-layering of Polymer
With 1.0, had micro/mini/standard; micro/mini aren’t very used
Looking at 2 layers: super-light layer for custom element syntactic sugar, then full Polymer with databinding
Automate a lot of changes with polyup tool
Webanimations.js polyfill for Chrome
Can we drop it?
Believe it’s shipped already
AI: dbeam -- talk to Shane Stephens (update: crbug.com/584126)
Performance testing
Settings was looking into Telemetry; changed plan
Added UMA logs for old/new settings page
New tracing based thing
SYD team helping Polymer with ability to inspect traces