116 Followers
36 Following
55 Posts
Software developer at Google working on chromium and web standards. Opinions are my own.
Just finished prototyping a set of CSS feature proposals that aim to enable authors to create responsive carousel experiences with pure CSS. Try it out at https://flackr.github.io/web-demos/carousel/
Carousel example

Scroll snap + scroll driven animation + smooth scroll-behavior = no JS "hamburger" menu with swipe support: https://flackr.github.io/web-demos/css-scroll-snap/menu/#content
Using position: sticky + https://www.w3.org/TR/scroll-animations-1/ to implement pure CSS scroll driven story-telling 📜📖 https://flackr.github.io/web-demos/scroll-animations/story-telling/
Scroll-driven Animations

Used my prototype of display animation[1] and transition[2] support to create a demo of entry and exit animations for a dialog in CSS[3].

[1] https://github.com/w3c/csswg-drafts/issues/6429
[2] https://github.com/w3c/csswg-drafts/issues/4441
[3] https://output.jsbin.com/buquher

[css-display] Why is display listed as not animatable instead of animation type: discrete? · Issue #6429 · w3c/csswg-drafts

https://www.w3.org/TR/css-display-3/#the-display-properties I thought we were going for discrete for all properties that can't be intelligently interpolated, and that "not animatable" was reserved ...

GitHub