Live data from Hacker News

HEAD – A guide to elements

htmlhead.dev

51–60 of 129 posts

Re: HEAD – A guide to <head> elements

#51

Question: how many of these are standardized? I'm not particularly interested in adding a bunch of specific, proprietary tags…

I'd go by W3 https://www.w3schools.com/html/html_head.asp

Then again were all slaves to the whims of Alphabet and Facebooks for traffic.

Re: HEAD – A guide to <head> elements

#52
post #20

Please no. IMO this makes most pages unusable on mobile. Most websites, e.g. news websites with long-form articles, shouldn't be using mobile pages / responsive design / zoomed-in layout at all. Web apps (Twitter, GMail), maybe. But most mobile pages are far more unusable than desktop versions (looking at you, Facebook and Reddit).

It seems to work well for motherfuckingwebsite.com (their is almost exactly the "recommended minimum" here).

But, I also have no problem with Facebook's mobile site, so maybe I just don't see the same problems as you are seeing.

Re: HEAD – A guide to <head> elements

#54
post #14

Does anybody remember that funny thread where some dev here was saying "who calls it HTML5 anymore" as if everyone else was out of touch with stagnating irrelevant skills that would immediately throw red flags during a phone screen? It just gave me a chuckle thinking about it Thanks for the guide!

Uh... what do people call "it" now-a-days? Serious

"web dev" according to that guy from the old thread

sure, I've heard that context too

Re: HEAD – A guide to <head> elements

#56
post #21

> The above 2 meta tags must come first in the to consistently ensure proper document rendering. It looks like they don't follow their own advice:

Do what they say, not what they do! maximum-scale has only three valid uses: 1. extreme values, like 5.0, if a browser misdetects that zooming that far is useful when it isn't (rare) 2. pure-app websites like maps or video games that have alternative scaling arrangements and browser pinch-zoom gets in the way. 3. there is no number three, and the thing you are thinking of is incorrect. maximum-scale is an automatic u…

I tried to order a house online last night and I got to the "enter your email address to get your free quote" and because I couldn't zoom out, I could not see the Submit button.

OMG, I thought how much money is this company losing because their website intentionally disables a built in feature!?

Re: HEAD – A guide to <head> elements

#57
post #38

Earlier quoted context omitted.

> maximum-scale is an automatic usability and accessibility fail I wish more people realized this. As somebody that's visually impaired, it makes mobile browsing quite painful for me.

just out of curiousity, how do you deal with this problem in native apps where pinch zoom is disabled?

You can't, and it sucks. That's why the web is better, or at least why it's supposed to be better.

Re: HEAD – A guide to <head> elements

#58
DublinCore[1] is totally missing! It once was the metadata standard, it's understood by archives and libraries (including Library of Congress) worldwide, macOS will automatically import them into spotlight, etc.

Instead we find many of those tags (title, description, author, etc.) hidden behind the namespace of some corporations.

[1] https://www.dublincore.org/specifications/

Re: HEAD – A guide to <head> elements

#59
post #51

Question: how many of these are standardized? I'm not particularly interested in adding a bunch of specific, proprietary tags…

I'd go by W3 https://www.w3schools.com/html/html_head.asp Then again were all slaves to the whims of Alphabet and Facebooks for traffic.

W3Schools is not W3C, and is frequently inaccurate.
Post reply on HN