Anomalie #1891
ouvert
2 tabs required after selecting a member from dropdown
0%
Description
When using keyboard navigation, after a emmebr has been selected from the dropdown, user must tab 2 times to continue browsing if he hit enter to select the member (iff user uses tab, everything is fine).
Fichiers
Mis à jour par Guillaume AGNIERAY il y a 5 jours
- Fichier member_dropdown_keyboard.gif member_dropdown_keyboard.gif ajouté
I can't reproduce. On my side, after selecting a member in the dropdown hitting enter, only one tabulation is necessary to continue browsing the form (tested on develop using Firefox and Chrome on the member form, the contribution form and the transaction form).
Mis à jour par Johan Cwiklinski il y a 5 jours
Guillaume AGNIERAY a écrit (#note-2):
I can't reproduce. On my side, after selecting a member in the dropdown hitting enter, only one tabulation is necessary to continue browsing the form (tested on develop using Firefox and Chrome on the member form, the contribution form and the transaction form).
I can reproduce, but I need to wait a bit after hitting enter (if i do enter+tab quickly, navigation works as expected.
Mis à jour par Guillaume AGNIERAY il y a 5 jours
Johan Cwiklinski a écrit (#note-3):
I can reproduce, but I need to wait a bit after hitting enter (if i do enter+tab quickly, navigation works as expected.
Even waiting a few seconds after hitting enter, I still can't reproduce on my side :/
Mis à jour par Johan Cwiklinski il y a 5 jours
Strange :/
On my instance, all tested users have already existing contributions, therefore dates are changed - and I recently fix something on that side (bd86a97ccd08dca0f19c1bb341912ae538a6bf28).
Maybe is that why it does work on your instance and not mine?
Mis à jour par Guillaume AGNIERAY il y a 5 jours
Johan Cwiklinski a écrit (#note-5):
Strange :/
On my instance, all tested users have already existing contributions, therefore dates are changed - and I recently fix something on that side (bd86a97ccd08dca0f19c1bb341912ae538a6bf28).
Maybe is that why it does work on your instance and not mine?
Indeed, it is strange...
Tested users on my instance also have existing contributions and dates are properly changed accordingly.
I tested on the demo and still can't reproduce on my side :(