[Contextual Search] Exclude suppressed taps from aggregate suppression heuristics logging

chrome/android/java/src/org/chromium/chrome/browser/contextualsearch/ContextualSearchHeuristic.java

 // 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.
 
 package org.chromium.chrome.browser.contextualsearch;
 
 /**
  * A piece of conditional behavior that supports experimentation and logging.
  */
 abstract class ContextualSearchHeuristic {
@@ skipping 26 matching lines @@
 
     /**
      * @return Whether this heuristic should be considered when logging aggregate metrics for Tap
      *         suppression.
      */
     protected boolean shouldAggregateLogForTapSuppression() {
         return true;
     }
 
     /**
-     * @return Whether this heuristic's condition would have been satisfied if it were enabled
-     *         through VariationsAssociatedData. When logging aggregate metrics for Tap suppression,
-     *         the condition may be considered satisfied even if the tap wasn't suppresed.
+     * @return Whether this heuristic's condition would have been satisfied, causing a tap
+     *         suppression, if it were enabled through VariationsAssociatedData. This method should
+     *         return false if the feature is enabled through VariationsAssociatedData.

[Donn Denman, 2016/09/23 20:40:13]

Nit: please rephrase this second sentence to better connect with the previous
regarding enabling, e.g. "If the feature is enabled through
VariationsAssociatedData then this method should return false."

[Theresa, 2016/09/23 20:57:30]

Done.

      */
     protected abstract boolean isConditionSatisfiedForAggregateLogging();
 }