Note on the fact that this would add JS that needs to be loaded to see the page. No, because similar smart people created server-side rendering, adding another layer of complexity.

How do you implement this keyboard navigation with SSR (if you use buttons)?

https://www.radix-ui.com/primitives/docs/components/radio-gr...

I can’t tell if this is sarcasm or not! Radio buttons support keyboard navigation without JS.

That's what I mean: if you reimplement it, you need client-side JS to support keyboard navigation.

It needs JS to be interactive unlike the native radio button

This interactivity definitely adds a wow effect.

Is it sarcastic or does it appear only on high frame rate devices? To me it simply feels like another radio button.

> Is it sarcastic or does it appear only on high frame rate devices? To me it simply feels like another radio button.

You're absolutely right!

Today I'm using a friends gaming computer. It's a 244hz monitor powered by a RTX 5070 TI and a screamingly fast AMD Ryzen 7 9800X3D CPU with 128GB of overclocked 6000MT/s RAM.

Not only does the radio look mundane for such overcomplicated component, but it also misses clicks where I would expect it to register. Like slightly above or below it.

For example, clicking where the pointer is in this image does NOT select the first radio button. It's not forgiving with regards to precision.

https://i.imgur.com/PNoCJeL.png

It also doesn't catch clicks between the label and the radio button.

In a hilarious turn of fate, on iOS safari the first time one of the radio options is clicked after loading, the css focus style is applied, but a click is not always registered so the radio item ends up stuck in an invalid weird-looking state. I highly doubt the issue would occur if the built in radio were being used

Please, make a Fairphone mini. I'd buy it right away, whatever the price.

Also whatever the battery size though?

Not that I disagree. I bought a Fairphone some years ago and sold it onward because it simply didn't fit in my hand, but the phone I got instead had a delicious combo of small physical battery and terribly inefficient chipset (2019 Exynos). I'd still make the same choice but it's a considerable downside (thankfully the only downside of this phone besides its age and software support by now)

Does not work without Google Play services. No-go.

> The trend at the time was that every website should be architected as an application, and then shipped to the user’s browser to render.

This is wrong. Some websites are better mostly (mostly) rendered on the client (we call them "apps", like a map application) and some are better mostly rendered on the server (like blogs).

It was and will be.

Google maps on mobile is directing the user to the native app more and more. So I doubt this. Geolocation on desktop is mostly useless.

I wonder if this new element is used by MapLibre.

Protomaps should have been cited.

Not many people know that compass on the Web is possible.

https://cartes.app/nord

Works on most Android phones.

I discovered that when I figured out that a Web map without a position arrow is missing something.

Turns out, it was easy to implement. The Web has been so forgotten for the profit of app stores that entreprises don't even bother to check how capable it is.

I know offline maps (think Comaps) is possible on the Web, there just isn't anyone that did implement it yet.

Interesting. Is there a license that acts this already ?