Browser process changes for Resource Timing sizes.

content/public/common/resource_response_info.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/public/common/resource_response_info.h"
 
 #include "content/public/common/appcache_info.h"
 #include "net/http/http_response_headers.h"
 
 namespace content {
 
 ResourceResponseInfo::ResourceResponseInfo()
     : has_major_certificate_errors(false),
       content_length(-1),
       encoded_data_length(-1),
+      encoded_body_length(0),

[kinuko, 2016/06/28 15:10:17]

This being 0 by default while others are -1 comes from the spec?  It feels a bit
inconsistent... does it make sense to keep these -1 but return 0 at the final
ResponseTiming API implementation in Blink?

[Adam Rice, 2016/07/07 06:50:09]

Actually, it's only 0 in Javascript when we can't supply it due to the
cross-origin restriction. So the default value shouldn't matter. I have changed
it to -1.

       appcache_id(kAppCacheNoCacheId),
       was_fetched_via_spdy(false),
       was_npn_negotiated(false),
       was_alternate_protocol_available(false),
       connection_info(net::HttpResponseInfo::CONNECTION_INFO_UNKNOWN),
       was_fetched_via_proxy(false),
       was_fetched_via_service_worker(false),
       was_fallback_required_by_service_worker(false),
       response_type_via_service_worker(
           blink::WebServiceWorkerResponseTypeDefault),
       is_using_lofi(false),
       effective_connection_type(
           net::NetworkQualityEstimator::EFFECTIVE_CONNECTION_TYPE_UNKNOWN) {}
 
 ResourceResponseInfo::ResourceResponseInfo(const ResourceResponseInfo& other) =
     default;
 
 ResourceResponseInfo::~ResourceResponseInfo() {
 }
 
 }  // namespace content