LGTM2, with the understanding that cleaning up the developer-facing story around this work is important. I think the unenrolled case probably falls into step ~8 of https://wicg.github.io/trust-token-api/#issue-request, in which case I think the web-facing behavior is clearly-enough specified. I'd like y'all to make sure that that failure mode is debuggable, which I'm happy for you to wrap into a larger story around enrollment in devtools if that's what you land on when working with that team.
Thanks! -mike On Mon, May 15, 2023 at 5:06 PM Steven Valdez <[email protected]> wrote: > Thanks, we'll work on fixing those two issues. > > I'm not sure what the general flow for enrollment in DevTools will look > like, but if there's a general flow to detect when enrollment is missing > for other APIs that check at runtime, we can try to integrate with that > when PST calls are made with an unregistered issuer. > > On Fri, May 12, 2023 at 7:05 PM Mike Taylor <[email protected]> > wrote: > >> LGTM1 % resolving the following spec issues: >> >> https://github.com/WICG/trust-token-api/issues/232 >> >> https://github.com/WICG/trust-token-api/issues/230 >> >> On Wed, May 10, 2023 at 5:52 AM Mike West <[email protected]> wrote: >> >>> Will devtools help guide developers towards enrollment? >>> >> Also I think Mike's question on devtools support is worth answering. >> > > > -- > > Steven Valdez | Chrome Privacy Sandbox | [email protected] | Cambridge, > MA > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3Df-CTw1wcvB1YCyxRn3OATXZh%2BnP3%2BqD0t8d8bkLLnmMQ%40mail.gmail.com.
