Commit-Queue | +1 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
TestCase{
.conversion_measurement_enabled = true,
.expected = true,
},
Andrew Paseltiner@lin...@chromium.org This test case is failing with this CL: The feature policy apparently doesn't include `attribution-reporting` (line 109). Any ideas what's going on here?
Separately, it probably makes sense to rename this file and the associated test fixtures and/or move this to WPT.
Acknowledged
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
kAttributionReportingCrossAppWebSupportHeader);
Is it intended that we still keep the enum (https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/mojom/use_counter/metrics/web_feature.mojom;l=4159)?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
kAttributionReportingCrossAppWebSupportHeader);
Is it intended that we still keep the enum (https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/mojom/use_counter/metrics/web_feature.mojom;l=4159)?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
kAttributionReportingCrossAppWebSupportHeader);
Don't you want to unconditionally count here now, instead of removing the count?
RuntimeEnabledFeatures::AttributionReportingEnabled(dom_window);
The lhs is `(x || true)`, so the behavior-preserving change is to change this to just `= dom_window` I think.
Maybe the LHS was wrong and wanted to use `&&` instead of `||`. If that's the case, we should change that in a separate CL, probably before landing this one here.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
kAttributionReportingCrossAppWebSupportHeader);
Don't you want to unconditionally count here now, instead of removing the count?
I guess I'm not really sure what the purpose of this count is from a Blink perspective.
CC @lin...@chromium.org who authored this logic in http://crrev.com/c/5249677, and also @john...@chromium.org for clarification.
RuntimeEnabledFeatures::AttributionReportingEnabled(dom_window);
The lhs is `(x || true)`, so the behavior-preserving change is to change this to just `= dom_window` I think.
Maybe the LHS was wrong and wanted to use `&&` instead of `||`. If that's the case, we should change that in a separate CL, probably before landing this one here.
This is a good question.
CC @lin...@chromium.org who authored this logic in http://crrev.com/c/4467529, and also @john...@chromium.org for clarification.
Code-Review | +1 |
kAttributionReportingCrossAppWebSupportHeader);
Andrew PaseltinerDon't you want to unconditionally count here now, instead of removing the count?
I guess I'm not really sure what the purpose of this count is from a Blink perspective.
CC @lin...@chromium.org who authored this logic in http://crrev.com/c/5249677, and also @john...@chromium.org for clarification.
When the feature was default enabled, the support header will be sent for all attribution-eligible requests. Therefore there's no need for a separate user counter, and we can simply refer to `kAttributionReportingAPIAll` for API usage.
RuntimeEnabledFeatures::AttributionReportingEnabled(dom_window);
Andrew PaseltinerThe lhs is `(x || true)`, so the behavior-preserving change is to change this to just `= dom_window` I think.
Maybe the LHS was wrong and wanted to use `&&` instead of `||`. If that's the case, we should change that in a separate CL, probably before landing this one here.
This is a good question.
CC @lin...@chromium.org who authored this logic in http://crrev.com/c/4467529, and also @john...@chromium.org for clarification.
This was added when we were running OT for web-based ARA and cross app web ARA separately, and the intention was to allow testing cross app web ARA with only the token for cross app web ARA OT.
After the OTs ended and was removed, the runtime feature is gated by this base::Feature as well as `kConversionMeasurement` (see https://source.chromium.org/chromium/chromium/src/+/main:content/child/runtime_features.cc;l=660). Therefore, we still need the condition on the main runtime feature which is gated by `kConversionMeasurement`.
Jason Chase removed feature-co...@chromium.org from reviewers of this change.
Remove AttributionReportingCrossAppWeb runtime and content features
These have been enabled by default since M125, so this is a simple
mechanical removal.
This CL contains no intentional web-visible behavioral changes.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |