| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows the inspect form to be submitted when offline, with the data
saved in localStorage, the number of saved forms shown in the banner,
and the forms to be uploaded when back online.
It copes if you go back to a report after having submitted the form, and
if the back-online submission fails due to CSRF failure, retrying once
with a new token.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This:
* On an online visit to /my/planned, caches all shortlisted reports,
their images and static maps in localStorage, with progress banner;
* When a report is added/removed from the shortlist, caches/de-caches
that report;
* When viewing a report page offline, shows that page from the cache
if present (replacing the dynamic map with the cached static map, and
replacing report images with their cached equivalents – it is a shame
to duplicate, but we cannot rely on the browser cache having these images);
* When viewing another page offline, shows an error message but also the
list of shortlisted reports that are cached (again, replacing their
thumbnail images with the cached versions).
|
| | |
| |
| |
| |
| | |
Use a list to store JavaScript files, so it can be shared
between the HTML footer and the appcache manifest.
|
| | |
| |
| |
| |
| |
| | |
The styling applied to the nice front end multi-select dropdowns should
not be applied to the admin multi-select ones, until such time as they
are using the nice select interface too.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| | |
Different categories may have a different list of priorities, so store
them all and update as the category changes.
|
| | |
| |
| |
| |
| |
| | |
- Record state change when leaving update and marking as duplicate
- Change save button wording to match problem state when inspecting
- Make it clearer that updates marking a report as duplicate actually close the report
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Use Problem->pin_data for single report page
- Promote markers_highlight to fixmystreet.maps API
We want to highlight map pins on the duplicate report selection UI, so let's use
what's already there instead of writing something new.
- Make sure duplicate report pins aren’t draggable
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This lets us version and cache-bust it as necessary, plus let
browser decide how to load it, we're always going to need it.
|
| |/
|
|
|
|
| |
Thanks to Dave Tapuska and Chrome team:
https://bugs.chromium.org/p/chromium/issues/detail?id=670942
https://github.com/openlayers/ol2/issues/1510
|
| |
|
|
|
|
|
|
| |
When filtering the map by a category containing spaces, this category wasn't
being carried through to the dropdown on the new report form. Ensuring it's
wrapped in quotes in the jQuery selector fixes the problem.
Fixes mysociety/fixmystreetforcouncils#134
|
| | |
|
| |
|
|
|
| |
The change to remove inline JavaScript stopped the Bromley-specific
tiles from working. Put them back with an extra JavaScript file.
|
| | |
|
| |
|
|
|
|
| |
Allow multiple asset layers, and setting of multiple asset attributes.
[Bristol] Add Bristol asset layers.
|
| |
|
|
| |
Including WFS for forthcoming assets layers.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Includes newest, oldest, least/most recently updated, and most comments.
The default remains the same, which is last updated on /reports, and
newest on /my and /around (the latter plus not-in-view
sorted-by-distance ones).
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The inspect form, if shown, is in a sibling div to the report div,
so make sure that it is shown/hidden as appropriate.
We consolidate the inspect JavaScript setup into one function, so
that it can be called on load, and when pulled in.
|
| |/
|
|
|
| |
- A user can be assigned to any number of its body's categories
- The category ids are stored as a list in the user's extra field
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
This makes it easier to use the map, as the land outside the area is
shaded, rather than the area itself.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
If you were on a body page, selected a report, then another report, the
"Back to all reports" link then had an incorrect URL. Also, going "Back
to all reports" after one report would fetch an incorrect Ajax query of
reports to show (as the URL had not yet been updated).
Both of these are fixed by storing the URL on page load, and using that
for the "Back to all reports" link and the URL used by the Ajax call.
There is still an issue with the URL shown if you filter, then select a
report, then click "Back to all reports", but the contents are okay.
|
| |
|
|
|
|
| |
It turns out that whilst IE9+ defines MouseEvent, it's not in the
form that can be used as a constructor until Edge. To fix this we
check that MouseEvent is a function before using it as one.
|
| |\ |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | |
| |
| |
| |
| | |
This matches the behaviour on /around, and prevents a refresh when
changing the state or category filters.
|
| | | |
|
| | |
| |
| |
| |
| | |
- Also adds add select all/none UI
- Adds admin hint for empty category list behaviour
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* The same template is now used for creating new contacts as well as editing
existing ones.
* Zurich template for editing contacts has been left unchanged for now
* Reputation threshold is included on form
* Fields are in a more intuitive order
* Required fields are marked as such in DOM for client-side validation
* Rename ‘notes’ field to make its meaning clearer
|
| |/
|
|
|
|
|
|
|
|
| |
Clicking the thumbnail on a report admin page was causing the 'rotating photo
will discard changes' alert to appear unnecessarily. This was due to the
data-confirm attribute on the parent <dd>, the meaning of which was changed by
f5b171f.
Fixed by using a different attribute name. Spotted another bug that I think
caused the dialog to never actually be shown with the correct message because
'this' was the form and not the clicked button element.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This lets people filter by multiple categories or states. It uses our
jQuery multi-select plugin to turn the <select multiple>s into little
overlay lists of checkboxes. HTML5 history is also supported.
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want to make sure the extra metadata stored on a problem is kept in sync with
the requirements of the category the report is in. Thus, if a report is moved to
a category that collects extra metadata then the appropriate input fields should
be shown so the inspector can enter the data.
This commit shows the category extra HTML elements for every selectable category
on the inspector page hiding those that don't apply to the selected category. JS
is used to show/hide the extra fields when the category dropdown is changed.
A consequence of the implementation is that any extra metadata from the original
category is lost when the category is changed. Some thought was given to storing
the old values elsewhere in the problem's extra field but I decided against this
for the time being.
For mysociety/fixmystreetforcouncils#45
|
