- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 24 Aug 2016 20:01:12 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Thursday, 25 August 2016 03:01:42 UTC
> Ah, that makes more sense. However I am not sure I agree with the concern. I am quite certain that my team would be interested in using it. Ok. That's sweet music to the spec editor's ears 🎸. > We (spec folks) don't have any requirements of the browsers, either. Nit pick: but the RCF2119 keywords are conformance requires precisely for browsers. > I know that Edge is extremely interested in using them. Ok, cool. That's what I needed to hear. > I am not clear on what the issue is - that user has manifest data. Stores A and B ingest it, user updates the data on Store A, and as a result Store B is out of date? No, that user updates the data in the manifest, but Store A and B don't update. So, user updates data in Store A and B, but then stops updating the manifest. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/477#issuecomment-242268884
Received on Thursday, 25 August 2016 03:01:42 UTC