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

Comments \n are not escaped properly #175

Closed
Me1000 opened this issue Apr 11, 2012 · 5 comments
Closed

Comments \n are not escaped properly #175

Me1000 opened this issue Apr 11, 2012 · 5 comments
Assignees
@Me1000
Labels
Fixed Pending Release

Comments

@Me1000
Copy link
Owner

Me1000 commented Apr 11, 2012

new line characters show up as the characters \n
@koraktor
Copy link

See #176. It was created with BugHub 1.5.1.\n\nAdditionally, the slashes in the URL have been escaped, so there are probably more characters that will be escaped.

@Me1000
Copy link
Owner Author

Me1000 commented Apr 12, 2012

Ah, good catch. I'll resubmit the new version that fixes both issues.

@koraktor
Copy link

Nice.

PS: I edited the other issue, so it's readable again.

@ghost ghost assigned Me1000 Apr 12, 2012
@Me1000
Copy link
Owner Author

Me1000 commented Apr 16, 2012

Apple has approved my request for expedited review. Hopefully we'll see this update today or tomorrow instead of friday!

@Me1000
Copy link
Owner Author

Me1000 commented Apr 16, 2012

Fix has landed on the App Store. Closing

@Me1000 Me1000 closed this as completed Apr 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Me1000 Me1000

Labels
Fixed Pending Release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@koraktor @Me1000