-
Notifications
You must be signed in to change notification settings - Fork 27
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
ios 9 silently fails if location services turned off #5
Comments
Perhaps we can add an attribute to turn on a visual warning / error message that can be toggled on or off with a attribute to geoCheck().
|
Or we could make a more universal geoError() which could be hooked into everything that has a visual message. I might make the argument for letting the user handle the visual side of things in case they want something more custom than what we would provide. Thoughts? |
+1 for letting the user decide how to display errors. I would probably remove all |
I mean I figured it out pretty easily.... but I feel like someone with less It just seems like overkill to set up remote console logging, which is not So I guess its a question for a novice web developer what should we do to
Thoughts?? On Sun, Jun 26, 2016 at 2:41 PM, Ben Moren [email protected] wrote:
Tyler Stefanich |
I agree that remote logging is a huge pain. Anything we can do to get around that would be ideal. To your thoughts, yes, lets do all 3. I think this is the simplest way around for novice developers. We can make a catchall error function which throws a visible alert which can be toggled on/off which is enabled by default. If on, visible alert is shown in addition to a p5 style error thrown, if off, the error as derek pointed out above is thrown only. |
When testing on ios 9 and if the users Settings -> Privacy -> Location services -> Safari are set to "Never" the webpage will not prompt for permission. There should maybe be a more explicit alert that notifies vs a console log. Will look into testing to see if we can do something more direct for ios / mobile.
The text was updated successfully, but these errors were encountered: