What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== given I have opened the F12 development tools and I am on the 'Network' tab and the site is executing an XHR web request then I see the response in the list when I click the Request and I select the 'Response' tab then I can see the response body Current behavior: the response is rendered as source code. often also with syntax highlighting is working. Expected behavior: if the response is HTML or JSON, than there should be the option to render it in an human readable version like on Google Chrome. the source code and syntax highlighting should be kept, since it is often needed to inspect the raw data. What problems would this solve? =============================== easier to inspect the response from the server. Who would use this? =================== software developers What would users see? ===================== see description What would users do? What would happen as a result? =================================================== - faster inspection of the result from an XHR request - not switching to another browser like Chrome for this task Is there anything else we should know? ======================================

Thanks for filing the request. For clarity, are you saying that your XHR request can respond with JSON or HTML and you want the output syntax highlighted instead of just displaying plain text?

not exactly. In my use case: The XHR request responds either - with JSON when everything is ok, or - (in development only) with an HTML error page with debugging information (ie. when there is an exception on the server). In order to read the HTML error page and determine the cause of the exception from the server, syntax highlighting (which is working quite well btw.) makes little sense, since it is still very hard to find the relevant information. What is required is the rendering/preview of the HTML page.

Ah, I see what you mean! Thanks for clarifying. I have updated the bug to better capture what you requested! :-)