Use a submit button in budget executions filters
As mentioned in commit5214d89c8, there are several issues with submitting a form when a `<select>` tag changes. In particular, keyboard users might accidentally fire the event while browsing the options, and screen reader users will find a form with no obvious way to submit it. In this case, there's an extra problem: in commitbe8a0dbe8we added a second `<select>` field to this form, which also submitted on change. Sometimes users changed one of the values and wanted to change the other value as well before submitting the form. However, it wasn't possible, because we would submit it before they had a chance to change the second value. So now we don't submit the form on change and add a submit button. This is similar to what we do in the "Advanced filters" we use in several places.
This commit is contained in:
@@ -669,6 +669,7 @@ es:
|
||||
back: "Volver a mi contenido"
|
||||
shared:
|
||||
edit: "Editar"
|
||||
filter: "Filtrar"
|
||||
save: "Guardar"
|
||||
delete: "Borrar"
|
||||
"yes": "Si"
|
||||
|
||||
Reference in New Issue
Block a user