Loading Profile...
topic content and reply content use different formating styles
Line breaks are escaped differently depending if the content is a Topic or Reply. This is really confusing, and seems to require different rendering code to display them properly.
Can this be normalized? Or at least can you explain how I should process each to properly display them in my client?
http://api.getsatisfaction.com/topics... is my example. I would expect the content blocks of each to be identical.
Can this be normalized? Or at least can you explain how I should process each to properly display them in my client?
http://api.getsatisfaction.com/topics... is my example. I would expect the content blocks of each to be identical.
I’m confused
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?also, the your code tag corrupts the xml entered within it. I put an element <Node id="attribute"/> in my post and it is rendered as <node></node> and the attribute is destroyed. This really needs to be fixed, it prevents us from posting correct code examples in GSFN.
I’m troubled
-
Inappropriate?Hi John,
Is this only happening on topics and replies viewed (or created) through the API?
It looks as though the API is stripping out break tags from replies, but not topics.1 Comment
Add a comment
This solves the problem
-
For now, the trouble we've been seeing has been topics and replies created on gsfn. We're not using the API to create topics with code in them at the moment. -
Inappropriate?There is a larger issue here though
We are not properly formatting HTML entered into topics and replies.
And yes our code tag doesn't keep certain code snippets from being rendered as HTML.
These are two known issues that need to be solved. I'm just not sure where they fit in. I'll talk to my peeps and let you know :) -
Inappropriate?Alright. I have some imperfect short term rendering fixes in place for replies. If you can give me a rough eta on a fix, i'll use that to determine how much more custom rendering fixes I will apply to the replies.
-
Inappropriate?I'll bring our API expert in the loop to see if we can get an ETA on fixing the line break discrepancy.
I’m confident
-
Inappropriate?Hi John,
Sorry about the FUBAR. I'll put a bug fix in tonight that should bring reply and topic formatting into sync. For the record, the topic formatting is the correct version.
Regarding the xml... you need to make sure that any XML entered is entity-encoded. Since we allow some html, we use a whitelist formatter that strips out and modifies anything inside angle brackets that isn't allowed by the whitelist. It is something that we want to improve in the future, but are short on resources to make it happen in the near term.
If you want to make good code examples, I would recommend escaping every < in your code with <
I know that's frustrating, but it is what we have to work with right now.
Hope that helps,
-Scott
1 person says
this solves the problem
-
Inappropriate?Hi Scott,
Thanks for the fix. I'll update my code to expect the new reply format tonight.
We'll escape our code samples from now on as well.
I’m doin' alright
-
Inappropriate?Curious if this went out tonight1 Comment Add a comment
This solves the problem
-
Yeah, just now it did.
EMPLOYEE
EMPLOYEE
