| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| |
| | |
As there are two category drop-downs in this situation (one in the
hidden reporting form, one in the inspect form), the correct entry
needs to be specified.
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
The base layer does this transformation,
so I am not sure what this was for.
|
| |
| |
| |
| |
| |
| | |
Change the way we set the BBOX strategy for the map layer as otherwise
when we check for bbox_strategy in display_around this is set but has
not been associated with a layer so .activate fails.
|
|/ |
|
|\ |
|
| | |
|
|/
|
|
| |
We retain the code as it is updating the URL on map move.
|
|
|
|
| |
Also update lat/lon parameters to match JS.
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
If autofill on Chrome is turned on and has saved the user's login it
can autofill the user's email address in the report title, so add
validation to make sure the title does not look like an email.
Fixes #2570
|
|
|
|
|
| |
Add more checking for map things so e.g. on a skipped map page
we stop getting JavaScript errors given there is no map present.
|
| |
|
| |
|
|
|
|
|
| |
Sometimes this can be a long way down,
if e.g. extra Open311 questions above.
|
|
|
|
|
| |
Add a WMTS config to use Buckinghamshire's own map tiles to display
house numbers.
|
|
|
|
|
|
| |
Run immediately, not onready, so the category change listener is in
place; listen to a better event, removing need for a debouncer; don't
look up if empty category.
|
|
|
|
|
|
| |
The form may be brought in via JS, so we have to add an event to
something that will always be there (or alternatively set up when
pulled in, which was the old pre-duplicates.js behaviour).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previously staff-only fixmystreet.set_up.manage_duplicates() has
been promoted from staff.js to its own file so that we can use it to
display the duplicate suggestions on the `/report/new` form.
render_duplicate_list (the old refresh_duplicate_list) no longer filters
or slices the reports_list returned by the ajax call, since it turns out
the server handles all of that (`sub _nearby_json` in `Report.pm` and
`sub nearby` in `Nearby.pm`).
Since the expandable list items include the "fancybox" image previews,
the fancybox CSS now has to be included in the `/report/new` page head,
hence the addition of "photo-js.html" in `fill_in_details.html`.
The “Get updates” flow reuses the same JavaScript that handles the
submission of the "Get updates" drawer at the bottom of around pages.
|
|
|
|
|
| |
The behaviour should be the same whether “Show older” or “Show older
reports” is clicked, but only the latter was updating the URL.
|
| |
|
|
|
|
|
|
| |
Remove the server-side zoom-in-url fix, instead use an ArgParser
subclass to default to the provided data if nothing in URL. Then
we can switch to using short lat/lon in geocoder URLs.
|
|
|
|
|
|
| |
Fixes #2242.
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
|
|
|
|
| |
So it can run even when fixmystreet.js is not loaded.
|
| |
|
|
|
|
| |
The core validation_rules.js is not included on e.g. the front page.
|
| |
|
|
|
|
| |
Fixes #1649.
|
|
|
|
|
|
|
|
|
| |
use the bodies array of reporting_data to check if there is council
specific javascript validation and, if so, load that into the JS
validation rules.
This does mean we reset the validation rules each time you select a
category.
|
|
|
|
| |
Fixes #2294
|
|
|
|
|
|
|
| |
Includes an option to send to the council instead for e.g. reports on
underpasses or bridges.
Fixes #736
|
|
|
|
|
| |
Cobrands might include the fields elsewhere, e.g. in moderation.
Also only use 6 decimal places.
|
|
|
|
|
|
| |
replace_query_parameter() was stringifying select multiples, meaning
they were incorrectly recorded by the pushState and thus breaking on
navigation.
|
|
|
|
|
|
|
| |
Works for both the "Report" button shown in the mobile header,
and the "Report a problem" span on the desktop site.
Thanks to Louise for suggesting this in mysociety/collideoscope#42!
|
|
|
|
|
|
|
|
| |
Some cobrands (like Collideoscope) don’t have a .report-a-problem-btn
in their mobile nav menu, so .querySelector() would raise an exception
when we tried to attach an event listener to it.
Now we check that the element exists before attaching the listener.
|
| |
|
|
|
|
|
|
| |
We needed this for Collideoscope, where we’re displaying small bar
charts on the Statistics page, and the default bar height of 30px
was much too small when the chart was reduced in size.
|
|
|
|
|
| |
Collideoscope doesn't have fixed reports so only add a line for fixed
reports if there is data.
|
|
|
|
|
| |
Avoid a JS error if a line graph has no points. This is mostly useful
for collideoscope where we only want to show one line.
|
| |
|
|
|
|
| |
Bing no longer shows it at zoom level 11.
|
|\ |
|