Live data from Hacker News

A Blog Post with Every HTML Element

patrickweaver.net

31–40 of 88 posts

Re: A Blog Post with Every HTML Element

#31

Awesome article. Like the author, I'm also confused about when to use b and strong & i and em.

I’m not sure if screen readers actually work like this but the intention was that text that is is spoken with emphasis, like “oh, please”, whereas is simply italic, like veni, vidi, vici.

Re: A Blog Post with Every HTML Element

#32
post #24

Earlier quoted context omitted.

Eric Meyer, the king of css still has his old css references in frames pages https://meyerweb.com/eric/css/references/css1ref.html

I get "www.w3.org refused to connect." Is that expected?

I guess it is some sort of cross-site security thing. Devtools just says "blocked:other" as the reason for not displaying it.

Re: A Blog Post with Every HTML Element

#34

Awesome article. Like the author, I'm also confused about when to use b and strong & i and em.

My sense is that the more complicated explanation that OP found is just retconning, trying to explain away the fact that someone in the committee didn't like and but couldn't get anyone else on board with deprecating them.

In practice, any sane screen reader or default visual style will treat them exactly the same.

Re: A Blog Post with Every HTML Element

#35

Awesome article. Like the author, I'm also confused about when to use b and strong & i and em.

I’m not sure if screen readers actually work like this but the intention was that text that is is spoken with emphasis, like “oh, please ”, whereas is simply italic, like veni, vidi, vici .

So will give my screen reader an Italian accent?

Re: A Blog Post with Every HTML Element

#36
post #7

> 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…

Then came iframes, also terrible.

Then came the adtech boom. got things started but a hidden iframe running ads in rotation? That minted fortunes.

Re: A Blog Post with Every HTML Element

#37
post #24

Earlier quoted context omitted.

I get "www.w3.org refused to connect." Is that expected?

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

Re: A Blog Post with Every HTML Element

#38

I 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.

Re: A Blog Post with Every HTML Element

#39

Most 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…

> 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 use WAAPI), Safari adds a proprietary pseudo element, etc.

It is possible to have sliding animations without JS, it just isn't very pretty on close (on open looks fine):

https://codepen.io/dada1smo/pen/LYydWBg

(note, that is not mine, I found it via a comment on a css-tricks link).

Re: A Blog Post with Every HTML Element

#40
post #7

> 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…

https://tintara.tripod.com/FramesSuck.html
Post reply on HN