aboutsummaryrefslogtreecommitdiffstats
path: root/web
Commit message (Collapse)AuthorAgeLines
...
* [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.
* Fix history API bug.Matthew Somerville2018-10-02-9/+17
| | | | | | replace_query_parameter() was stringifying select multiples, meaning they were incorrectly recorded by the pushState and thus breaking on navigation.
* [Oxfordshire] Avoid nav menu CSS overlap for staff on mappageZarino Zappia2018-10-01-2/+7
| | | | Fixes mysociety/fixmystreet-commercial#1131
* [Oxfordshire] Update cobrand to match new OCCLSS style guideZarino Zappia2018-10-01-413/+524
| | | | | The change to web/js/front.js was required because Oxfordshire has no `.report-a-problem-btn`, so the front.js shouldn’t assume it’s there.
* Nicer image replacement for #nav-link mobile menu buttonZarino Zappia2018-10-01-2/+3
| | | | | | | | | | | The large negative text-indent can sometimes cause horizontal scrollbars in Right-to-Left languages, and, in some browsers, can also result in a huge :focus outline being drawn around the button and off to the right of the window. Setting a zero height, padding top, and overflow:hidden is a simpler way to achieve the same thing, and works regardless of text direction, text length, or focus state.
* Reduce specificity of #front_stats CSSZarino Zappia2018-10-01-53/+48
| | | | There is no need for #front_stats to always be nested inside of #front-howto.
* Improve vertical alignment of #main-nav in IE9-11Zarino Zappia2018-10-01-7/+98
|
* Clearer relocation options while you’re reporting a problemZarino Zappia2018-09-19-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.
* Clicking "Report" header links on homepage focusses #pc inputZarino Zappia2018-09-19-1/+13
| | | | | | | Works for both the "Report" button shown in the mobile header, and the "Report a problem" span on the desktop site. Thanks to Louise for suggesting this in mysociety/collideoscope#42!
* Avoid exception if homepage does not include a .report-a-problem-btnZarino Zappia2018-09-19-1/+1
| | | | | | | | Some cobrands (like Collideoscope) don’t have a .report-a-problem-btn in their mobile nav menu, so .querySelector() would raise an exception when we tried to attach an event listener to it. Now we check that the element exists before attaching the listener.
* Handle MultiPolygon geometries for boundary on /reportsDave Arter2018-09-17-1/+2
|
* .js-make-bar-chart now accepts custom chart/bar dimensionsZarino Zappia2018-09-13-2/+4
| | | | | | We needed this for Collideoscope, where we’re displaying small bar charts on the Statistics page, and the default bar height of 30px was much too small when the chart was reduced in size.
* [Bromley] Use service_sub_code codes, not text.Matthew Somerville2018-09-12-5/+5
| | | | Couple of texts have newlines in them, and may change anyway.
* Merge branch 'asset-consolidation'Matthew Somerville2018-09-12-45/+62
|\
| * Move get_select_control/select_nearest_asset inside class.Matthew Somerville2018-09-12-32/+32
| |
| * [Bromley] Use service_sub_code for asset display.Matthew Somerville2018-09-12-1/+17
| |
| * Move check_layer_relevant to layer.relevant.Matthew Somerville2018-09-11-12/+13
| |
* | make fixed reports line on reports graph optionalStruan Donald2018-09-12-11/+16
| | | | | | | | | | Collideoscope doesn't have fixed reports so only add a line for fixed reports if there is data.
* | do not generate labels for empty dashboard graphsStruan Donald2018-09-12-0/+3
|/ | | | | Avoid a JS error if a line graph has no points. This is mostly useful for collideoscope where we only want to show one line.
* [Bromley] Update asset for category changes.Matthew Somerville2018-09-11-5/+29
|
* [Buckinghamshire] Do not report on non-Bucks roadsMatthew Somerville2018-09-10-3/+5
| | | | | | Sending to Bucks reports made on non-Bucks roads was only disabled if Bucks was the only body concerned; flytipping is a concern of both tiers, but reports on non-Bucks roads should still not be sent to Bucks.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 17:05:20 +0000