The fact is, if you're smart enough you can just eyeball raw css and just see it if you close your eyes.

Oh you're not also gifted? Well I guess you're not special enough for this job then. Maybe you should be flipping burgers instead.

/s

The Bash entry was really just a half-finished personal note that I never properly edited. It’s probably out of scope too.

In short: unless the native scroll bar will be wrong, do not under any circumstances hide it.

There are a few specific situations where it can be useful, but I added the caveat precisely because it’s generally not a good practice.

1) You can only use tiny buttons with precise pointers.

2) You can only use hover popups with pointers that can actually hover.

In practice, much of this is too much work and everyone just designs for touchscreens instead. It's rare to find a website that even bothers with using title="" for tooltips because smartphones are a disaster of UI and lack tooltips.

The intended point is that device type is often the wrong thing to detect: a touchscreen laptop may expose both coarse and fine pointers, while a tablet may be connected to a mouse or trackpad. The snippet detects available input capabilities instead, which is usually what the interface should respond to.

I wasn’t particularly careful with the titles, but this one should be "Detect input capabilities". Thanks for the heads-up!

If the term is confusing, I’m open to better wording.

Each note has a stable URL that can be shared or bookmarked and can be indexed independently. A dedicated page also leaves room for longer content or links to related notes.

Flip interactions also behave differently on touch devices and require more care around keyboard accessibility. It’s a valid alternative, but I don’t see navigation to a standalone document as something inherently undesirable on the web.