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
Reading through the spec, this seems like infrastructure that a couple of other specs are currently relying on, but one that could be potentially useful for future cases. (e.g. one can imagine a "cross-origin data worklet" that has access to cross-origin data and uses it to generate performance-related histograms in a secure way that doesn't leak any user-specific data)
Given that, I think it'd make sense to make this spec more agnostic to specs that rely on it. In order to do that, I think it'd make sense to move all the SharedStrorage/FLEDGE specific bits to their respective specifications, and only define the infrastructure (that can serve both cases) here.
The text was updated successfully, but these errors were encountered:
Note this has been partially addressed by #51, but leaving the issue open until the monkey patches are moved to the Shared Storage/Protected Audience specs
Reading through the spec, this seems like infrastructure that a couple of other specs are currently relying on, but one that could be potentially useful for future cases. (e.g. one can imagine a "cross-origin data worklet" that has access to cross-origin data and uses it to generate performance-related histograms in a secure way that doesn't leak any user-specific data)
Given that, I think it'd make sense to make this spec more agnostic to specs that rely on it. In order to do that, I think it'd make sense to move all the SharedStrorage/FLEDGE specific bits to their respective specifications, and only define the infrastructure (that can serve both cases) here.
The text was updated successfully, but these errors were encountered: