- From: Mike West <mkwst@google.com>
- Date: Thu, 30 Oct 2014 15:04:57 +0100
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: WebAppSec WG <public-webappsec@w3.org>
Received on Thursday, 30 October 2014 14:05:46 UTC
I think everything here should follow from the way we define the interaction with Fetch. You're suggesting just making this a non-normative section, and explicitly explaining these results as byproducts of the algorithms? -mike -- Mike West <mkwst@google.com> Google+: https://mkw.st/+, Twitter: @mikewest, Cell: +49 162 10 255 91 Google Germany GmbH, Dienerstrasse 12, 80331 München, Germany Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Christine Elizabeth Flores (Sorry; I'm legally required to add this exciting detail to emails. Bleh.) On Thu, Oct 30, 2014 at 2:51 PM, Anne van Kesteren <annevk@annevk.nl> wrote: > It's not a good idea to have duplicate requirements. If the relevant > requirements follow from Fetch, we should not duplicate them here. > It's fine to have text explaining the consequences, but we should not > require it twice. > > > -- > https://annevankesteren.nl/ > >
Received on Thursday, 30 October 2014 14:05:46 UTC