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

51–60 of 88 posts

Re: A Blog Post with Every HTML Element

#51

Post by SquareWheel »

b112 wrote: post #48
jorams wrote: post #37

Earlier quoted context omitted.

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.

Chrome shows the following:

> Refused to frame 'https://www.w3.org/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://cms.w3.org/".

Re: A Blog Post with Every HTML Element

#52

Post by euroderf »

Semantic HTML has excellent potential. I personally like the style where footnotes for running text are placed in the right-side margin, in a smaller and/or semi-greyed font, and maybe with details/summary expanders.

But every implementation of styles like this seem to require some sort of detailed knowledge of CSS to wrangle it into working order.

Re: A Blog Post with Every HTML Element

#54

Post by __float »

SquareWheel wrote: post #51
b112 wrote: post #48

Earlier quoted context omitted.

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.

Chrome shows the following: > Refused to frame ' https://www.w3.org/ ' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://cms.w3.org/ ".

It only shows that in the console for me. The rendered error page just says 'www.w3.org refused to connect.'

Re: A Blog Post with Every HTML Element

#55

Post by spread_love »

lelanthran wrote: post #39
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…

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

Thanks! I should have specified it's impossible without a fixed height (height: auto).

Re: A Blog Post with Every HTML Element

#56

Post by crooked-v »

peddling-brink wrote: post #35
zarzavat wrote: post #31

Earlier quoted context omitted.

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?

That's where the classic nickname 'Mario tags' came from.

Re: A Blog Post with Every HTML Element

#57

Post by famfamfam »

Regarding the element, which the OP mentions their confusion about as:

> I was initially surprised that it survived to HTML 5 (while didn’t) because modern browsers treat it as essentially a . Researching further on Wikipedia I read: "MENU existed in HTML Tags, and was standardized in HTML 2.0; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict; then redefined in HTML5, but removed in HTML 5.2," and now I don’t know what to think.

HTML 5.2 was retired by W3C in 2021 in favour of the WhatWG HTML Living Standard, which (unlike HTML 5.2) never deprecated , and has been redefined as representing "a toolbar consisting of its contents, in the form of an unordered list of items (represented by li elements), each of which represents a command that the user can perform or activate.".

Wikipedia's list of elements seems to be out of date here — along with a lot of the Wikipedia information on HTML versions — as the element is still alive. Given its history of being repeatedly deprecated, and the fact that event recently browsers were confused by exactly what semantics to assign to , you are probably nearly always better off using with an appropriate ARIA role attribute (toolbar, menu, or menubar).

Post reply on HN