aboutsummaryrefslogtreecommitdiffstats
path: root/web
Commit message (Collapse)AuthorAgeLines
...
| * [Buckinghamshire] Question for on-road flytipping.Matthew Somerville2019-01-23-1/+27
| | | | | | | | | | | | | | | | 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).
* | Bugfix display of next-steps.Matthew Somerville2019-01-22-8/+2
|/ | | | | Missing a "&" in base selector, so wasn’t being applied, and use flex directly on layout rather than floating.
* [Buckinghamshire] Show guidance message for gritting routesDave Arter2019-01-17-0/+35
| | | | | | | | | 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.
* [Oxfordshire] length checking for names, emails and phone NosStruan Donald2019-01-16-0/+10
| | | | | | | Add in validation to check names, email and phone numbers don't exceed maximum lengths permitted by HIAMS. Fixes mysociety/fixmystreet-commercial#1244
* Switch .description_tips to use flexbox.Matthew Somerville2019-01-11-4/+2
|
* Compare assets on their ID field, not JS object.Matthew Somerville2019-01-04-4/+14
| | | | | | | | | | 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.
* Put find_matching_feature on the layer object.Matthew Somerville2019-01-04-24/+29
|
* Merge branch '1072-reason-for-reporting'Matthew Somerville2018-12-19-0/+20
|\
| * Make who question more prominent.Matthew Somerville2018-12-19-0/+20
| |
* | [Buckinghamshire] add more asset layers layersStruan Donald2018-12-19-1/+101
| | | | | | | | | | | | | | | | | | Add layers for: * Road crossings * Belisha Beacons * Gullies * Street signs * Bollards
* | [Buckinghamshire] allow different feature code attributesStruan Donald2018-12-19-31/+46
| | | | | | | | | | | | | | 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.
* | [Buckinghamshire] change sidebar label depending on asset typeStruan Donald2018-12-19-16/+38
|/ | | | | | | 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.
* Make sure map state stored if filters used first.Matthew Somerville2018-12-14-2/+3
|
* Increase clickable area for "Back to all reports" linkZarino Zappia2018-12-13-2/+2
|
* Modernise report "status" bannerZarino Zappia2018-12-13-201/+46
| | | | | | | | | | | | | * 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.
* Merge branch '2346-unescape-titles'Matthew Somerville2018-12-13-1/+13
|\
| * Don’t escape entities in report titles via ajax.Matthew Somerville2018-12-12-1/+13
| |
* | Merge branch 'bucks-roads-message-tweak'Matthew Somerville2018-12-13-1/+18
|\ \ | |/ |/|
| * [Buckinghamshire] Nicer not-our-road messages.Matthew Somerville2018-12-11-1/+18
| |
* | [UK Councils] Fix undefined body_validation_rules.Matthew Somerville2018-12-11-25/+22
|/ | | | The core validation_rules.js is not included on e.g. the front page.
* Fix issue with multiple button IDs on page.Matthew Somerville2018-12-05-5/+5
| | | | | | 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.
* Make sure form_section_preview set up with ajax.Matthew Somerville2018-12-05-0/+1
|
* Merge branch '642-new-report-flow-changes'Matthew Somerville2018-12-05-47/+127
|\
| * Move email input nearer password input on forms.Zarino Zappia2018-12-05-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
| * Update sign in flow for new reports/updates.Matthew Somerville2018-12-05-20/+109
| | | | | | | | Co-authored-by: Zarino Zappia <zarino@mysociety.org>
| * Prevent horizontal space between sibling block-level buttonsZarino Zappia2018-12-05-0/+7
| |
| * Form submit buttons no longer inline with inputs.Zarino Zappia2018-12-05-0/+7
| | | | | | | | | | | | 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.
| * Simplify category required attribute.Matthew Somerville2018-12-05-7/+3
| |
| * Consolidate the report/update loggedout templates.Matthew Somerville2018-12-05-2/+1
| |
| * Remove form-focus-trigger/hidden behaviour.Matthew Somerville2018-12-04-17/+0
| |
* | Fix moderation without JavaScript.Matthew Somerville2018-12-04-5/+13
|/
* Merge branch 'hide-pin-no-location'Matthew Somerville2018-12-03-0/+3
|\
| * Don't draw a pin for a problem with no location.Martin Wright2018-12-03-0/+3
| |
* | [Bucks] display street light numbers upon selectStruan Donald2018-12-03-1/+73
|/ | | | | | 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.
* Consistent behaviour of ‘problems nearby’ linkDave Arter2018-11-27-24/+33
|
* Restore zoom level when navigating back to /around from /reportDave Arter2018-11-27-2/+51
| | | | Fixes #1649.
* [UK] council specific javascript validationStruan Donald2018-11-26-2/+73
| | | | | | | | | 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.
* Disable two-tap marker highlighting on touchscreensDave Arter2018-11-22-11/+17
| | | | Fixes #2294
* On moderating update, scroll to its top, not page.Matthew Somerville2018-11-21-2/+2
|
* add report_prefill user permissionStruan Donald2018-11-19-2/+1
| | | | | | | 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
* [Bristol] include highways england dataStruan Donald2018-11-19-3/+7
| | | | | | This changes the projection from EPSG:3857, which is not included in the bristol openlayers build, to the identical EPSG:900913 which is, so that the conversion happens.
* [Buckinghamshire] Allow reports on Highways England roadsStruan Donald2018-11-19-1/+28
| | | | | Do not hide the report form if you click on a non Bucks road that is managed by Highways England.
* [UK] send reports on highways agency roads to highways agencyStruan Donald2018-11-19-3/+133
| | | | | | | Includes an option to send to the council instead for e.g. reports on underpasses or bridges. Fixes #736
* Scroll to form top when going to/from moderation.Matthew Somerville2018-11-16-0/+2
|
* Simplify /auth sign in page.Matthew Somerville2018-11-09-1/+39
|
* Tidy up UK council cobrand button style overridesZarino Zappia2018-11-09-11/+23
| | | | | | | | | | | | | | | Given recent changes to the button mixins, now is a good opportunity to clear out some overcomplicated button styling from a few UK council cobrands: Greenwich, Hart, and Oxfordshire. All three referred to `button.green-btn` elements that don’t seem to exist any more, and I couldn’t find a reason for the extra specificity in the `input.green-btn` selectors either. Oxfordshire’s buttons are drastically restyled from the FMS defaults, so its button rules are a little complex. But I’ve tried to make the distinction clearer between buttons we’re having to build from scratch (.btn, .green-btn, etc) and buttons we’re simply re-colouring.
* Remove a few .btn related unnecessary things.Zarino Zappia2018-11-09-8/+0
| | | | .btn--social doesn't do anything, and neither do the text-transforms.
* Make .btn--block work on button and input elementsZarino Zappia2018-11-09-54/+87
| | | | | | | | | The intention of .btn--block is to make the element full width. Because of the weird way browsers handle sizing of form elements, just setting `display: block` on `<button>` and `<input type="submit">` elements wasn’t making them full width. Instead, .btn--block needed to explicitly set a 100% width, and then reset any margins or box-sizing issues that might cause it to overflow its parent.
* Update any lat/lon fields when changed.Matthew Somerville2018-11-09-2/+2
| | | | | Cobrands might include the fields elsewhere, e.g. in moderation. Also only use 6 decimal places.
* Clearer relocation options while reporting.Zarino Zappia2018-11-06-4/+35
| | | | | | | | | | | | | | | | Now that the "Report a problem" link in the nav bar links, more often than not, to the reporting form rather than the homepage, it could be challenging to actually start a new report in a location *other* than the one currently on screen. Rather than adding a link to the homepage, this change hopefully adds a link right at the moment the user expects it – right on the "Report a problem" form. It also gave us an opportunity to reword the "Wrong location" message and give it an icon more suitable for high-dpi displays. Fixes #2238.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 00:26:32 +0000