Scroll snapping, state queries, monster hunter, and gamification

https://utilitybend.com/blog/the-customizable-select-part-four-scroll-snapping-state-queries-monster-hunter-and-gamification

29•tobr•7mo ago

Comments

cmiller1•7mo ago

Seems to only work in Chrome, I stared at the "end result" in both Firefox and Safari wondering what the heck was so special about a regular old dropdown menu.

webstrand•7mo ago

Yeah, this is using a new feature[1] only available in Chrome so far. Mozilla is positive[2] about the specification, so we should see it in Firefox eventually, pending an implementation.

[1]: https://developer.chrome.com/blog/a-customizable-select

[2]: https://github.com/whatwg/html/pull/10548

Bengalilol•7mo ago

Doesn't work in Safari and Firefox. The end result = the initial result.

And I would get rid of the mouse events in favor of pointer events.

jakelazaroff•7mo ago

But crucially, it does work - it just looks like a normal select, rather than a fancy scroller.

ethan_smith•7mo ago

Pointer events are definitely the way to go here as they unify touch, pen and mouse inputs while also providing pressure/tilt data and better handling of edge cases like when fingers leave the active area during a gesture.

oneeyedpigeon•7mo ago

The delay between reaching the end of the list and the button greying out is a bit awkward, imo. I think the button should disable instantly, when the end of the list is reached.

tobr•7mo ago

This is part 4 in a series. Part 1 makes it more clear that this is a very new feature with limited availability.

https://utilitybend.com/blog/the-customizable-select-part-on...

yourpants•7mo ago

`<selectedcontent>`? Aren't you supposed to use a hyphen in the names of custom elements?

shhsshs•7mo ago

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

yourpants•7mo ago

Thanks! Somehow I missed it. Seems it's experimental.

Cyykratahk•7mo ago

It's great to see more progress around scroll snapping - I'll have to check out this scroll-state container query and the new events.

The biggest missing scroll-snap feature I see is the ability to tell a scrolling container to "snap to the next position in this direction", and maybe by extension "which element(s) are currently snapped". In this article clicking an arrow moves the scroll position by a fixed 40px, but it would be very nice to have a proper API that accounts for element sizes, snap alignments, out-of-axis children, etc.

I ended up writing a package a few years ago that does this (scroll-snap-api). It feels so dirty to calculate the styles on every child in the tree just to find scroll snap positions.

SectorC: A C Compiler in 512 bytes

Brookhaven Lab's RHIC concludes 25-year run with final collisions

The F Word

Software factories and the agentic moment

Speed up responses with fast mode

I write games in C (yes, C)

Hoot: Scheme on WebAssembly

Stories from 25 Years of Software Development

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

First Proof

The Waymo World Model

Al Lowe on model trains, funny deaths and working with Disney

Vocal Guide – belt sing without killing yourself

Start all of your commands with a comma (2009)

Reinforcement Learning from Human Feedback

Selection Rather Than Prediction

We mourn our craft

Show HN: A luma dependent chroma compression algorithm (image compression)

Coding agents have replaced every framework I used

The AI boom is causing shortages everywhere else

France's homegrown open source online office suite

72M Points of Interest

Show HN: I saw this cool navigation reveal, so I made a simple HTML+CSS version

A Fresh Look at IBM 3270 Information Display System

Unseen Footage of Atari Battlezone Arcade Cabinet Production

Where did all the starships go?

History and Timeline of the Proco Rat Pedal (2021)

Learning from context is harder than we thought

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox