HEAD – A guide to &lt;head&gt; elements

Re:HEAD – A guide to <head> elements by krapp on Monday September 30, 2019 @05:27PM (#21119815)

What weirdly specific thing?

You don't have to put anything in a head tag, you don't even need a head tag, but it's a good idea to have one and to at least add a charset meta tag. Everything is optional, though.

The entire point of it is for you to share metadata about your page with the browser.

[ Parent | on HN ]

Re:HEAD – A guide to <head> elements by munk-a on Monday September 30, 2019 @06:05PM (#21120109)

My favorite weird thing that happens without certain <head> tags is the ten billion attempts to get a favicon. I don't know if browsers still try all those silly favicon requests if none is defined, but it was saddening to watch that grow to be wide spread previously.

[ Parent | on HN ]

Re:HEAD – A guide to <head> elements by shakna on Monday September 30, 2019 @07:52PM (#21120759)

Yes, they all still issue several favicon requests, so far as I'm aware. Having one, instead of returning a 404, can speed up the page load. Which makes 0 sense.

[ Parent | on HN ]

Re:HEAD – A guide to <head> elements by dyanaraps on Monday September 30, 2019 @08:34PM (#21120950)

This is how I avoid this issue entirely:

    <link href=data:, rel=icon>

This is the smallest possible "null" favicon. It causes the browser to display nothing and ensures 0 HTTP requests for the favicon!

[ Parent | on HN ]

Re:HEAD – A guide to <head> elements by SquareWheel on Tuesday October 01, 2019 @03:22AM (#21122812)

Does the browser display the generic "no favicon" icon, or is it just completely blank? I like the idea.

[ Parent | on HN ]

Re:HEAD – A guide to <head> elements by dyanaraps on Tuesday October 01, 2019 @03:58AM (#21123045)

It's completely blank (tested in Firefox and Chromium).

[ Parent | on HN ]