51–60 of 271 posts
Earlier quoted context omitted.
> input button is hidden using CSS tricks because the actual button can't be styled. Buttons can be styled.
Not the file input button, unless things have changed in the last year since I had to build one. Other buttons, sure, but not on file inputs.
I'm still looking for "just use links". So many frontends I see use fancy onclicks to emulate links (including updating window.location). However they are either not links or are void links. This breaks all sorts of useful things (copy link location, open in new tab &c.).
When it comes to reading text I honestly prefer the old school academic websites (albeit with a max-width set).
Keeping stuff simple even makes maintaining the site simple, I personally run https://www.discoverdev.io and have used zero JavaScript. Inspired by brutalist design principles :)
Earlier quoted context omitted.
Not the file input button, unless things have changed in the last year since I had to build one. Other buttons, sure, but not on file inputs.
Heaven forbid your buttons look like buttons.
Reading this article made me realize what it is that's broken about the concept of semantic markup and why websites even today are div soup. It's the same reason why divs won in the first place. You can't dictate the shape of a document to people and it be anything other than a kludge. Take the site I work on, Great Big Story[1]. We have sections and headers, but our content isn't defined by text, it's defined by gra…
> input button is hidden using CSS tricks because the actual button can't be styled. Buttons can be styled.
Earlier quoted context omitted.
It's a simple sans serif font, what's so bad about it?
Not the OP, but I see what they mean - it's just a bit too heavy, so all the round letters tend to blur together or something.
I tend to prefer leaving it up to their browser default when possible, on the assumption that the few people who really care have customized their browser and don't want me to override it and nobody else will appreciate my refined sensibilities in font selection.
after 2000, graphic designers took over this work and evolved into "frontend" developers. although there were periodic wins like google maps that would have never been produced by the 90s greybeards...most of it has been an endless stream of garbage. but the goatee crowd should not bear all the the blame, some must also fall on the adtech people who insist I need 15 mb of tracking garbage to read a news story.
Earlier quoted context omitted.
> I really wish "reading mode" was a prominent feature in desktop browsers. What do you mean here by "prominent"?
I wish I could set reader mode as the default experience. Then, I’d click on something to load the full experience when I know/think it’s needed (and perhaps have my browser remember that choice). Currently, I can only enable reader mode after my browser has loaded all the shit I don’t want loaded.
I'm still looking for "just use links". So many frontends I see use fancy onclicks to emulate links (including updating window.location). However they are either not links or are void links. This breaks all sorts of useful things (copy link location, open in new tab &c.).
So that's why that happens. Why on earth would you break one of the most foundational aspects of HTML that way?
It's not all that hard to build a React or Angular apps that use proper links along with the browser history API. Designed properly, the apps should be able to load their state and render correctly even when deep-linked to somewhere other than the app's top level.
This isn't a new concern - I remember paying attention to this back in the old days of SPAs using GWT back in 2009/2010.
Unfortunately, many web apps choose to ignore this. On the bright side, lots of them get it right, too.