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

Messages are rendered differently on iOS and OS X. But shouldn't. #10

Closed
regexident opened this issue Jul 25, 2016 · 1 comment
Closed

Comments

@regexident
Copy link

Wire for Mac (or Web) appears to be rendering messages differently than the native client on iOS.

Given:

  • A message containing ¯\_(ツ)_/¯.

When:

  • On iOS.

Then:

  • The message shows up as ¯\_(ツ)_/¯.

Given:

  • A message containing ¯\_(ツ)_/¯.

When:

  • On OS X or Web.

Then:

  • The message shows up as ¯_(ツ)_/¯.

Given:

  • A message containing ¯\\_(ツ)_/¯.

When:

  • On iOS.

Then:

  • The message shows up as ¯\\_(ツ)_/¯.

Given:

  • A message containing ¯\\_(ツ)_/¯.

When:

  • On OS X or Web.

Then:

  • The message shows up as ¯\_(ツ)_/¯.

Same thing for foo _bar_ baz, which shows up as foo _bar_ baz on iOS and as foo bar baz (with bar in italics) on OS X or the web.


The web app seems to have some basic support for markdown-flavored formatting, which the native client lacks.

@bennycode
Copy link
Contributor

Hi @regexident, thank you very much for making us aware of this issue. We added your scenario to our test suite with this Pull Request: #16

Thank you very much — Good job!

Benny

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants