Earlier quoted context omitted.
To be fair, the designer of the website can’t restore scrollbars…
... not exactly. It's possible to essentially reimplement the logic of how scrollbars look, where they are, and when they appear, in just CSS on modern browsers. Ended up having to do part of that once because it was easier at the time than to figure out just why a mismatched browser scrollbar would show up due to complex layouting issue (in embedded world, so we didn't actually have to worry about end user preferenc…
Microfeatures I love in blogs and personal websites
381–390 of 444 posts
Re: Microfeatures I love in blogs and personal websites
#382Re: Microfeatures I love in blogs and personal websites
#383Earlier quoted context omitted.
Obvious solution is obvious: restore the fucking scrollbar. I suspect a strong driver of scrollbar deprecation is the overwhelming dominance of small-screen touch-based mobile devices. An active scrollbar, that is, one which not only shows page scroll depth, but controls it via touch, is one more UI element to generate annoying behaviours given the already perilous state of touch-based UIs. (The inability to correctl…
To be fair, the designer of the website can’t restore scrollbars…
I'm #notafan of customising site scrollbars. But I've written my own CSS to do that (used only on my own, non-public, Web pages), and man is it a breath of fucking fresh air.
There are other apps which are similarly fucked in this regard. Mozilla's Pocket comes to mind.
Re: Microfeatures I love in blogs and personal websites
#384Earlier quoted context omitted.
I think progress bars are a logical consequence of the user-hostile shrinking of the scrollbar. Unusable, narrow things which are often hidden by default, and rarely have a visible elevator (or thumb) anymore. Of course, scrollbars are often entirely useless in pages which insist on loading content piecemeal -- another user hostile pattern.
Obvious solution is obvious: restore the fucking scrollbar. I suspect a strong driver of scrollbar deprecation is the overwhelming dominance of small-screen touch-based mobile devices. An active scrollbar, that is, one which not only shows page scroll depth, but controls it via touch, is one more UI element to generate annoying behaviours given the already perilous state of touch-based UIs. (The inability to correctl…
Yes, I use a big screen, but borderless and clean windows allows me to fit more content into the screen and is less distracting in general.
Re: Microfeatures I love in blogs and personal websites
#385Earlier quoted context omitted.
I've just read a couple of their articles, and I think an aside works nicely, just a note about something, but a full on dialog is a bit much. I suppose a lot of my concern was with how Xe Iaso does it, where it just feels over the top and unnecessary, and IMO distracts from the actual content of the article, which is otherwise largely enjoyable
It is a very hard thing to calibrate. I try to have my internal conflicts and the like get put onto the canvas. I imagine that part of the perceived distraction is because of the CSS being bad (I suck at CSS so much). I'll go dig through a few Tailwind examples and see if I can make the messages more compact.
Re: Microfeatures I love in blogs and personal websites
#386Re: Microfeatures I love in blogs and personal websites
#387> Easily Linkable Headings I haven't found a nice way to do this on both desktop/mobile. What I want is for every heading to have an anchor link that can be copied, similar to a hyperlink. I see a lot of sites do this with a [unicode chain symbol] which is present on hover, but that's not an option on mobile. Alternate option is to have it next to every heading (ugly), turn every heading into a hyperlink without styl…
Try this. /* keep the icon hidden by default */ :is(h1, h2, h3, h4, h5, h6) .icon { visibility: hidden; } /* show the icon on focus and hover */ :is(h1, h2, h3, h4, h5, h6):focus .icon, :is(h1, h2, h3, h4, h5, h6):hover .icon { visibility: visible; } /* show the icon on devices that don't have any accessory that can hover */ @media (pointer: coarse), (any-hover: none) { :is(h1, h2, h3, h4, h5, h6) .icon { visibility:…
Re: Microfeatures I love in blogs and personal websites
#388Earlier quoted context omitted.
... not exactly. It's possible to essentially reimplement the logic of how scrollbars look, where they are, and when they appear, in just CSS on modern browsers. Ended up having to do part of that once because it was easier at the time than to figure out just why a mismatched browser scrollbar would show up due to complex layouting issue (in embedded world, so we didn't actually have to worry about end user preferenc…
Yes, that’s true but I suspect that what you’re doing is also what people are complaining about ;-)
Especially since in our case I essentially deleted the scrollbar.
Re: Microfeatures I love in blogs and personal websites
#389RSS should be a core rather than a 'micro' feature.
Re: Microfeatures I love in blogs and personal websites
#390Earlier quoted context omitted.
I think progress bars are a logical consequence of the user-hostile shrinking of the scrollbar. Unusable, narrow things which are often hidden by default, and rarely have a visible elevator (or thumb) anymore. Of course, scrollbars are often entirely useless in pages which insist on loading content piecemeal -- another user hostile pattern.
Obvious solution is obvious: restore the fucking scrollbar. I suspect a strong driver of scrollbar deprecation is the overwhelming dominance of small-screen touch-based mobile devices. An active scrollbar, that is, one which not only shows page scroll depth, but controls it via touch, is one more UI element to generate annoying behaviours given the already perilous state of touch-based UIs. (The inability to correctl…
Scrollbars do two things. They let you scroll (duh), but they are also progress indicators. There are other ways of scrolling (e.g. swiping on mobile) which work by default. But there is no other default way of showing progress. I don't particularly like the progress bar example in the original post, something as unobtrusive as a percentage in the bottom right corner would work just as well. But I do want some indication of progress ...