| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This reverts commit ee3c4e05daf3f4df01762ead3d07697a12f13a28.
|
|
|
|
|
| |
Anything using old names should still work as long as they included the
mixins file.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
So version 2.4.1 has no translation changes, putting back straight after.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
|
| |
Part of #2012.
Should make it much quicker to report multiple problems in the same
location, one after the other.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2180.
Input placeholders are a generally problematic UI convention, and we’ve
accidentally started using them in more and more parts of FMS over the
last few years.
In some cases, the placeholders simply repeated text from the input’s
existing label element. In cases like those, the placeholder attribute
could just be removed.
In other cases, we broke the placeholder text out into a .form-hint
element, between the input and its label, so that the text is easily
accessible and falls into the top-to-bottom reading flow.
Notable changes:
* Form hint on main postcode search form, instead of placeholder.
* Form hint on alert search form, instead of placeholder.
* Form hints in reporting form (problem summary and description),
instead of placeholders.
* Removed placeholders from most login/password inputs.
* The character limit for "Inspector" report updates is no longer
displayed in the textarea placeholder.
* Form hints now `#666` grey, and better spaced when immediately
following a label element.
|
| |
|
|
|
|
| |
This was caused by the header overlapping the state banner
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Useful for simple tables like the cookie lists on Privacy Policy pages.
|
|
|
|
| |
Fixes #2124.
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#231
|
|
|
|
|
| |
Only the contacts table gets a button added to toggle the display
of deleted rows; elsewhere the rows need to continue to be shown.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since #map_sidebar no longer disappears behind #site_header, there is
no need for .internal-link-fixed-header to compensate for the height
of the header. Just an arbitrary 2em offset is enough to prevent it
butting up against the top of the #map_sidebar scrollable element.
Meanwhile, moving the .internal-link-fixed-header anchor element to
the top of its parent list item means it no longer has to compensate
for the height of the moderation form elements, because those elements
(indeed, the entire list item <form>) now comes *after* the anchor.
Fixes mysociety/fixmystreet-commercial#1027.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The easy thing first - IE appears to 'stack' :before entries, so if a
stylesheet is loaded multiple times (e.g. due to critical CSS loading
on the front page), a font-size of 2.5em gets multipled. Switching to
rems fixes this.
The preload polyfill in IE8/9 loads the base stylesheet as if it were
after the layout stylesheet, which breaks the navigation display. The
polyfill has a new version which is somewhat simplified, updating the
existing <link> rather than creating a new one, so we upgrade to that
plus a PR to prevent browser hanging.
However, in IE8 this now incorrectly uses the print styles on screen,
meaning the navigation and footer disappear. So use an IE conditional
comment to just cut IE8 out entirely. This means we can also cut down
the polyfill somewhat.
|
| |
|
| |
|
|
|
|
|
|
|
| |
If JavaScript is enabled hide the deleted contacts from the list on the
body page. Display as normal if no JavaScript.
Fixes #1962
|
|
|
|
|
| |
Makes a bit more sense to group those relating to sending/receiving
comments together and those relating to fetching comments together.
|
| |
|
|
|
|
|
| |
Fixes positioning bugs in all versions of IE due
to calculating the wrong horizontal position.
|
| |
|
|
|
|
| |
Fixes broken aspect ratio in IE10
|
|
|
|
|
|
|
|
| |
Fixes #2018 by making the #sub_map_links bigger.
But the greater win here is that we’re using fewer ID selectors in our
CSS, and both #sub_map_links and #mob_sub_map_links now share the same
styling – both of which are good for maintainability.
|
|
|
|
| |
Fixes mysociety/fixmystreet-commercial#943.
|
|
|
|
|
|
|
|
|
|
| |
The "coerce pin ID to integer" behaviour to fix a previous issue was
coercing undefined to NaN, which then caused other problems with the
new report pin, such as fading out when hovered, and being the wrong
size.
Also improve the cursor handling, showing the grab/ grabbing cursors
where available.
|
|
|
|
| |
The change to base in fc172603 affected the layout display.
|
| |
|
|
|
|
|
|
|
|
| |
The tiny buttons could prove hard to trigger, especially on touchscreen
devices, and with large screens now more commonplace, there’s no reason
not to give them a few more pixels.
One of a number of enhancements suggested in #1462.
|
|\ |
|
| | |
|
|/
|
|
|
| |
A top banner (for e.g. offline, or just custom display) could be used
by any cobrand, so remove the need to add an extra line of CSS.
|
|
|
|
| |
Fixes part of mysociety/fixmystreet-commercial#965.
|
| |
|
|
|
|
| |
This will also be used by /reports/[body]/summary in a bit.
|
|
|
|
| |
Fixes #1589.
|
|
|
|
|
|
|
|
| |
Display a list of the email addresses used to contact the council on the
council dashboard. Does not display emails if the council has an
integration, rejects FMS reports or is currently turned off.
Fixes mysociety/fixmystreetforcouncils#941
|
|
|
|
| |
An experiment towards fixing #525.
|