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

Mobile VoiceOver doesn't allow small step sizes relative to large ranges #139

Open
jessegreenberg opened this issue May 20, 2019 · 4 comments

Comments

@jessegreenberg
Copy link
Contributor

From phetsims/sun#495, we need to submit a bug report to Apple about this. If the step attribute for an input of type range is too small relative to the entire range of the input, the element won't receive alternative input.

@jessegreenberg jessegreenberg self-assigned this May 20, 2019
@terracoda terracoda self-assigned this May 28, 2019
@terracoda
Copy link
Contributor

@jessegreenberg , is this issue about the custom small-step with the Shift key, or a control that has a small range and a default "smallish step size"?

@jessegreenberg jessegreenberg changed the title VoiceOver doesn't allow small step sizes relative to large ranges Mobile VoiceOver doesn't allow small step sizes relative to large ranges May 31, 2019
@jessegreenberg
Copy link
Contributor Author

This bug seems to happen when a slider has a very large range relative to a very small step size. We encountered this specifically in gravity-force-lab where the slider range spans 9 billion and the step size was 1. In this case, mobile VoiceOver failed to send DOM events to the browser when the user changed values with gestures. We fixed this in gravity-force-lab by making the step size 1 billion in this case.

Outside of a PhET simulation, a slider with a step size of 1 with a range of 9 billion would be very bad. But VoiceOver should still handle that case gracefully, so we would like to submit a bug report to Apple about it.

@jessegreenberg
Copy link
Contributor Author

I just submitted a bug report to Apple, lets see if anything comes of it!

@jessegreenberg
Copy link
Contributor Author

Apple responded by requesting we resubmit the report using Feedback Assistant and submitting any generated files that service provides.

@terracoda terracoda removed their assignment Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants