See https://github.com/openstreetmap/openstreetmap-website/pull/5592#discussion_r1938530806
In practice this should make no difference because lat/lon don't contain any characters that need escaping. But there's still no reason for attempting to escape them twice. You can view, comment on, or merge this pull request online at: https://github.com/openstreetmap/openstreetmap-website/pull/5595 -- Commit Summary -- * Don't apply extra encodeURIComponent to lat/lon search params -- File Changes -- M app/assets/javascripts/index/contextmenu.js (2) M app/assets/javascripts/index/search.js (2) -- Patch Links -- https://github.com/openstreetmap/openstreetmap-website/pull/5595.patch https://github.com/openstreetmap/openstreetmap-website/pull/5595.diff -- Reply to this email directly or view it on GitHub: https://github.com/openstreetmap/openstreetmap-website/pull/5595 You are receiving this because you are subscribed to this thread. Message ID: <openstreetmap/openstreetmap-website/pull/5...@github.com>
_______________________________________________ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
