Open rachelmcr opened 4 years ago
The URL used for Log In with WordPress.com is actually https://public-api.wordpress.com/oauth2/authorize?scope=global
, which redirects to the login screen if the user isn't logged in to WordPress.com in that browser. I'm not sure if we can pass locale to that authentication URL or if the redirect would maintain that locale.
Thanks for clarifying! The current behavior definitely works, so I'd consider this a nice-to-have for the localized experience if it's an option.
It's also potentially worth an API enhancement to support locale if it doesn't yet, but I know that's outside the scope of the clients themselves.
What
Currently, when a user selects "Log in with WordPress.com" we send them to the English WordPress.com login screen no matter what device language they are using. (For example, on Android and iOS where the app itself is localized.)
The WordPress.com login screen detects the device language and offers the user the option to switch to that language, but it would be better to send them straight to the localized login screen. For example, if a user has their device set to Arabic we should send them to
https://wordpress.com/log-in/ar
.Why
Sending the user to the localized login form provides the best experienced for non-English speakers.
How
Current behavior, for example, on iOS with device set to Arabic:
Select Log in with WordPress.com:
End up on WordPress.com login screen in English, with a banner at the top offering the option to switch to Arabic:
Current behavior tested on: