- Issue created by @AlfTheCat
- 🇹🇭Thailand AlfTheCat
Another UX issue I would like to add, is that with the current implementation, refreshing the page prompts a "confirm form re-submission" dialog to the end user. The problem with that is, is that in doing so the user actually re-submits the original location data. So if the user moves from point A to point B, and refreshes the page in their browser, instead of seeing updated proximity values based on their new location B, they see the old data from point A. This is completely counter-intuitive to the end user because they expect that a page refresh would show the data based on their new location.
- 🇮🇹Italy itamair
Thanks @alfthecat for reporting this.
As immediate feedback I would highlight to you that the "Client Location Origin" (id: geofield_client_location_origin) is a @GeofieldProximitySource Drupal Plugin, like any other @GeofieldProximitySource ones (that implement GeofieldProximitySourceInterface),
and that you, as everybody else, can implement your own @GeofieldProximitySource Drupal Plugin in a custom module,
and thus try to implement all the features that you further require as custom.I might find some spare time to better go through this feature request of mine (I couldn't reproduce your use cases yet, and make it more mine) but in the meanwhile I welcome you to eventually contribute in start developing / drafting yourself the @GeofieldProximitySource plugin & related functionalities that you have in mind / need ...
- 🇹🇭Thailand AlfTheCat
Hi @itamair, thanks very much for your attention to this and your guidance. I'm indeed looking into developing and contributing a solution and it's very helpful to know about the @GeofieldProximitySource Drupal Plugin.
My thoughts so far are to look at a javascript based implementation of storing a visitors lat/long in
Localstorage
and passing that data on to views.I will study the plugin and it will be great if I can share a working implementation here once I establish one, and maybe get your thoughts on it.
- 🇮🇹Italy itamair
Sure @alfthecat ...
The Localstorage (or may be better Sessionstorage) approach looks promising, but I don't know if it could be kept embedded only in the new dedicated @GeofieldProximitySource Drupal Plugin.
If not, may be you could also propose some patch / Merge Request to the whole Geofield Proximity system itself ...Please keep me updated on your progresses, Pretty curious about those.
- 🇹🇭Thailand AlfTheCat
Awesome @itamair, excited to work on this. I'll keep you posted, thanks very much.