Live data from Hacker News

A Blog Post with Every HTML Element

patrickweaver.net

61–70 of 88 posts

Re: A Blog Post with Every HTML Element

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

One usage of frames I recall was for sites that were meant to act as an index of other sites, where there’d be a sidebar on the left with links to various sites that opened on the right. I think this was actually a pretty good use case for frames, especially back before browser tabs existed. It was nicer to run through a list of links in one window with frames than to jump back and forth through history or juggle mul…

I remember a search engine working like that, but I forget it's name. Dog something? It's ground breaking idea was, hey all these search engines kind of suck and you have to go to about 10 of them to find what you want - so what if you enter one search term on our page and we'll Iframe in the results from 10 different search engines!

I remember everyone at my university using it for quite a while, then google came out we were floored with the simplicity of it's home page (imagine what ten 1999 yahoo search competitor results crammed into one page looked like :D )

Re: A Blog Post with Every HTML Element

#62

Earlier quoted context omitted.

One usage of frames I recall was for sites that were meant to act as an index of other sites, where there’d be a sidebar on the left with links to various sites that opened on the right. I think this was actually a pretty good use case for frames, especially back before browser tabs existed. It was nicer to run through a list of links in one window with frames than to jump back and forth through history or juggle mul…

I remember a search engine working like that, but I forget it's name. Dog something? It's ground breaking idea was, hey all these search engines kind of suck and you have to go to about 10 of them to find what you want - so what if you enter one search term on our page and we'll Iframe in the results from 10 different search engines! I remember everyone at my university using it for quite a while, then google came ou…

Dogpile

Re: A Blog Post with Every HTML Element

#63

Earlier quoted context omitted.

One usage of frames I recall was for sites that were meant to act as an index of other sites, where there’d be a sidebar on the left with links to various sites that opened on the right. I think this was actually a pretty good use case for frames, especially back before browser tabs existed. It was nicer to run through a list of links in one window with frames than to jump back and forth through history or juggle mul…

I remember a search engine working like that, but I forget it's name. Dog something? It's ground breaking idea was, hey all these search engines kind of suck and you have to go to about 10 of them to find what you want - so what if you enter one search term on our page and we'll Iframe in the results from 10 different search engines! I remember everyone at my university using it for quite a while, then google came ou…

Dogpile?

Re: A Blog Post with Every HTML Element

#66

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

Lol, in modern react apps sometimes I find or even better some made up "component" like or . Then there is styled components like bold = styled.span`font-weight: bold`. It's amusing.

Re: A Blog Post with Every HTML Element

#67

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

This sounds interesting, but I’m not following. Do you mind expanding?

Specifically, how does nesting details/summary tags relate to 5 MB of HTML, and how does that relate to breaking a lot of browsers?

Sounds like a great story, and I’d love to hear it!

Re: A Blog Post with Every HTML Element

#68
post #63

Earlier quoted context omitted.

I remember a search engine working like that, but I forget it's name. Dog something? It's ground breaking idea was, hey all these search engines kind of suck and you have to go to about 10 of them to find what you want - so what if you enter one search term on our page and we'll Iframe in the results from 10 different search engines! I remember everyone at my university using it for quite a while, then google came ou…

Dogpile?

Dogpile! That's it! Oh wow it even has it's own wikipedia page, and it's still online (albeit a very different site now).

Re: A Blog Post with Every HTML Element

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

One usage of frames I recall was for sites that were meant to act as an index of other sites, where there’d be a sidebar on the left with links to various sites that opened on the right. I think this was actually a pretty good use case for frames, especially back before browser tabs existed. It was nicer to run through a list of links in one window with frames than to jump back and forth through history or juggle mul…

iframe can do that: just change the src attribute.

Re: A Blog Post with Every HTML Element

#70

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

This sounds interesting, but I’m not following. Do you mind expanding? Specifically, how does nesting details/summary tags relate to 5 MB of HTML, and how does that relate to breaking a lot of browsers? Sounds like a great story, and I’d love to hear it!

If you have a story with the following prompt:

> go left

> go right

Where each of those is a branch in the story. Even if both branches converge eventually, all possibilities need to be in each branch. And so on. The number of summary tags is n! where n is the number of possible decisions.

Thus you very, very quickly end up with a very large dom. Browsers aren’t really optimized to display hundreds of thousands of these tags, so they crashed.

Post reply on HN