| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
| |
Fixes #2242.
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
|
| |
|
|
| |
Dropped Kerbs and Skips in a Licensing group.
|
| | |
|
| |
|
|
|
|
| |
This is so front-end tests will not try and send email, or
call Gaze. Various co-ordinates have to be updated because
the default zoom level of the map has now changed.
|
| |
|
|
|
|
|
|
|
| |
With the recent login changes, the user form was being hidden after
logging in while leaving an update, meaning you had to click "Continue"
to see the thing it was asking you to check. Refactor the update flow
slightly in this area to be more like reporting, showing the relevant
bit of the user form immediately (and thus also not having it within a
hidden section).
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
| |
Co-authored-by: Zarino Zappia <zarino@mysociety.org>
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
Previously if there was a mix of groups and top-level categories
they weren’t sorted together.
|
| | |
|
| |
|
|
| |
Check selecting a category and selecting a sub category
|
| |
|
|
|
|
| |
Add options to set the cobrand plus related options for co-ordinates,
name and area id to the browser test command. Set BASE_URL to same as
test server, as that is used in e.g. list link output.
|
| |
|
|
|
| |
rather than hardcoding a postcode pull it from ENV to make testing a bit
more flexible for use in cobrand testing
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
replace_query_parameter() was stringifying select multiples, meaning
they were incorrectly recorded by the pushState and thus breaking on
navigation.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Including testing the filters, viewing a report, and pushState.
Plus a mock MapIt handler for returning a GeoJSON outline, to make the
page load. The BASE_URL is also set to the same as the test server, as
that is used in list link output.
|
| |/
|
|
| |
checks what is shown/hidden at various screen sizes
|
| |
|
|
|
|
|
|
| |
The Cypress docs suggest putting machine-specific config into a
`cypress.env.json` file at the same location as `cypress.json`.
(For example, if you want to disable video recording of test sessions
on your machine, but not everyone else’s.) Since this file will be
machine-specific, we don’t want it tracked in Git.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
If you started a new report by clicking the map before the
server had responded with the map list pins, when they did
arrive they would replace the new report pin.
|
| |\ \
| | |
| | |
| | | |
'2016-uk-green-banner-position-test' and '2021-uk-homepage-intent-experiment'
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Present "report" vs "browse" choice at time of postcode entry, so we
can track intent, as part of a temporary experiment into what people
expect to see on the fixmystreet.com/around page.
Google Analytics will be able detect which button was pressed by
looking for the `intent=report` or `intent=report` query string param
in the resulting pageview location.
We supply a *third* submit button, immediately before the other two,
and hidden from visual users and assistive devices, to prevent either
of the "intent" submit values being sent when the user submits the
form via the Return/Enter key.
Part of #2021.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Data collected by #2001 has shown that some people are clicking the big
green "Click map to report a problem" banner on fixmystreet.com/around.
We assume the same is true for other cobrands.
As suggested in #2016, this commit adds a click handler to that banner
element, which will begin a new report at the centre of the screen. It
might not be the exact right location, but the pin can be repositioned
from the /report/new form, and beginning a report is better than just
soaking up the click and doing nothing.
|
| |/
|
|
|
|
|
|
| |
I don't think this check could ever have worked, because items are invisible
if their parent is set to `display: none`, so it would hide the links bar if
it was already hidden, and show it if it was already shown.
Use a js- class for the movement of the feed item into the sub map links.
|
| |
|
