Closed christianmalek closed 9 years ago
Don't do that. Disabling user-scaling severely reduces accessibility, for example for people who have weak eyesight.
width=device-width, initial-scale=1.0
is pretty much the best viewport tag you could use.
OK. The problem is that e.g. Chrome zooms in when you select an text field. How can I avoid that behaviour?
This is related to mobile devices/browsers.
Why would you want to stop that? I, personally, did not yet use Redundancy on a mobile device, but if the design breaks you should fix the design, not disable zooming.
The design doesn't break. According to http://stackoverflow.com/questions/7073396/disable-zoom-on-input-focus-in-android-webpage it isn't possible without disabling zoom.
I wanted to disable it because in my humble opinion it disturbs the "app feeling". Native mobile apps aren't zoomable. So why should the web app be zoomable? I did a proof-of-concept to see what it looks like when I embed the web app into a native android app with the webview component.
Should this now be implemented or not? I'm confused.
bumb
I would prefer it.
squarerootfury notifications@github.com schrieb am Fr., 8. Mai 2015 07:25:
bumb
— Reply to this email directly or view it on GitHub https://github.com/Redundancycloud/redundancy/issues/144#issuecomment-100103861 .
This is probably a matter of opinion. I do not think websites should mirror the behavior of native apps (There is a reason they are not a native app), especially if this might cause problems for people using other devices or people with something like weak eyesight.
Whould that be an idea to do this only on mobile devices?
Not reliable and way too much effort, I think.
I personally don't use smartphones, so I do not exactly have experience with what is discussed here, but I would assume that zooming in on focused inputs is a feature that can be disabled in a users personal settings?
This would be the best idea. I will add it to the user options to allow scrolling.
I meant device settings, but this works too.
I would suggest to disable it by default though, since an application should be accessible by default.
@Phisherman @elomatreb does this collide with the old meta viewport?
I mean when the settings would be disabled and/ or nobody is logged in, what should be used?
<meta name="viewport" content="width=device-width, initial-scale=1.0">
width=device-width, initial-scale=1.0
is pretty much the best you could do. Makes it easy to work with media-queries, but does not have any real accessibility drawbacks.
Should this be on any device or just mobile ones?
Desktop browsers force scaling if you want to, so you don't need to distinguish between mobile and desktop browsers.
It could also be possible that mobile browsers ignore it.
Issue was fixed. Meta tag is added when the user activates the setting.
add
<meta name="viewport" content="initial-scale=1.0, user-scalable=no" />