271–280 of 309 posts
But if I remember correctly the correct way to prevent this was to set the font-size of the input field to at least 16px.
EDIT: More infos: https://stackoverflow.com/questions/2989263/disable-auto-zoo...
Earlier quoted context omitted.
They can send whatever data they like but they have no right of control over what I do with it or how it’s rendered. Browsers would be better if they prioritised user preferences over website designers.
>Browsers would be better if they prioritised user preferences over website designers. The vast majority of users would prefer not to have to write an entire layout and stylesheet for each site they visit, nor would they consider having all sites conform to a single layout or style to be of any value. It's only very small minority of people (probably exclusive to HN) who would prefer the web was nothing more than JSO…
I don’t think this would be a reasonable way to put user preferences ahead of website owners/designers, this seems more like replacing the web with something else entirely.
What I am taking about is not requiring users to be more technical or do more work, precisely the opposite. Make their lives as easy as possible, and design the browser from the perspective that the user is king/queen, and you literally don’t give a shit about the web designer or their business model. If what they want the site to do is incompatible with maximising user happiness, tough luck, the browser should ignore their code or markup.
Good examples of features (some) browsers incorporate which do some of the job without requiring technical knowledge, most of which should IMO be on by default:
- preventing autoplay of videos and audio
- the flag to force enable Zoom
- reader mode
- blocking ads and or trackers
- etc.
I’d love to see much more of it, and enabled by default.
Earlier quoted context omitted.
"People using those devices are not our target demographic."
Then they complain that people in that demographic don't use their product. Because it turns out that people in that demographic exist and they're trapped in a bubble where anyone who is using an old device is a child, elderly person or homeless.
Yes! I have good eyesight but still frequently zoom for various reasons. The main one is small images and diagrams on responsive websites. Another is clicking small clustered links. In the same vein, if you use images on your responsive website, consider linking to the full size version.
I have decent eyesight post-LASIK, but I have a lot of trouble reading small text. I almost always read books in large-print if it's available, and the Kindle has been a godsend for this particular reason. I've been tested for dyslexia and I don't have it, I just have a weird brain that has trouble with small text. 95% of the time this is a complete non-issue for me, since my monitor (for home and work) is a 50" 4k T…
Can you tell me what you think of the font sizes? Is it readable enough? Is there room for improvement?
Earlier quoted context omitted.
Same here..I don't even have another browser installed on my main machine. Never have the need for it, FF works great. I think the OP has too many plugins :)
now some apps grab keys from the browser like "control-F" won't give me a native search modal dialog - instead providing their own search widget. Things like this break experience of the web for me. Combine that with tridactyl which i prefer to use to navigate around and it's even worse. My addon list isnt that big either... it's just that I disable a lot of things as well, like webGL and other stuff. Suprising numbe…
Follow https://github.com/tridactyl/tridactyl/issues/2712 if you want updates when that's added. It would help if you could link to the website that hijacks ctrl-f in that issue :)
My pet theory: I'm pretty sure this is because when HTML5 became a thing, some major tech blog showed us what an HTML5 page would look like (simplified doctype, meta charset) and they included the viewport settings that disabled zoom. Then pretty much everyone copied from these guides, and here we are. I remember I had used HTML5 skeleton templates for a while before I learned that the "maximum-scale=1, user-scalable…
Yes it is silly. The article actually ends with some useful tips: As a user, you can force allow zooming: In Firefox find the settings, select “Accessibility” and activate “Zoom on all website” In Chrome find the settings, select “Accessibility” and check “Force enable zoom”
Unfortunately this also disables it on sites where it makes sense. For example I have a simple tool to pick a random person or split people into groups https://playerone.kevincox.ca/ Without zoom disabled 5 people putting their fingers on a screen looks a lot like a pinch gesture. Disabling the default event handlers only works some of the time. This is a common problem with the web, we can't have nice things because…
I've never been able to zoom on mobile apps.
Earlier quoted context omitted.
Almost all major template for JS frameworks these days include that line. And there are tons of guides that specify adding that in. I get why it's there, if you're building a PWA that is supposed to mimick a mobile app, you have to enable that to override some annoying mobile browser behaviors like zooming on an input. The problem is that the above scenario is about the only time you would want to set the viewport in…
Call me highly skeptical. I have not personally seen disabling zoom recommended in a very long time.
Earlier quoted context omitted.
It is the creator's right to dictate the original presentation, but it is not the creator's right to dictate a user's behavior. Just like it is a filmmaker's right to set the default framerate and playback speed for a film, but you can rewind or fastforward, or play the film at X speed if you so wish in your media player. Disabling or otherwise inhibiting user behavior is not a creator's right.
Well, I don't believe it's not their right, but I am otherwise in agreement with you - it's daft to block such functionality. Ultimately, that's the creator's mistake to make and it's incumbent upon the end-user to read the content as they can, if they must. I'm not sure why people believe they have a right to dictate how someone else's content is created. I guess I'm more talking about individuals here, not organisa…
I do not believe anyone here is at all believing that they have a right to dictate how someone else's content is created. The argument is about modification, not creation. People should absolutely have the ability to modify their local version of the content to make it readable to them.
Earlier quoted context omitted.
> override some annoying mobile browser behaviors like zooming on an input. Yep, I've seen some people disable zoom in their webpages specifically to prevent Safari from auto-zooming all over the place as the user moves from this to that input. It gets really annoying if you have anything but the simplest form. And what webpage doesn't have at least one form on it, even just the search box? I fully agree with OP that…
Safari only zooms if your input text is too small (less than 16px). The answer to defeating autozoom is to not make inputs that many people would need to zoom manually.
The manager doesn't want that annoying autozoom. The designer doesn't want to change the font size or page layout. There are also edge cases where something that was supposed to be 16px ends up being slightly smaller because of unit conversion and Safari zooms anyway. The developer, tired of this bullshit, googles a solution to satisfy everyone.
Fortunately, there's yet another workaround for developers stuck in this situation. Drop "maximum-scale=1", but keep "user-scalable=no" in the meta viewport tag. Safari will ignore the directive and allow the user to zoom freely, but this somehow disables zooming on inputs. Makes sense, huh?
One browser implementing a non-standard feature that doesn't even work consistently eventually hurts everyone, including the developer and the user. Just blaming the developer misses the larger problem.