Live data from Hacker News

HEAD – A guide to elements

htmlhead.dev

111–120 of 129 posts

Re: HEAD – A guide to <head> elements

#112
post #56
post #21

Earlier quoted context omitted.

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!?

house salad?

Re: HEAD – A guide to <head> elements

#113
post #56
post #21

Earlier quoted context omitted.

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!?

It didn’t happen to be this site? https://www.dwellito.com/modular-homes/cover (example home)

Only asking because it’s a friend’s site and I helped him build the quote modal which you currently can’t zoom.

Re: HEAD – A guide to <head> elements

#114
post #109

Earlier quoted context omitted.

If I double-tap a column of text, it will zoom in on the part of the page to fit the width of the column on the screen, but if the column is too wide (e.g. a page with just a single 100% width column of text) the text size is still unreadably small. It won't reflow the column to fit the screen. (e.g. try visiting http://www.catb.org/~esr/jargon/html/I/ICBM-address.html , a page with no viewport directive and not even…

That shows OK on iOS (6 lines of text, vs 2.5 lines on desktop Safari), without even having to double-tap.

You must have much better eyes than me (or a bigger iPhone) - at 6 lines the font size is half the size of the text on Hacker News, which is already pushing it for readability, and a third of the default font size for Safari's own "reader mode".

The 6 lines comes from iOS Safari defaulting to emulating an approx 800 point wide display (on a 400 point wide display)

Re: HEAD – A guide to <head> elements

#115
post #41
post #21

Earlier quoted context omitted.

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…

Is there a way to change this in JS? I'd love to, say, make sure that the zoom doesn't automatically change because I have an input element that's slightly thinner than the viewport and Apple thinks this is what people want, but still let people pinch to zoom.

Not a JS solution but if memory serves, setting the font size of in an input to 16px or greater prevents the mobile auto-zoom. At least on iOS.

Re: HEAD – A guide to <head> elements

#116
post #77
post #64

Earlier quoted context omitted.

I use Dreamweaver all the time. It's actually a full-blooded static site generator, two decades before that was trendy. And marketing can use the visual editor to make it a content management system.

I still use a copy because no editor has a built in sftp anymore. Sublime/vs code/phpstorm are great for git projects but for remote projects you don't want to work on locally dreamweaver can't be beat. The only problem is modern code has changed syntax so dreamweaver gives warnings for valid code. I wonder if anyone has updated these.

Since you mention text editors, Emacs can be used to work remotely by its TRAMP remote access layer. Instead of /path/to/file, you type /ssh:user@host:/path/to/file. Since Emacs has a built-in directory browser, you can use it as if it was an SFTP client this way.

Re: HEAD – A guide to <head> elements

#117
post #96

Earlier quoted context omitted.

No, Safari on iOS auto-formats text columns to be screen width when you zoom in (double-tap) on them... but the rest of the website is intact!

If I double-tap a column of text, it will zoom in on the part of the page to fit the width of the column on the screen, but if the column is too wide (e.g. a page with just a single 100% width column of text) the text size is still unreadably small. It won't reflow the column to fit the screen. (e.g. try visiting http://www.catb.org/~esr/jargon/html/I/ICBM-address.html , a page with no viewport directive and not even…

That page is fine on my fairly old android phone while using brave. It might even be a bit jarring because the text is a bit too big.

Re: HEAD – A guide to <head> elements

#118
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).

I agree with this. I often prefer desktop pages because they have more functionality. Even Google's search gives you better search settings in desktop mode compared to mobile (you can't set arbitrary search dates on mobile, you can on desktop, oh and mobile search forces the horror of AMP on you). I also loathe the mobile version of reddit, even more than the new UI.

The only pages I prefer in mobile view are ones that get rid of their backgrounds and useless white space on the sides. I use HN in mobile view, but the difference is small enough that it doesn't matter.

Even the htmlhead.dev site that is linked works better in desktop mode, because it doesn't force you to scroll the code tags.

Re: HEAD – A guide to <head> elements

#119
post #109

Earlier quoted context omitted.

That shows OK on iOS (6 lines of text, vs 2.5 lines on desktop Safari), without even having to double-tap.

You must have much better eyes than me (or a bigger iPhone) - at 6 lines the font size is half the size of the text on Hacker News, which is already pushing it for readability, and a third of the default font size for Safari's own "reader mode". The 6 lines comes from iOS Safari defaulting to emulating an approx 800 point wide display (on a 400 point wide display)

Indeed, I've 20/20 vision... Setting "Larger Text" in Accessibility Settings unfortunately doesn't increase the rendered text size on that website (it should) but it also doesn't increase it on Twitter's fully mobile website.

Re: HEAD – A guide to <head> elements

#120
post #51

Earlier quoted context omitted.

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.

Re: them being inaccurate: that was true many moons ago, but it seems they’ve cleaned up and are more accurate now IMHO.
Post reply on HN