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.

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

Element Desktop does not understand config.json saved with UTF8 BOM encoding #1788

Open
Twi1ightSparkle opened this issue Jul 19, 2024 · 1 comment
Labels
A-Config O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@Twi1ightSparkle
Copy link

Steps to reproduce

Save your config.json file in UTF8 BOM encoding. According to one customer, this used to work before 1.11.59

Outcome

What did you expect?

Element to load the config file

What happened instead?

Element start with default config

Operating system

Windows 11

Application version

1.11.71

How did you install the app?

From https://element.io/download

Homeserver

n/a

Will you send logs?

Yes

@dosubot dosubot bot added O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist labels Jul 19, 2024
@t3chguy
Copy link
Member

t3chguy commented Jul 19, 2024

Looks like Node doesn't handle BOM itself so it should never have worked given we have no code to handle this.

nodejs/node-v0.x-archive#1918

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Config O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants