Engineer @ Google working on web tooling: Headless Chrome, Puppeteer, Lighthouse
ReportingObserver gives developers insight into what their code is doing in the wild. ReportingObserver surfaces information on issues like deprecations and interventions, messages that were previously only available in the DevTools console.
Feature Policy allows developers to selectively enable, disable, and modify the behavior of certain APIs and features in the browser. It's like CSP, but for features! Shipped in Chrome 60.
This article shows how to run headless Chrome and Puppeteer as part of your web server to "SSR" a static version of client-side JS apps for improved loading performance and better crawler indexability.
CSS Typed Object Model (Typed OM) brings types, methods, and a flexible object model to working with CSS values. Shipped in Chrome 66.
The CSS overscroll-behavior property allows developers to override the browser's overflow scroll effects when reaching the top/bottom of content. It can be used to customize or prevent the mobile pull-to-refresh action.
position: sticky and
IntersectionObserver together to determine when elements become sticky. Apply scroll effects without scroll events!
How to setup Karma, Mocha+Chai, and Travis to run automated tests on Headless Chrome.
Headless Chrome (shipping in Chrome 59) is a way to run the Chrome browser in a headless environment. It brings all modern web platform features provided by Chromium and the Blink rendering engine to the command line.
What's new in Lighthouse 1.5. New audits, extension updates, Performance Experiment, online Viewer features, and UI tweaks.
What's new in Lighthouse. Redesign, new best practice audits, and an online report viewer.
The BroadcastChannel API allows same-origin scripts to send messages to other browsing contexts. It can be thought of as a simple message bus that allows pub/sub semantics between windows/tabs, iframes, web workers, and service workers.
Shadow DOM allows web developers to create compartmentalized DOM and CSS for web components
Custom elements allow web developers to define new HTML tags, extend existing ones, and create reusable web components.
Learn how we built a the Google I/O 2016 Progressive Web App (IOWA) using web components, Polymer, and material design and launched it into production on Google.com.
IOWA is a single page application (SPA) that's built using web components, Polymer, Firebase, and has an extensive backend written in App Engine (Go). It pre-caches content for offline users using a service worker, dynamically loads new pages, gracefully transitions between views, and reuses content after first load.
URLSearchParams trivial access and manipulation of the URL's query string
Introduction to the Web Speech API's synthesis feature.
Polymer is a gateway into the amazing future of Web Components. Learn more about Web Components and Polymer from the Chrome Dev Summit
Powering a css background using canvas or webgl
Intro to the Full Screen API