5 ms·

Whoa I am about to save you so much time! You totally can view the response, just go to the 'Resources' tab, choose 'XHR' from the top bar (or not, but it's ea

Whoa I am about to save you so much time! You totally can view the response, just go to the 'Resources' tab, choose 'XHR' from the top bar (or not, but it's easier). Now cause a request. You'll see it pop up in the list on the left and you can click it to see headers/params and the response.

spooneybarger 16y ago
Wow. This isn't adding value to the conversation but I had never noticed that while using or in the documentation. You saved more than 1 person a lot of pain. Thank you.
- thenduks 16y ago
  No problem, took me a while to find it too. I would still prefer to be able to expand it in the console a-la Firebug -- however the more I use Chrome as my primary browser the less I find myself using the console in general and thus I mostly stay on 'resources' except in the early stages of coding (when there's a lot of logging going on :)).
catshirt 16y ago
I had to reread the reply, but it sounds like they're speaking strictly about rendered HTML- not just the response text. For instance, when an XHR response is returned as "Content-Type:text/html; charset=UTF-8", I still see raw HTML in the content pane: http://grab.by/7SXg http://grab.by/7SXg
- wahnfrieden 16y ago
  Yes, exactly right. Sorry my post wasn't clear.
wahnfrieden 16y ago
Thanks, but this doesn't render the HTML, it just shows the plaintext. The HTML generated by Django for error messages is not very readable, which is why I have to copy what Chrome gives me in that XHR tab into a new file to view as rendered HTML. I just end up using Firebug Lite instead when I need to do this, but it's really clunky.
- thenduks 16y ago
  Ah I see you want to see it rendered. Well, considering how Web Inspector is implemented that shouldn't be especially difficult to do. Maybe make a bug report[1]? [1]: https://bugs.webkit.org https://bugs.webkit.org
  - wahnfrieden 16y ago
    This feature request already exists.

spooneybarger 16y ago

Wow. This isn't adding value to the conversation but I had never noticed that while using or in the documentation. You saved more than 1 person a lot of pain. Thank you.

thenduks 16y ago
No problem, took me a while to find it too. I would still prefer to be able to expand it in the console a-la Firebug -- however the more I use Chrome as my primary browser the less I find myself using the console in general and thus I mostly stay on 'resources' except in the early stages of coding (when there's a lot of logging going on :)).

catshirt 16y ago

I had to reread the reply, but it sounds like they're speaking strictly about rendered HTML- not just the response text. For instance, when an XHR response is returned as "Content-Type:text/html; charset=UTF-8", I still see raw HTML in the content pane: http://grab.by/7SXg http://grab.by/7SXg

wahnfrieden 16y ago
Yes, exactly right. Sorry my post wasn't clear.

wahnfrieden 16y ago

Thanks, but this doesn't render the HTML, it just shows the plaintext. The HTML generated by Django for error messages is not very readable, which is why I have to copy what Chrome gives me in that XHR tab into a new file to view as rendered HTML. I just end up using Firebug Lite instead when I need to do this, but it's really clunky.

thenduks 16y ago
Ah I see you want to see it rendered. Well, considering how Web Inspector is implemented that shouldn't be especially difficult to do. Maybe make a bug report[1]? [1]: https://bugs.webkit.org https://bugs.webkit.org
- wahnfrieden 16y ago
  This feature request already exists.