[Payments] Record navigations that close the Payment Request as aborts.

components/payments/content/payment_request.cc

 // Copyright 2016 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 "components/payments/content/payment_request.h"
 
 #include <string>
 #include <utility>
 
 #include "base/memory/ptr_util.h"
@@ skipping 175 matching lines @@
 
   // This sends an error to the renderer, which informs the API user.
   client_->OnError(mojom::PaymentErrorReason::USER_CANCEL);
 
   // We close all bindings and ask to be destroyed.
   client_.reset();
   binding_.Close();
   manager_->DestroyRequest(this);
 }
 
+void PaymentRequest::NavigatedAway(bool is_user_initiated) {
+  journey_logger_.RecordJourneyStatsHistograms(
+      is_user_initiated ? JourneyLogger::COMPLETION_STATUS_USER_ABORTED
+                        : JourneyLogger::COMPLETION_STATUS_OTHER_ABORTED);
+}
+
 void PaymentRequest::OnConnectionTerminated() {
   // We are here because of a browser-side error, or likely as a result of the
   // connection_error_handler on |binding_|, which can mean that the renderer
   // has decided to close the pipe for various reasons (see all uses of
   // PaymentRequest::clearResolversAndCloseMojoConnection() in Blink). We close
   // the binding and the dialog, and ask to be deleted.
+  journey_logger_.RecordJourneyStatsHistograms(
+      JourneyLogger::COMPLETION_STATUS_OTHER_ABORTED);

[Mathieu, 2017/05/09 18:12:19]

I don't think this line should be here, because it's in contradiction with line
142, amongst others?

[sebsg, 2017/05/10 14:58:48]

I still feel like we should log something here. Would you be OK with me logging
an abort reason here, instead of the journey stats?

   client_.reset();
   binding_.Close();
   delegate_->CloseDialog();
   manager_->DestroyRequest(this);
 }
 
 void PaymentRequest::Pay() {
   state_->GeneratePaymentResponse();
 }
 
 }  // namespace payments