281–290 of 385 posts
Earlier quoted context omitted.
All you need to do is use standard HTML form elements. None of those questions are even relevant, just excuses to increase complexity and make things harder for everyone.
[flagged]
As the author identifies, the idioms come from the use of system frameworks that steer you towards idiomatic implementations. The system UI frameworks are tremendously detailed and handle so many corner cases you'd never think of. They allow you to graduate into being a power user over time. Windows has Win32, and it was easier to use its controls than rolling your own custom ones. (Shame they left the UI side of win…
> You can't change the height of a native button, for example. You can definitely do so, it's just not obvious or straightforward in many contexts.
It used to be, in AppKit, that a normal NSButton could have its size class changed (small, regular etc.) but you couldn't set the height without subclassing and doing the background drawing yourself!
Earlier quoted context omitted.
> There was no way to tell where a given style is used from, or even if it's used at all It's pretty easy. Open the inspector, select an element and you will find all the styles that apply. If you didn't try to be fancy and use weird build tools, you will also get the name of the file and the line number (and maybe navigation to the line itself). In Firefox, there's even a live editor for the selected element and the…
> It's pretty easy. Open the inspector, select an element and you will find all the styles that apply. Of course it's not easy, 80% of that list will be some garbage like global variables I would only need when I actually see them in a style value, not all the time. The names are often unintuitive, and search is primitive anyway, so that's of little help. And the values are just as bad, with --vars() and !important n…
Earlier quoted context omitted.
> It's pretty easy. Open the inspector, select an element and you will find all the styles that apply. Of course it's not easy, 80% of that list will be some garbage like global variables I would only need when I actually see them in a style value, not all the time. The names are often unintuitive, and search is primitive anyway, so that's of little help. And the values are just as bad, with --vars() and !important n…
Someone is using Tailwind (and the likes) and/or CSS-in-JS. Which I dump squarely in the weird tools.
Earlier quoted context omitted.
Hiding scrollbars is a deeply annoying trend. I don't understand the rationale. Because someone thought it looks aesthetically cooler?
mobile first philosophies is my guess. ...curious who decided seeing scrollbars wasn't useful on mobile though. it's very useful knowing where i am in a long scrolling thing.
Earlier quoted context omitted.
> As an example, the structure of HN's reply page Is made up of table tags, which the CSS people will tell you is wrong/impossible/has different semantics.
> Is made up of table tags, which the CSS people will tell you is wrong/impossible/has different semantics A table is a grid. Lot of UI toolkits have a grid container, and even CSS added it specifically as a layout engine.
Sure. As long as the end result is the same grid, it shouldn't matter. But in a CSS world you switch your table for grid-layout divs (or vice versa) and suddenly one corner case thing that is in one grid cell somewhere in your app gets its styling flipped.
Earlier quoted context omitted.
I haven’t happened to have seen that - which web apps do it?
Hmm, at this point I think I might be imagining it ... I'll let you know if I can find it ...
Earlier quoted context omitted.
Carriage return and line feed go way back. Tty stands for teletype. A computer was the job description of a person. It’s turtles all the way down.
What lower turtles were there? My impression was that teletypes were the first proper keyboard-based interfaces.
In text boxes in some applications, enter submits the entered text, and ctrl-enter forces a newline (not at my computer, but I think Slack does this). In others, it's the other way around (pretty sure GitHub does this for comments). I don't know how we got here and I don't know how to fix it, but "bring back idiomatic design" doesn't help when we don't have enough idioms. I'm not even sure if those two behaviors are…
I have a suspicion — it has to do with instant messaging clients. The idea being that you want to type short one-line messages and send them as quickly as possible in most cases, but in a rarer case when you do want a line break, that's Ctrl+Enter or Shift+Enter. Probably the first one where I personally encountered "enter is send" is ICQ, but I'm sure it's older than that, I would be surprised if no IRC clients did that.