Surprised all icons is only:
I thought there was literally like a dozen different sizes and names to support all different Apple and Android devices.
HEAD – A guide to elements
61–70 of 129 posts
Re: HEAD – A guide to <head> elements
#62Earlier 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?
Taking screenshots and zooming in on those... a very tedious process.
Re: HEAD – A guide to <head> elements
#63Earlier 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 FYI in case you didn't know, both Firefox and Chrome on mobile allow you to force zoom even if there's a viewport restriction. Check accessibly settings.
Had no idea, thank you!
Re: HEAD – A guide to <head> elements
#64> Is Dreamweaver still a thing? I haven't heard of it in years, many years.
I last touched it in 2012 - but apparently, yes, yes it is: https://helpx.adobe.com/dreamweaver/using/whats-new.html Although, it looks like their cumulative 2019 updates are limited to the following headlines between the two: 1) added support for HTML tag highlighting inside PHP code 2) bootstrap CSS support. ... I was surprised to see it was still alive.
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.
Re: HEAD – A guide to <head> elements
#65Please 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).
We must have different devices. IMO most pages are unusable on mobile without this. I wonder if it's the device, website content, or personal preference at play here.
Re: HEAD – A guide to <head> elements
#66Earlier quoted context omitted.
just out of curiousity, how do you deal with this problem in native apps where pinch zoom is disabled?
Taking screenshots and zooming in on those... a very tedious process.
With iOS you don't need to do this. You can enable zooming as a system-wide feature. You can even zoom parts of the screen, like a magnifying glass. You can find all of these settings under Settings -> Accessibility -> Zoom.
Re: HEAD – A guide to <head> elements
#67Why would be required if you can set it in the HTTP headers? I've also read that modern browsers (everything except IE) will look for a byte-order mark.
Probably nice for people that save the HTML document locally via curl or similar.
curl or similar could inject a meta tag.
Or we could have a default of UTF-8.
I don't dispute that it can be nice. I am just curious why so many say it is required.
Re: HEAD – A guide to <head> elements
#68Why would be required if you can set it in the HTTP headers? I've also read that modern browsers (everything except IE) will look for a byte-order mark.
Quite a few of these can be set in the HTTP headers as well, but people editing templates don't always have access or know how to do it. BTW; not all UTF-8 text has a byte-order mark, I would say most of them don't.
If you can't set the header, sure, put it in the head.
What I don't get is why so many say it is required in the head, even when you manage to set the header.
Re: HEAD – A guide to <head> elements
#69Earlier quoted context omitted.
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.
My favorite weird thing that happens without certain 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.
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.
Re: HEAD – A guide to <head> elements
#70Earlier quoted context omitted.
Probably nice for people that save the HTML document locally via curl or similar.
curl or similar could inject a meta tag. Or we could have a default of UTF-8. I don't dispute that it can be nice. I am just curious why so many say it is required.
I imagine it's the cumulative amount of my first example, curl, and probably other "save as html" functionality in some browsers, crawlers, s3 buckets, archival tools, and so on. I'm sure many can do as you suggested and inject the header, but suspect many don't.
Another use case might be content that is authored in a content management system. Perhaps it's the easiest way to carry your intended charset to the destination.