[webkit-dev] Request for position on Import Conditions
daniec at microsoft.com
Tue Mar 9 15:29:23 PST 2021
Import assertions and JSON modules were reviewed in the WebKit Slack at https://webkit.slack.com/archives/CTY7Z24RZ/p1599076278003200a last September, but I can't find an official position posted anywhere. Would it be possible to have a position stated here, so I have something to link to that doesn't require logging into the Slack?
I was thinking that I had also received a reply on this old thread but I must have misremembered.
From: Daniel Clark
Sent: Thursday, July 9, 2020 9:47 AM
To: 'webkit-dev at lists.webkit.org' <webkit-dev at lists.webkit.org>
Cc: 'Daniel Ehrenberg' <littledan at igalia.com>; 'Myles Borins' <myles.borins at gmail.com>; Sven Sauleau <sven at sauleau.com>
Subject: Request for position on Import Conditions
I'd like to ask for WebKit's official position on import conditions, as described in the explainer at . This proposal adds an inline syntax for module import statements to pass on more information alongside the module specifier. It includes support for JSON modules as a primary application, with the "type" condition used to mitigate the security issue described in  that previously blocked their adoption in HTML. The proposal is designed such that other conditions can be added in the future for additional use cases, some of which may not yet be anticipated.
The champion group is particularly interested in your opinion on whether it's acceptable for import conditions to not be part of the module map key. The current state of our HTML spec integration PR at  is that they are not part of the module map key. We perform module map caching such that there will always be no more than a single fetch for a given module specifier regardless of failed module type checks. The thread at  discusses this issue in detail.
We plan to request Stage 3 for this proposal at the upcoming TC39 meeting beginning on July 20.
 Explainer: https://github.com/tc39/proposal-import-conditions
 Modules MIME-type security issue: https://github.com/w3c/webcomponents/issues/839
 HTML Spec integration PR: https://github.com/whatwg/html/pull/5658
 HTML integration thread: https://github.com/whatwg/html/issues/5640
Mozilla standards-position ("worth prototyping") https://github.com/mozilla/standards-positions/issues/373
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev