- From: Martin Thomson <notifications@github.com>
- Date: Wed, 03 Jul 2024 21:17:43 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 4 July 2024 04:17:47 UTC
> I was trying to point out that if the developer uses a single web-app-origin-association file for multiple origins that pass a same-site test means that if it also specifies scope then scope applies to all origins that pass the same-site test. Just because this is a little murky still. My point is that only an origin can speak for itself in this regard. That is, "https://a.example.com/" (an origin) can't speak for "https://b.example.com/" (a different origin), even if they are the same site. Of course, if you have operational practices that mean you put the same file at the well-known location on both of those origins, that's fine, but that's not our business. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/875#issuecomment-2208089628 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/875/2208089628@github.com>
Received on Thursday, 4 July 2024 04:17:47 UTC