| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
When a report is pulled in via ajax, it means there are then two sets of
login flow buttons on the page, and the JS setup only attaches to the
first of these.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves the email input from `user_loggedout.html` closer to the
password inputs in `user_loggedout_{by_email,password}.html`, because
we want to emphasise the connection between your login email/username
and your password, and, now that only one "Yes I have an account / No
I do not have an account" fieldset is displayed at a time, there was
no reason to ask for the email/username up front.
This, however, now means the form includes two username inputs, so:
* `Report/New.pm` and `Report/Update.pm` now pick the first non-empty
username param and use that.
* `user_loggedout_email.html` now expects a `name` parameter, so that
we can give the two username inputs unique ids in the markup.
Also:
* The "optional" phone and email inputs in user_loggedout_by_email.html
are printed *after* the main username input if SMS login is enabled
(since one or other of them is unhidden by javascript, based on
whether you entered a phone number or and email address into the
"username" input, and it would look weird to have an input become
unhidden *above* the input you’re currently editing).
|
| |
| |
| |
| | |
Co-authored-by: Zarino Zappia <zarino@mysociety.org>
|
| | |
|
| |
| |
| |
| |
| |
| | |
This was a cute space-saving feature at the time, but the layout made it
look like the button was specific to that input, rather than submitting
the whole form. Make similar buttons full width, and improve spacing.
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\ |
|
| | |
|
|/
|
|
|
|
| |
When a user selects a street light display the street light column
number beneath the asset on the map. Also replace the "Select a street
light" text with an indication of which street light has been selected.
|
| |
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
If set then when the user creates a new body report it will prefill the
report title and description with some basic text.
For mysociety/freshdesk#23
|