We are currently using the group-by-origin execution mode. However, this mode presents a significant limitation:

• When overwriting an interest group from another joiningOrigin, all interest groups created with the first joiningOrigin are deleted. This behavior is undesirable and constrains our interest group creation policy.

We are planning to increase the number of cross site interest groups. We understand that in this case we should use the ExecutionMode frozen-context, but as explained in the ticket Frozen-Context · Issue #1415 · WICG/turtledove we are facing issues with this mode. So we would like to keep the group-by-origin optimization.

The rationale behind this implementation is unclear, and we do not perceive a concrete privacy threat in relaxing this constraint.
Indeed, once interest groups joined from origin A are re-joined from a different origin B, they would be grouped according to their new origin B and all evaluated in the same execution environment.

Any interest group joined from origin A would be in another group, and thus evaluated in a different execution environment, preventing cross site leackage.

Question:

Could we consider relaxing this constraint to mitigate its impact on our interest group creation policy?