You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2023. It is now read-only.
FLoC OT was already finished, but some users still test FLoC with manually enabled options.
I had an issue that they have the wrong cohort id from unexpected histories when a feature flag of FlocPagesWithAdResourcesDefaultIncludedInFlocComputation is missing as noted in shigeki/floc_simulator#2 (comment).
@samdutton Could you please update your article of https://web.dev/floc/ to avoid unnecessary confusion?
Or it might be one option to stop the current FLoC features completely even when feature options are used.
The text was updated successfully, but these errors were encountered:
@shigeki - can you say a little more about what you mean by stopping the current FLoC features completely? If you mean that Chrome will no longer respond to document.interestCohort(), I think it is very beneficial to keep that in place to allow folks to continue to experiment and plan for the change - even if there are some zigs and zags leading up to the GA release.
FLoC OT was already finished, but some users still test FLoC with manually enabled options.
I had an issue that they have the wrong cohort id from unexpected histories when a feature flag of
FlocPagesWithAdResourcesDefaultIncludedInFlocComputation
is missing as noted in shigeki/floc_simulator#2 (comment).@samdutton Could you please update your article of https://web.dev/floc/ to avoid unnecessary confusion?
Or it might be one option to stop the current FLoC features completely even when feature options are used.
The text was updated successfully, but these errors were encountered: