| Commit message (Collapse) | Author | Age | Lines |
... | |
|/
|
|
|
|
|
|
|
|
|
| |
Reduce the space between checkbox and label, so the text isn't lost if
the page is zoomed in. Fixes #2411.
Replace the creator_fixed question with segmented control to match the
full questionnaire, and the admin verified checkboxes with inline-text
as they need no padding. Having done that, all uses of .inline are now
on their own lines, so no post-padding is needed any longer, but we’ll
leave some in case of future use.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
There’s no need for this `--reports` to be there, so let’s start phasing
it out.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`_item_expandable.html` is an alternative to regular list items, where
you can display extra information on the first click on the item, and
then also, optionally, offer a further action, as a separate button.
Right now the expandable list items aren’t used anywhere, but we’ll
soon be using them in the duplicate report suggestion UI for council
staff and the public.
|
| |
| |
| |
| |
| | |
Moving the 4em padding from _layout.scss to _base.scss helps separate
the content on /report/<id> and /report/new pages from the nav below.
|
|/ |
|
|
|
|
| |
Makes sure the logo looks nice on devices with high resolution.
|
|
|
|
|
|
|
|
| |
The previous approach of filtering features that match one of many
values worked client side for e.g. GeoJSON format WFS layers, but crashed
when attemping to build the XML request for server-side feature filtering
(e.g. Bristol). This code instead builds a proper Logical filter which
OpenLayers can use in both situations.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
The behaviour should be the same whether “Show older” or “Show older
reports” is clicked, but only the latter was updating the URL.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Update database to store an array of IDs rather than only one;
consequential changes to the admin and the dashboard to allow
selection.
|
|/ |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Sometimes IE11 appears to have one, some interaction with appcache
iframe? Not sure, but not worth tracking it down.
|
| |
|
| |
|
|
|
|
| |
This will also be used by the moderation conflict code.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a question to check whether a flytipping report concerns
flytipping on a road or not. Client-side, it is asked when a road is
selected and destination adjusted according to the answer; server side
it uses the answer to direct any both-tier submissions (from e.g.
non-JavaScript or phone app).
|
|/
|
|
|
| |
Missing a "&" in base selector, so wasn’t being applied,
and use flex directly on layout rather than floating.
|
|
|
|
|
|
|
|
|
| |
If a report is started on a road in the WinterRoutes asset layer in the
"Snow and ice problem/winter salting" category, an extra guidance
message is shown beneath the category UI with a link to the council's
gritting schedule.
Fixes mysociety/fixmystreet-freshdesk#25.
|
|
|
|
|
|
|
| |
Add in validation to check names, email and phone numbers don't exceed
maximum lengths permitted by HIAMS.
Fixes mysociety/fixmystreet-commercial#1244
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As the selected feature is a clone (so it survives e.g. layer reloading
from server after a pan), we need to compare the asset ID field instead
to see if we already have a match, to prevent a double select().
This also fixes a bug where an auto-selected asset would, after picking
a different asset, reshow the selected pin image onmouseout, due to the
way OL was storing old hover state internally.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add layers for:
* Road crossings
* Belisha Beacons
* Gullies
* Street signs
* Bollards
|
| |
| |
| |
| |
| |
| |
| | |
Not all the layers use the same attribute for the feature code so add
and use a config option to set this, and extract out the style map
settings so we can change them to use the correct attribute for the
label.
|
|/
|
|
|
|
|
| |
use the asset code to determine what sort of type the asset is for
displaying the 'you have selected $type $code' message. Also, pull this
out into a new set of defaults so we can apply it across multiple asset
types.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Simplify markup required for the status banner.
* Simplify styles - the banner is now identical on all screen sizes.
* Move the banner from `report/display.html` into `report/_main.html`
so that it can appear after `.problem-back` in the source order.
* Use real pin icon instead of `pin-flat-white-small.png`.
* Set a default `$col_fixed_label` colour in `_base.scss`, so cobrands
don’t have to define it themselves if they’re happy with green.
* Introduce `$col_fixed_label_light`, with a sensible default for all
cobrands, even ones that have a custom `$col_fixed_label`.
* Remove `$col_fixed_label_dark` – no longer needed.
|
|\ |
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
|
| |
The core validation_rules.js is not included on e.g. the front page.
|