The article is interesting, but I often come across resources that talk about or reference the HTML5 specification by the W3C. Since 2019, HTML has become a living standard (and therefore no longer has a version number). It is available through Whatwg here: https://html.spec.whatwg.org/multipage/
A Blog Post with Every HTML Element
41–50 of 88 posts
Re: A Blog Post with Every HTML Element
#42You can nest details/summary tags. I once created a choose-your-own adventure using it and posting it on our corporate intranet (I had a generator script to stitch things together. The actual text was only a few pages long.) The HTML was 5mb ... I broke a lot of browsers that day. It had to be deleted.
Re: A Blog Post with Every HTML Element
#43Earlier quoted context omitted.
> no simple standard CSS declaration to hide something from visible display but keep it for screenreaders ARIA attributes allow for that. https://developer.mozilla.org/en-US/docs/Web/Accessibility/A... Example code. https://stackoverflow.com/questions/26032089/in-html-how-can...
aria-label/labelledby is not always a workable solution. Sometimes you really need the text to be sitting there on the page as text for things to work right. Note that the very SO thread you linked to goes immediately to doing position/clipping tricks right after mentioning aria-label.
In addition, aria labels don't work reliably with some HTML elements [1]. Specifically, the example from SO (div) will not work in some screen readers.
[1] https://www.tpgi.com/short-note-on-aria-label-aria-labelledb...
Re: A Blog Post with Every HTML Element
#44Most of these aren't widely used because they were quaint attempts at solving problems that no longer exist, could be better solved with CSS (as the author concedes with ), and very much depend on browser implementation. I was excited when and landed in all evergreen browsers for example, but just to get the content to slide open (guiding the user) instead of pop open requires JS (the best implementations I've seen u…
used to be a formatting tag, but with HTML5 it became a “fine print” tag.[1] Formatting-only tags like have long been deprecated and fallen out of use.
[1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/smallRe: A Blog Post with Every HTML Element
#45I was trying to make a web browsing ai agent a few days ago and I was shocked to find that hacker news comments are implemented as table inside table inside table.
I was delighted when I found this out - my userContent.css to make HN more readable (make content have a limited width, set a 1.5em line-height and extra padding-top for all paragraphs). I no longer struggle to read HN on a wide browser which display 250 characters on a single line. Each paragraph is readable, and the paragraph breaks are visibly higher than the line-height.
Do you mind sharing this? Sounds like it would solve the exact problem on my ultra-wide monitor.
Re: A Blog Post with Every HTML Element
#46Earlier quoted context omitted.
I was delighted when I found this out - my userContent.css to make HN more readable (make content have a limited width, set a 1.5em line-height and extra padding-top for all paragraphs). I no longer struggle to read HN on a wide browser which display 250 characters on a single line. Each paragraph is readable, and the paragraph breaks are visibly higher than the line-height.
Do you mind sharing this? Sounds like it would solve the exact problem on my ultra-wide monitor.
Not at all, copied verbatim from my userContent.css file, full path $FIREFOXPROFILE/chrome/userContent.css:
@-moz-document domain(news.ycombinator.com) {
.comment {
font-size: 12px;
line-height: 1.75em;
padding: 10px 0 10px 0;
max-width: 64ch;
display: block;
}
.commtext {
font-size: 12px;
line-height: 1.75em;
padding: 10px 0 10px 0;
max-width: 64ch;
display: block;
}
}Re: A Blog Post with Every HTML Element
#47Awesome article. Like the author, I'm also confused about when to use b and strong & i and em.
is for emphasis, is for other things that typically use italic text (except those that fall under or ), such as foreign words. Analogously for and .
Re: A Blog Post with Every HTML Element
#48Earlier quoted context omitted.
I guess it is some sort of cross-site security thing. Devtools just says "blocked:other" as the reason for not displaying it.
Firefox on Android actually has a great error message here: > Nightly Can’t Open This Page > To protect your security, www.w3.org will not allow Nightly to display the page if another site has embedded it. To see this page, you need to open it in a new window. > Learn more…[1] > [Open Site in New Window] [1]: Links to https://support.mozilla.org/en-US/kb/xframe-neterror-page
Oh my god! You must be very confused now, being told an error message, and some detail about it.
Dear end-user, do you need therapy? I'll make sure that message is removed in the next release, so other end-users are not subjected to such horribly frightening information.
Re: A Blog Post with Every HTML Element
#49> Some of deprecated elements won’t render without some extra work, for example and are designed to be used instead of a , for I guess some kind of collage web page made up of other pages. The author is too young to remember frames, huh? :) I'd just link the Wikipedia article ( https://en.wikipedia.org/wiki/Frame_(World_Wide_Web) ), but I feel like it doesn't explain it very well. So, to briefly explain -- in the ear…
and are now obsolete and not just deprecated and have been so for a number of years. https://html.spec.whatwg.org/dev/obsolete.html#obsolete
Re: A Blog Post with Every HTML Element
#50Has anyone ever encountered a real world scenario where you reached ?
Yes, specs and other technical documents.
For example, the html spec[1] itself.