Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feat]: Use navigator.languages instead of .language to handle an array of user preferred languages in prioritized order #752

Open
Aspvik opened this issue Nov 9, 2024 · 0 comments
Open

[Feat]: Use navigator.languages instead of .language to handle an array of user preferred languages in prioritized order #752

Aspvik opened this issue Nov 9, 2024 · 0 comments
Labels
enhancement New feature or request triage yet to be reviewed

Comments

@Aspvik
Copy link

Aspvik commented Nov 9, 2024 •
edited
Loading

Description

As the title suggests I suggest to use navigator.languages instead of .language when autoDetect is set to "browser" in order to accomodate for user preferred languages. Maybe .language is not available as a translated language, but languages[1] is.

Thanks for a great product!

Proposed solution

No response

Additional details

No response
@Aspvik Aspvik added enhancement New feature or request triage yet to be reviewed labels Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request triage yet to be reviewed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Aspvik