aboutsummaryrefslogtreecommitdiffstats
path: root/web
Commit message (Collapse)AuthorAgeLines
...
* 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.
* Revert "Clearer relocation options while reporting."Matthew Somerville2018-11-06-35/+4
| | | | This reverts commit ee3c4e05daf3f4df01762ead3d07697a12f13a28.
* [BANES] filter roadworks messages on typeStruan Donald2018-11-06-2/+9
| | | | use symbol code to limit the types of roadworks that show.
* [BANES] limit roadworks.org message by categoryStruan Donald2018-11-06-0/+14
| | | | | use the filter option to only display roadworks message for road related categories
* allow cobrands to filter when roadworks message shownStruan Donald2018-11-06-1/+5
| | | | | add a `fixmystreet.roadworks.filter` option which cobrands can override to control when the message is displayed. e.g. limit by category.
* [BANES] Add roadworks.org layerStruan Donald2018-11-06-0/+66
| | | | Uses same parsing of roadworks messages as Lincs
* [FixaMinGata] Don't scroll report on loadJoe Siltberg2018-11-05-0/+1
|
* Sort category groups correctlyDave Arter2018-11-02-0/+11
| | | | | Previously if there was a mix of groups and top-level categories they weren’t sorted together.
* Merge branch '2080-nav-fg-rename'Matthew Somerville2018-10-25-78/+88
|\
| * Rename nav SCSS variable names.Matthew Somerville2018-10-22-78/+88
| | | | | | | | | | Anything using old names should still work as long as they included the mixins file.
* | Allow multiple JS dropzones on a single page.Matthew Somerville2018-10-22-4/+10
|/ | | | | As well as the original form using #form_photo, add Dropzone to any form with a .js-photo-label in it.
* [Angus] Remove cobrand.Matthew Somerville2018-10-10-1403/+0
|
* reselect subcategory selects on /report/newStruan Donald2018-10-09-2/+6
| | | | | | | | | | | | If /report/new is opened directly then the fixmystreet.reporting_data is not set, but the categories are already in place. These are then replaced when update_pin is called. If this has been triggered by clicking on a category with a subcategory this replaces the category selects but did not correctly reset them. By saving any selected value in the main category select we can correctly reset this and hence the display of the subcategory select. Fixes #2276
* [BANES] Branding for HTML emailsZarino Zappia2018-10-08-0/+0
|
* Merge branch 'dashboard-update-csv-export'Matthew Somerville2018-10-05-1/+16
|\
| * More efficient horizontal spacing in dashboard-options-tabsZarino Zappia2018-10-03-1/+16
| |
* | [Oxfordshire] Only run PROW code in Oxfordshire.Matthew Somerville2018-10-04-1/+5
|/
* Clearer relocation options while reporting.Zarino Zappia2018-10-03-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.
* Merge branch 'version-2.4.1'v2.4.1Matthew Somerville2018-10-03-35/+4
|\
| * Revert 50693857 “Clearer relocation options...”Matthew Somerville2018-10-03-35/+4
| | | | | | | | So version 2.4.1 has no translation changes, putting back straight after.
* | [Oxfordshire] display message if user selects PROW categoryStruan Donald2018-10-03-0/+23
|/ | | | | Adds some div wrappers round the non category bit of the form so we can then hide easily.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-31 11:22:44 +0000