Fix for too much margin for responsebody on images and empty response bodies; Style fixes

Author: Daniel Herzog

src/network/network_details_templates.js

@@ -149,6 +149,7 @@ templates._make_header_template_func = function(is_request_headers)
 {
   // add data-spec attributes on certain firstline tokens, depending on if it's request_headers.
   // todo: while this has firstline_tokens, it can't be reused.
+  // todo: not looking too good.
   var firstline_tokens = 0;
   var add_data_spec;
   if (is_request_headers)
@@ -392,7 +393,7 @@ templates._request_body = function(req, do_raw)
 
 templates._response_body = function(resp, do_raw, is_last_response)
 {
-  var ret = [this._wrap_pre("\n")]; // todo: no, then it's (really) empty there shouldn't be a separator either. For images it looks a bit wrong too, since the img elem makes its own space too.
+  var ret = [];
 
   var classname = "";
   if ((resp.saw_responsefinished && resp.no_used_mimetype) ||
@@ -439,6 +440,9 @@ templates._response_body = function(resp, do_raw, is_last_response)
       }
     }
   }
+  if (ret.length)
+    ret.unshift(this._wrap_pre("\n"));
+
   if (do_raw)
     return ret;
   else

src/network/network_style.css

@@ -267,7 +267,7 @@
   overflow: auto;
   height: 100%;
   box-sizing: border-box;
-  padding: 27px 20px 37px 0;
+  padding: 27px 20px 27px 0;
   background-color: #fff;
   /* using border-left instead of padding-left to keep the 
      space for the close button when scrolling horizontally */
@@ -310,11 +310,6 @@
   margin: 0;
 }
 
-.network-details-container img.network-body
-{
-  margin-top: 2em;
-}
-
 .network-details-container table
 {
   border-collapse: collapse;