Private aggregation feature flags moved into //content/common

Chromium change:

https://source.chromium.org/chromium/chromium/src/+/63abee9f6d8c1faa488c7139bd6fe583b13e909e

commit 63abee9f6d8c1faa488c7139bd6fe583b13e909e
Author: Alex Turner <alexmt@chromium.org>
Date:   Mon Aug 15 20:51:54 2022 +0000

    Gate privateAggregation JS object behind feature flag in FLEDGE

    Currently, the privateAggregation object is unconditionally exposed in
    FLEDGE worklets. Instead, we only expose the object when the Private
    Aggregation API feature is enabled.

    Bug: 1346106
This commit is contained in:
Emerick Rogul
2022-09-15 20:46:18 -04:00
parent 075358a6d9
commit cf2adedcb7
@@ -3,7 +3,7 @@
* License, v. 2.0. If a copy of the MPL was not distributed with this file,
* You can obtain one at https://mozilla.org/MPL/2.0/. */
#include "src/content/browser/private_aggregation/private_aggregation_features.cc"
#include "src/content/common/private_aggregation_features.cc"
#include "base/feature_override.h"