When connecting to MX Bank via the connect widget, the password field appears above the username field on the login screen. Users expect username first, then password — the current ordering is confusing.
The widget renders credentials in the order returned by the API without sorting by display_order. In src/views/credentials/Credentials.js, credentials are rendered via .map() with no sort. If the API returns password before username in the array, the widget displays them in that order.
The credential response schema includes display_order (username=1, password=2), but it's never used for ordering.
I'm not saying this is the issue but from what I can see in the repo, its one potential cause.
Cheers
Emmet
When connecting to MX Bank via the connect widget, the password field appears above the username field on the login screen. Users expect username first, then password — the current ordering is confusing.
The widget renders credentials in the order returned by the API without sorting by display_order. In src/views/credentials/Credentials.js, credentials are rendered via .map() with no sort. If the API returns password before username in the array, the widget displays them in that order.
The credential response schema includes display_order (username=1, password=2), but it's never used for ordering.
I'm not saying this is the issue but from what I can see in the repo, its one potential cause.
Cheers
Emmet