| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
| |
In Firefox/Edge on Windows, having a translucent stroke causes a large
slowdown in page painting.
|
| |
|
|
|
|
| |
Add title, image and also favicon
Fixes mysociety/commercial-staging#1834
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Once a location is fixed, we never want to regenerate the Highways
England question, as that can lose the selected category. Store the
location regardless of the HE question answer, so any category
change, as opposed to a location change, does not do anything.
We also do not want to clear category_meta, as that is where the extra
data fields appear.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Instead of sending off-road flytipping reports to the district, now that
Buckinghamshire is unitary we instead recategorise them into a new email
specific “Flytipping (off-road)” category which is handled in the same
way as other ex-district categories with the borough_email_addresses
cobrand feature, and omitted from the dropdown by the
categories_restriction cobrand method.
|
| |
|
|
| |
New unitary branding, and remove County from name.
|
| |
|
|
|
| |
Without this check, it is possible for calls to overlap and end up with
a situation whereby both the duplicate list and the form are hidden.
|
| |
|
|
|
| |
The server is now returning HE categories for us near a HE road, so
display/hide them as appropriate.
|
| |
|
|
| |
[HE] Deal with only_body same way TfL does.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Big purple survey banner, which is hidden by default, and shown on 40%
of pageloads, by JavaScript.
Works on both the static pages, and the map pages.
Clicking the CTA button, or the close icon, hides the banner and sets
a cookie so that the banner isn’t shown again on that device.
Banner is always hidden during the mobile reporting flow.
Fixes #2928.
|
| | |
|
| |
|
|
| |
To reduce the number of reports that are arriving without a site code
|
| |\
| |
| |
| | |
'origin/issues/commercial/1659-bromley-shortlist-css-bug'
|
| | |
| |
| |
| |
| |
| |
| | |
Brings Bromley more in line with how other cobrands do their button
styling, and also fixes mysociety/fixmystreet-commercial#1659 (where
Bromley’s high-specificity input styles were causing the shortlist
"star" input to display as a regular button).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A couple of small fixes to tidy the output of button-variant() and
make it easier to style up flat, borderless buttons.
* If $bg-top and $bg-bottom are identical, no linear-gradient() will
be generated. Same goes for $hover-bg-top and $hover-bg-bottom.
* If $border or $hover-border are `false`, then it’s assumed you don’t
want a border, and `border: none` will be generated.
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes a bug where the new tree plantings group was requiring a tree
group to be selected, which isn't the desired behaviour.
The bug was caused by the group layer not having the same `relevant`
function as the points layers. This adds the shared bits into a shared
config that the assets both use.
Also hide the asset item message for request to plant a new tree
category.
|
| |
|
|
|
| |
We always want a tree code for tree reports, so add the code needed to
make the asset selection step mandatory.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want to plant trees where there are already trees, so we add a
separate layer for new tree requests, and disable pin snapping for that
layer.
This adds a new option for layers named "relevant". If provided it will
be called with an options object, allowing you to check ".category" and
".group" and return a boolean for whether you want to display the layer
based on the passed options.
Note: You still need to provide an "asset_group" option even if you use
the "relevant" option as this is used elsewhere.
The "regular" tree-points layer uses this to exclude just the new trees
subcategory from being displayed.
|
| |
|
|
| |
Two layers, one for tree points, the other for tree groups.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
Rather than setting a min_resolution on all of the cobrands just set a
default in web/cobrands/fixmystreet/assets.js. This means that assets
will appear at all zoom levels, which seems like what we want to happen
most of the time.
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a line asset spans two tiles it seems like it's included in both
tiles which means you end up with it added to a layer twice. This means
you get two overlaid identical assets which, when combined with low
opacity colours produces inconsistent colours. This uses the `fid` to
check for duplicates on adding.
|
| | | |
| | |
| | |
| | |
| | | |
If the options to either road or asset layer include a `class` attribute
then use the Layer class there, otherwise the defaults.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Hard code the resolution as it only ever used the one value which isn't
the same in the 27700 based map. This is to avoid pulling in asset
groups.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Basic config and setup files for using WMS based map tiles. These still
require config in appropriate cobrand perl and javascript files
|
| | | |
| | |
| | |
| | | |
Non-JS clicking does not work if map tiles are scaled.
|
| |/ /
| |
| |
| |
| |
| | |
We already had these but labeled as EPSG:900913 which is the same as
3857. However, we tend to use 3857 as not all map servers recognise
900913.
|
| | |
| |
| |
| | |
Easier working with CSP headers.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
