aboutsummaryrefslogtreecommitdiffstats
path: root/web/js/map-fms.js
diff options
context:
space:
mode:
authorZarino Zappia <mail@zarino.co.uk>2018-07-27 15:20:02 +0100
committerZarino Zappia <mail@zarino.co.uk>2018-08-07 16:51:40 +0100
commit4e8e8d3b4912ec6552ae5290dbf47cf1d5968107 (patch)
treedda7d89f186f6f7347f5b63232656fbefd882c03 /web/js/map-fms.js
parent0f4a56c8654262d49a18b04e0517f99561da565f (diff)
"Report a problem here" button in nav when viewing a location
Fixes #2016. When you load a page that includes either a problem report, or is centered on a location, the "Report a problem" button in the nav bar (that normally takes you to the homepage) becomes a "Report a(nother) problem here" button, that leads directly to the new report form for the location in question. On full map pages (/around and any /report/<id> pages loaded via it) the reporting form will be rendered client-side, avoiding a full page reload. On pages lacking the full map (eg: missing fixmystreet.bbox_strategy), namely /reports/<area> and any /report/<id> page that hasn’t been client-side loaded via /around, we fall back to a server-side page load. Finally, as you’d expect, the text and URL for the button dynamically update as you move around the map, or switch between the different client-side states of the reporting flow. We also hide the button entirely when you’re reporting a problem, which was something suggested a long time ago.
Diffstat (limited to 'web/js/map-fms.js')
0 files changed, 0 insertions, 0 deletions