> 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…
The first website I created on GeoCities back in the 90s used frameset. In exactly the same layout you have mentioned.
> 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…
> 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…
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?
Awesome article. Like the author, I'm also confused about when to use b and strong & i and em.
I had thought that and describe how something should look, whereas and describe the meaning of something. means "this text should be thicker and darker than it normally would be", indicates "this text has gravitas... interpret that however you want". In other words, visual vs. semantic.
I have heard similar but the consequences always seemed weird to me. Following this if something is important and also should look visually different, I should use both and . However If something is important and I don't want it to show, I should use alone and alone only for the case where something should look important but that has actually no meaning as the meaning conferring tag would be .
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.
> 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…
I had thought that and describe how something should look, whereas and describe the meaning of something. means "this text should be thicker and darker than it normally would be", indicates "this text has gravitas... interpret that however you want". In other words, visual vs. semantic.
I have heard similar but the consequences always seemed weird to me. Following this if something is important and also should look visually different, I should use both and . However If something is important and I don't want it to show, I should use alone and alone only for the case where something should look important but that has actually no meaning as the meaning conferring tag would be .
The quintessential semantic use of is for typographically offsetting key words in a longer text, like how 5th Edition D&D adventures do when referencing a monster that has a stat block in the Monster Manual. It’s not strength of voice, but it has meaning that the text be emboldened.
This comes up briefly but I do still find it ridiculous that there's no simple standard CSS declaration to hide something from visible display but keep it for screenreaders. Everything I've seen still does clip, or positions the content off the side of the page, or something like that. How is this not just an alternative "display" value, or an additional property? There's been a "speak" property floating around in on…
Why should it be a part of CSS, that handles visual representation, and not part of HTML, which handles data, structure, and semantics? I wonder if a whitespace with a right aria-label could fit the bill.
> I wonder if a whitespace with a right aria-label could fit the bill.
Aria-label only works on interactive elements. I believe except the div has a `role`, screenreaders will ignore the label.