- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 22 Aug 2018 22:50:37 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 23 August 2018 05:50:58 UTC
> BUT the problem is that we don't want to trash the whole manifest if one member is invalid. If one member throws a TypeError, we generally want to ignore that member, not the whole thing. Yes, exactly. So to do that, we would need to implement a custom IDL binding layer. That's no feasible. Our (Gecko's) implementation just runs the old processing rules: https://github.com/mozilla/gecko-dev/blob/master/dom/manifest/ManifestProcessor.jsm#L65 We just do simple processing, it doesn't go through the IDL binding layer. Does Chrome's implementation go through the IDL layer? > It seems that this isn't an issue with using IDL in a document format, but rather that IDL's conversion algorithm doesn't have a "non-strict mode" (that I know of). That's really not feasible. We don't need to fork our IDL biding layer for this format. I think we need to go and figure out https://github.com/whatwg/infra/issues/159 -- 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/pull/710#issuecomment-415299353
Received on Thursday, 23 August 2018 05:50:58 UTC