The extracts are currently generated with the old API which doesn't produce valid xhtml5, so any malformed ajax request just won't show up in the content area.
Parsoid does produce xhtml5, so Extension:TextExtracts needs to be extended to support parsing with Parsoid rather than the old API. Trail of bug tracker links (updated as of 2017-11-20):
I have made the decision that this will not be fixed. T170617 will make sure that api consumers know about this problem. For those who want well formed HTML we will be providing a new service on RESTBase which will guarantee that (please follow along with T113094)
https://phabricator.wikimedia.org/T165017
AC (acceptance criteria?): "[...] The extract property is present and contains valid HTML."
Closed, resolved. Does this mean the functionality is now available?
The extracts are currently generated with the old API which doesn't produce valid xhtml5, so any malformed ajax request just won't show up in the content area.
Parsoid does produce xhtml5, so Extension:TextExtracts needs to be extended to support parsing with Parsoid rather than the old API. Trail of bug tracker links (updated as of 2017-11-20):
extract_html
in the example output). Note: isn't that already available?