If your IDE supports Emmet (supported by VS Code out of the box) then you can use "!"-tab to get the same tags.
Tags to make HTML work like you expect
211–220 of 248 posts
Re: Tags to make HTML work like you expect
#212Earlier quoted context omitted.
I wish `dang` would take some time to go through the website and make some usability updates. HN still uses a font-size value that usually renders to 12px by default as well, making it look insanely small on most modern devices, etc. At quick glance, it looks like they're still using the same CSS that was made public ~13 years ago: https://github.com/wting/hackernews/blob/5a3296417d23d1ecc90...
Shameless plug: I made this userstyle to make HN comfortable to handle both on desktop and mobile. Minimal changes (font size, triangles, tiny bits of color), makes a huge difference, especially on a mobile screen. https://userstyles.world/style/9931/
Thanks for that, it works well, and I like the font choice! Though personally I found the font-weight a bit light and changed it to 400.
Re: Tags to make HTML work like you expect
#213Earlier quoted context omitted.
Your whole comment assumes language identification is both trivial and fail-safe. It is neither and it can get worse if you consider e.g. cases where the page has different elements in different languages, different languages that are similar. Even if language identification was very simple, you're still putting the burden on the user's tools to identify something the writer already knew.
Language detection (where “language”== one of the 200 languages that are actually used), IS trivial, given a paragraph of text. And the fact is that the author of the web page doesn’t know the language of the content, if there’s anything user contributed. Should you have to label every comment on HN as “English”? That’s a huge burden on literally every internet user. Other written language has never specified its lan…
I wish this comment was true, but due to a foolish attempt to squish all human charactets to 2 bytes as UCS (that failed and turned into the ugly UTF-16 mess), a disaster called Han Unification was unleashed upon the world, and now out-of-band communication is required to render the correct Han characters in a page and not offend people.
Re: Tags to make HTML work like you expect
#214Earlier quoted context omitted.
Overall I would agree but I also agree with the above commenter. It’s ok for mobile but on a desktop view it’s very small when viewed at anything larger than 1080p. Zoom works but doesn’t stick. A simple change to the font size in css will make it legible for mobile, desktop, terminal, or space… font-size:2vw or something that scales.
It’s not ok for mobile. Misclicks all around if you don’t first pinch zoom to what you are trying to click.
Indeed, the vast majority of things I've flagged or hidden have been the accidental result of skipping that extra step of zooming.
Re: Tags to make HTML work like you expect
#215Earlier quoted context omitted.
On the flipside, HN is the only site I don't have to zoom out of to keep it comfortable. Most sit at 90% with a rare few at 80%. 16px is just massive.
Sounds like your display scaling is a little out of whack?
Yeah, this is like keeping a sound system equalized for one album and asserting that modern mastering is always badly equalized. Tune the system to the standard, and adjust for the oddball until it's remastered.
Re: Tags to make HTML work like you expect
#216Earlier quoted context omitted.
Yeah, I'm really asking for tons of whitespace and everything to breathe sooooo much by asking for the default font size to be a browser default (16px) and updated to match most modern display resolutions in 2025, not 2006 when it was created. HN is the only site I have to increase the zoom level, and others below are doing the same thing as me. But it must be us with the issues. Obviously PG knew best in 2006 for de…
on mobile at least, i find thati can frequently zoom in, but can almost never zoom out, so smaller text allows for more accessibility than bigger text
Browser (and OS) zoom settings are for accessibility; use that to zoom out if you've got the eyes for it. Pinching is more about exploring something not expected to be readily seen (and undersized touch targets).
Re: Tags to make HTML work like you expect
#217I thought automatically implied utf-8, or have things changed since html5 was the new hotness?
Re: Tags to make HTML work like you expect
#218Re: Tags to make HTML work like you expect
#219Earlier quoted context omitted.
Sounds like your display scaling is a little out of whack?
Yeah, this is like keeping a sound system equalized for one album and asserting that modern mastering is always badly equalized. Tune the system to the standard, and adjust for the oddball until it's remastered.
Except we all know what happened to the "standard" with the Loudness War.
Re: Tags to make HTML work like you expect
#220> ` ` The author might consider instead: ` `
It's time for an "en-INTL" (or similar) for international english, that is mostly "en-US", but implies a US-International keyboard and removes americanisms, like Logical Punctuation in quotes [1]. Then AI can start writing for a wider and much larger public (and can also default to regular ISO units instead of imperial baby food). Additionally, it's kind of crazy we are not able to write any language with any keyboar…
We should also enforce a standard where every website has to change their content to match the user’s preferred idiomatic diss, whether it be “yo momma”, “deez nuts”, “six seven”, or a series of hottentot tongue clicks recorded in Ogg Vorbiz.