| Commit message (Collapse) | Author | Age | Lines |
|---|
| |\ |
|
| | |
| |
| |
| | |
So version 2.4.1 has no translation changes, putting back straight after.
|
| |/
|
|
|
| |
Adds some div wrappers round the non category bit of the form so we can
then hide easily.
|
| |
|
|
|
|
| |
replace_query_parameter() was stringifying select multiples, meaning
they were incorrectly recorded by the pushState and thus breaking on
navigation.
|
| |
|
|
| |
Fixes mysociety/fixmystreet-commercial#1131
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
There is no need for #front_stats to always be nested inside of #front-howto.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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!
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
Couple of texts have newlines in them, and may change anyway.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Collideoscope doesn't have fixed reports so only add a line for fixed
reports if there is data.
|
| |/
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
GeoJSON is used by the /reports page now, not KML.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
It is possible to get here on e.g. a /report/new page load where the
asset is being shown but hasn't yet been added to the map.
|
| | |
| |
| |
| |
| |
| | |
Confusion over client/server side filtering meant Bristol was filtering
client-side on an attribute it was not asking to be returned by the
server.
|
| |/ |
|
| |
|
|
|
|
| |
Add by_category output to the /report/new/ajax call, containing all the data
that /report/new/category_extras returns for one category. Then alter the JS
to use that data immediately when needed.
|
| |
|
|
|
| |
If a layer doesn't have attributes the set_fields_from_attributes
function dies because $.each doesn't like undefined things.
|
| |
|
|
| |
Include instructions to fork to prevent this happening again.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Allows cobrands to customise message displayed, and includes
description in GeoJSON feature properties.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Bing no longer shows it at zoom level 11.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #2016.
When you load a page that includes either a problem report, or is
centered on a location, the "Report a problem" button in the nav bar
(that normally takes you to the homepage) becomes a "Report a(nother)
problem here" button, that leads directly to the new report form
for the location in question.
On full map pages (/around and any /report/<id> pages loaded via it)
the reporting form will be rendered client-side, avoiding a full page
reload.
On pages lacking the full map (eg: missing fixmystreet.bbox_strategy),
namely /reports/<area> and any /report/<id> page that hasn’t been
client-side loaded via /around, we fall back to a server-side page load.
Finally, as you’d expect, the text and URL for the button dynamically
update as you move around the map, or switch between the different
client-side states of the reporting flow.
We also hide the button entirely when you’re reporting a problem,
which was something suggested a long time ago.
|
| | | |
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| | |
Part of #2012.
Should make it much quicker to report multiple problems in the same
location, one after the other.
|
| |\ \ |
|
