Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility/UX: Why adding maximum-scale=1.0? #15024

Closed
Volker-E opened this issue Mar 19, 2015 · 9 comments
Closed

Accessibility/UX: Why adding maximum-scale=1.0? #15024

Volker-E opened this issue Mar 19, 2015 · 9 comments

Comments

@Volker-E
Copy link
Contributor

Currently the viewport meta tag is at layout.base.php:

<meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0">

and at the two other layout* files:

<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0>

What are the reasons for not letting users zoom in on smartphones/tablets? Was it some old, unreliabled iOS behavior?

See dhg/Skeleton#173 for a collection of pro and con arguments in a similar. I'm clearly strongly for the accessibility/less native app approach, allowing users to zoom in.

@MorrisJobke
Copy link
Contributor

cc @jancborchardt

@jancborchardt
Copy link
Member

It’s added to prevent accidental zooming. For example native apps can’t be zoomed either (except by built-in 3rd party accessibility apps) so web apps should not be either, just because they live in a browser.

@DeepDiver1975
Copy link
Member

case closed? @jancborchardt @Volker-E

@Volker-E
Copy link
Contributor Author

@DeepDiver1975 With the input of @jancborchardt it seems that the decision was made earlier.
In detail the decision between being a website or trying to get close to a web app living in a browser.

My standpoint is, that people are used to zooming in the browser on the smartphone and the case of accidentally zooming is far more uncommon than the wish to zoom in, in order to have ease of interaction.
That applies not only to users with visual disabilities or impairment, let's take for example the ownCloud Demo at https://demo.owncloud.org/index.php/apps/files/#//Demo%20Image%20-%20ccc.jpg

With the current settings you're not able to zoom in on the image, although that's a very common usecase of image apps.
Therefore I'd propose to try a higher maximum-scale setting/getting rid of maximum scale setting and see how many users giving feedback on that as bug rather than feature.

@jancborchardt
Copy link
Member

I totally agree with the zooming in for images usecase – and we should do that rather than allow zooming in general. I think @oparoz implemented that in the new Gallery app. @oparoz does that work on mobile?

@oparoz
Copy link
Contributor

oparoz commented Mar 23, 2015

Pinch to zoom works on iPads only unfortunately. I'd love it if someone could make it work on more devices.
Zooming and Fullscreen modes are available via keyboard shortcuts. It works on mobile, but you need a keyboard... and zooming mode alternates between filling the screen and real-size, so you can't zoom in on a panoramic picture which is filling the screen on a mobile device which is not an iPad.
Requests can be filled here: https://github.com/interfasys/galleryplus/issues

@jancborchardt
Copy link
Member

@oparoz aren’t there other js zoom/gesture libraries which work on other devices as well?

@oparoz
Copy link
Contributor

oparoz commented Mar 23, 2015

@jancborchardt - the problem is that it's the bigshot library which is controlling the gestures and it's apparently not detecting all possible events. I played with the library once, but couldn't figure it out.
It's also possible there is a conflict between the standard controls and the library.

@jancborchardt
Copy link
Member

I’m closing this since the general interface should just not be zoomable. However, the Gallery or other viewers should make it possible to zoom images.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants