[b]Bug Description:[/b] Editing any kind of post more than once causes the text inside of the text box to display incorrectly. If your thread has any form of paragraphing or new lines, they won't be displayed in the edit box on subsequent edits after the first. It will be as if every single paragraph and new line were concatenated into a single huge paragraph, which makes editing a specific part of your post much more difficult.
[b]Steps to Reproduce:[/b]
[b]1)[/b] Create a thread or reply to a thread with a post that contains at least one new line character, for example:
[quote]First Line
Second Line[/quote][b]2)[/b] Edit that Post. Observe that the text in the edit box is behaving normally. Then save the post without making any changes to the text.
[b]3)[/b] Without refreshing, edit the post again. Observe that the text in the edit box is being displayed as if it contained no new line characters. Example:
[quote]First Line Second Line[/quote][b]4)[/b] Save the post without making any edits. Observe that there are no changes to your original post's paragraph structure despite the fact that edit box showed your entire post on a single line.
[b]5)[/b] Refresh the page, then repeat steps 2 through 4. Observe that the text is only displayed properly in the edit box for only the first edit for each time you view the page.
[b]Expected Result:[/b] Subsequent Edits after the first should retain the original post's paragraph structure and display new line characters properly.
Please fix this Bungie. It makes drafting threads a lot more annoying. I'm using Internet Explorer 9 if that helps, and I haven't attempted to recreate the bug on any other browsers.
Keep up the hard work :D
-
Wait, so do the posts appear incorrect only in the edit box or, after two or more subsequent edits, does the post display incorrectly in the normal post area?
-
Edited by Malfar: 1/25/2013 5:51:50 AMI noticed this also, I would have wrote a bug about it, but I figure Bungie pays people to write bugs.(Or I took an arrow to the knee..) What I think is happening, when JavaScript stores the postEdit data, it strips out the '/n', and when it is rendered in the edit box, the browser dosen't read the '/r's as a newline. This is just a guess, but I have seen behavior like this before. Most likely an issue with a RegEx string.
-
Give this man a cookie for a well written bug report!
-
Hmm, well, maybe if you were using me you wouldn't have this issue.
-
Edited by A 3 Legged Goat: 1/23/2013 12:39:41 AMI was able to reproduce the bug in IE 9 but not in Google Chrome
-
This happened to me too. It was while I was using IE for xbox.