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

Updates corrupt certain characters in entry comments #180

Closed
NotJim99 opened this issue Aug 31, 2019 · 2 comments
Closed

Updates corrupt certain characters in entry comments #180

NotJim99 opened this issue Aug 31, 2019 · 2 comments
Labels
bug
Projects

Comments

@NotJim99
Copy link

NotJim99 commented Aug 31, 2019

Making any sort of updates to MAL entries (chapters/volumes read, episodes watched, score, status) using the extension will corrupt certain characters like apostrophes, quotation marks, and colons in said entry's comments and change them into either their HTML character codes when done from the MiniMAL window or a string of garbage followed by the character code when done using other means like the popup at the bottom of the page or the embed on the series' page on reader sites.

So an entry comment like:

This's an example.

Would become:

This's an example.

When the entry is edited through most means, and:

This's an example.

When the entry is edited with MiniMAL.

By entry comments, I mean this part here, in case that wasn't clear.

Comments

@lolamtisch lolamtisch added the bug label Aug 31, 2019
@lolamtisch lolamtisch added this to backlog in Features via automation Aug 31, 2019
@lolamtisch lolamtisch moved this from backlog to Planned for next release in Features Aug 31, 2019
@lolamtisch
Copy link
Member

lolamtisch commented Aug 31, 2019

It is probably only missing encoding on the comments section before sending it to MAL. Will soon look into it.

@lolamtisch lolamtisch moved this from Planned for next release to Done for next release in Features Sep 2, 2019
@NotJim99
Copy link
Author

NotJim99 commented Sep 15, 2019

Yeah, that seems to have fixed it. Thanks.

Features automation moved this from Done for next release to Done Sep 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug
Projects
Features
  
Done
Development

No branches or pull requests

2 participants