Skip to main content
Stack Apps

Return to Question

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

The Stack Exchange API (with a safe filter) is returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

I've seen this occur with this questionthis question, and the server response on the actual Stack Overflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the HTML (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the Stack Exchange API (or backend), or should API clients not assume that body content will be well-formed HTML? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?

The Stack Exchange API (with a safe filter) is returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

I've seen this occur with this question, and the server response on the actual Stack Overflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the HTML (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the Stack Exchange API (or backend), or should API clients not assume that body content will be well-formed HTML? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?

The Stack Exchange API (with a safe filter) is returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

I've seen this occur with this question, and the server response on the actual Stack Overflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the HTML (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the Stack Exchange API (or backend), or should API clients not assume that body content will be well-formed HTML? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?

More appropriate tags, misc cleanup
Source Link
edit approved Dec 3, 2013 at 5:14
Brock Adams
edit approved Dec 3, 2013 at 5:14
Brock Adams
  • 13k
  • 5
  • 39
  • 64

I've run into an issue with the StackExchangeThe Stack Exchange API (with a safe filter) is returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

The question I've seen this occur with is http://stackoverflow.com/questions/19774073/strange-behavior-of-length-command-oraclethis question. I've just noticed that, and the server response on the actual StackOverflowStack Overflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the htmlHTML (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the StackExchangeStack Exchange API (or backend), or should API clients not assume that body content will be well-formed htmlHTML? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?

I've run into an issue with the StackExchange API (with a safe filter) returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

The question I've seen this occur with is http://stackoverflow.com/questions/19774073/strange-behavior-of-length-command-oracle. I've just noticed that server response on the actual StackOverflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the html (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the StackExchange API (or backend), or should API clients not assume that body content will be well-formed html? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?

The Stack Exchange API (with a safe filter) is returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

I've seen this occur with this question, and the server response on the actual Stack Overflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the HTML (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the Stack Exchange API (or backend), or should API clients not assume that body content will be well-formed HTML? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?

Source Link
Rob MacEachern
Rob MacEachern
  • 123
  • 2

V2.1 API body HTML has unclosed li tags

I've run into an issue with the StackExchange API (with a safe filter) returning question body content with malformed HTML, specifically <li> elements that do not have closing tags (and no valid parent).

The question I've seen this occur with is http://stackoverflow.com/questions/19774073/strange-behavior-of-length-command-oracle. I've just noticed that server response on the actual StackOverflow page also includes the same issues.

The problem I'm facing is that I'd like to embed the question body in a custom web page and the unclosed elements are causing the browser to misinterpret the html (particularly when body content is put into container <li> elements).

So my question is: is this a bug in the StackExchange API (or backend), or should API clients not assume that body content will be well-formed html? If the answer is the latter, what kinds of workarounds are available for displaying body content on the web in a more predictable way?