Android Chrome Canary is experimenting with an animated back gesture like iOS 🤯 Here's a video of me trying it on my full screen pwa from nerdy.dev h/t to @bramus for sharing this with me today!

for me, it's: 1. a masonry layout isn't a grid. there's no shared row lines, only columns. so it has to ignore all sorts of syntax to accommodate this, syntax we'll have to memorize isnt applicable 2. if masonry is it's own thing, it can pace and grow at it's own rate. subgrid has already added tons of bugs and complexity to grid layouts, adding masonry in there too makes the combinatorial explosion even greater tldr; Chrome is pro masonry. we're adocating things are simpler for both spec writers, site authors and implementors to make a new layout strategy for masonry instead of appending it to grid. this would mean nothing to unlearn or exceptions to memorize. and yeah, performance is better, that's nice too. it's becoming pretty common that initial proposals for features get push back and refined, the good news is, so far, it's always been a better spec for it.