正在加载视频...
视频加载失败
Pinterest moved to native CSS carousels to replace legacy JS platform-wide → Using CSS primitives like scroll markers and snap, they achieved: 📉 90% code reduction (2k JS → 200 CSS) 🚀 15% faster page loads ✨ Smoother, interactive UI
31 条评论

Their carousel implementation isn't what I want native, it's this bad boy. Give us that sweet sweet display: grid-lanes!

It’s actively being worked on! Microsoft is adding the feature to Chromium. They are sweating the details to make sure the implementation is feature complete and spec compliant. ETA TBD.

dope! what are they using to polyfill for safari and firefox?

@grok pode explicar?

This is the kind of frontend progress people underestimate. Replacing custom JS with browser primitives usually buys you three things at once: less code to maintain, fewer edge-case bugs, and better runtime behavior. The 90 percent reduction is wild.

@grok explica de uma forma completa e tecnica

As far as I know, you still can’t make a looped (infinite) carousel with pure CSS where you can seamlessly swipe/scroll straight from the last slide directly to the first one.

That is correct at the moment. Is this something you would like to see in the future?

yes

@grok do all modern browsers support this?

@LeonidasEsteban Is this available for all modern browsers? 🤔

@LeonidasEsteban This is Chromium (Chrome, Edge, Brave) only … but the feature is part of the css-overflow-5 specification, so other browsers can implement it over time. People can resort to feature detection to provide alternatives in browsers with no support.

@LeonidasEsteban Got it! Thanks for clarifying. It's always exciting to see these new CSS capabilities landing in Chromium first. Looking forward to implementing this with proper fallbacks! 🔥

2k lines of JS replaced by 200 lines of CSS. The best code is the code you delete. Native web platform keeps closing the gap on frameworks.

So people are moving towards plain vanilla as the frameworks get bloated

Here is an example of native CSS carousel with polyfill.

Browsers are eating UI logic, less JS glue, more native primitives, this shifts complexity from apps into the platform layer

Spot on. Shifting that complexity down to the platform layer means the browser engine can optimize it at the C++ level, pushing animations and scrolling directly to the compositor thread.

Nice! What about RAM usage on this? One other thing people would probably like to see is more RAM optimization.

hah, wish I could create visuals like these :)

@grok Native CSS is here

save stuff locally instead of pinterest on

I'm very see.

@0xGorri

nice

The real win is shrinking the surface area, not just cutting JS.

Exactly! Swapping a heavy JS carousel for native CSS scroll-snap doesn't just save bytes over the wire, it completely removes that entire execution surface from the main thread.

Is native drag on desktop in scope for improvement? It has been a deal breaker on multiple project for adoption to replace Swiper

@teqqed

Hey... See

true industry got scammed by these middleware bloats in code
相关视频
Sensitive content
Can we please stop with the scroll-jacking carousels on websites? CSS Scroll Snap is a much better solution! Re-built the Uniqlo home page with 6 lines of CSS and 4 lines of JS
Wes Bos
305,522 次观看 • 2 年前

