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

Apostrophes are replaced with HTML entity codes in messages, replies. #175

Closed
zenmonkeykstop opened this issue Nov 15, 2018 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@zenmonkeykstop
Copy link
Contributor

zenmonkeykstop commented Nov 15, 2018

If a message contains an apostrophe , ie I'm a message, the text will be rendered as I&#x27m a message in the client.

Note that this isn't always the case - the message & # " ' <a href="foo"> rendered correctly.

@eloquence eloquence added the bug Something isn't working label Nov 15, 2018
@redshiftzero redshiftzero added this to the 0.1.0beta milestone Nov 15, 2018
@ultimatecoder
Copy link
Contributor

Thanks @zenmonkeykstop for such detailed observation 😃

I am trying to fix this issue. Will update here as soon as I will create the PR.

ultimatecoder added a commit to ultimatecoder/securedrop-client that referenced this issue Nov 17, 2018
In conversation, messages with single quote (') or double quote(") quote
wasn't rendered correct. It was difficult for journalist to read those
messages. This commit is fixing that problem of parsing quote based
messages and improves readability of the text in the conversation.

Resolves: freedomofpress#175
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants