aboutsummaryrefslogtreecommitdiffstats
path: root/web/js/duplicates.js
Commit message (Collapse)AuthorAgeLines
* Do not focus on title on duplicate list removal.Matthew Somerville2019-05-28-14/+3
| | | | | Sometimes this can be a long way down, if e.g. extra Open311 questions above.
* Tidy up duplicate fetching code.Matthew Somerville2019-03-28-26/+8
| | | | | | 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.
* Listen for all inspector form duplicate events.Matthew Somerville2019-03-06-2/+2
| | | | | | 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).
* Duplicate suggestion UI when reporting problems.Zarino Zappia2019-02-25-0/+206
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.