You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Right now if you deny the app location access, it seems to just assume you're at city hall. This conflicts with the new "Near Me" feature.
Describe the solution you'd like
We should add some logic to keep track of whether or not we have access to a user's location. This would allow us to dynamically enable/disable features based on that data to reduce undefined behavior in the app.
Describe alternatives you've considered
Additional context
Spoke with @affabillyty at the December Hack Night and this seems to be a pretty pressing concern. This will require a follow up ticket specifically for the "Near Me" button to be disabled based on location status.
The text was updated successfully, but these errors were encountered:
One limitation of my current implementation of this is that Firefox "temporary permissions" don't change the permission state like other browsers, so if a user doesn't check the "Remember this option" box on the prompt, it will be stuck in a sort of limbo.
I know we talked about this on standup, so capturing it here for future reference. It seems like we should explore this from a user experience perspective.
In my opinion, this is definitely more of a good-to-have than a need-to-have, so no need to suffer too much if this becomes difficult to explore. I generally appreciate Firefox's approach to location sharing as it helps me when testing to use our default location
Is your feature request related to a problem? Please describe.
Right now if you deny the app location access, it seems to just assume you're at city hall. This conflicts with the new "Near Me" feature.
Describe the solution you'd like
We should add some logic to keep track of whether or not we have access to a user's location. This would allow us to dynamically enable/disable features based on that data to reduce undefined behavior in the app.
Describe alternatives you've considered
Additional context
Spoke with @affabillyty at the December Hack Night and this seems to be a pretty pressing concern. This will require a follow up ticket specifically for the "Near Me" button to be disabled based on location status.
The text was updated successfully, but these errors were encountered: