Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Blog Post with Every HTML Element

patrickweaver.net

Post reply on HN
Print view View original

81–88 of 88 posts

Re: A Blog Post with Every HTML Element

#81

Post by tetris11 »

gsharma wrote: post #74
jwells89 wrote: post #14

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…

This reminds me of “frame buster” JavaScript. It was a piece of JS that goes in the site to combat above mentioned behavior and “freed” your webpages from someone else’s content frame.

Is this the same as now right clicking on an iframe and selecting "Show This Frame Only"?

Re: A Blog Post with Every HTML Element

#82

Post by proamdev123 »

withinboredom wrote: post #70
proamdev123 wrote: post #67

Earlier quoted context omitted.

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

Lol. Hilarious! Thanks for elaborating.

Re: A Blog Post with Every HTML Element

#83

Post by proamdev123 »

marcosdumay wrote: post #72
proamdev123 wrote: post #67

Earlier quoted context omitted.

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!

The GP made an entire game in an (autogenerated) static HTML file. Most browsers don't have a 5MB single HTML as an usual target, and I guess not as a test case either.

Got it. Thanks!

Re: A Blog Post with Every HTML Element

#84

Post by throwaway18533 »

runarberg wrote: post #77
dsego wrote: post #65

Earlier quoted context omitted.

One of many things that irk me, like why limit to 1-6 instead of allowing an attribute for arbitrary size, eg

They tried to make the the explicit number irrelevant and infer the level by the number of nested sections, so instead of: Title Section Sub Section Sub Sub Section You could simply use repeatedly and keep the semantic structure of the former. Title Section Sub Section Sub Sub Section However this was never implemented by any browser or screen reader and was finally dropped from the standard. http://html5doctor.com/c…

XHTML 2 did that. It only had a tag that was depending on to define the level. In fact your code would be exactly like xhtml2, if you replaced with

I understand why some people might not like xhtml2, but it did have some good ideas for creating a semantic document

Example: https://www.w3.org/TR/2010/NOTE-xhtml2-20101216/mod-structur...

Re: A Blog Post with Every HTML Element

#85

Post by account42 »

jwells89 wrote: post #14
Sniffnoy wrote: 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…

The big issue with this any really an use of frames is that you can't bookmark or share the state.

Re: A Blog Post with Every HTML Element

#87

Post by Sniffnoy »

tetris11 wrote: post #81
gsharma wrote: post #74

Earlier quoted context omitted.

This reminds me of “frame buster” JavaScript. It was a piece of JS that goes in the site to combat above mentioned behavior and “freed” your webpages from someone else’s content frame.

Is this the same as now right clicking on an iframe and selecting "Show This Frame Only"?

No -- the point of a frame-buster script is that it's a script included on a page to force that page out of a frame, it's not something the user runs deliberately.

Re: A Blog Post with Every HTML Element

#88

Post by spread_love »

bandergirl wrote: post #44
spread_love wrote: post #6

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…

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/small

...and is supposed to mean "idiomatic text" now but let's be honest it's never used that way
Post reply on HN