Re: [dispatch] Dispatching Work on ECMAScript Media Types Updates

Martin Thomson <> Thu, 17 August 2017 11:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7D087132113 for <>; Thu, 17 Aug 2017 04:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eUiCx6TvglnU for <>; Thu, 17 Aug 2017 04:38:38 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6DA85126DD9 for <>; Thu, 17 Aug 2017 04:38:38 -0700 (PDT)
Received: by with SMTP id 76so29603718ith.0 for <>; Thu, 17 Aug 2017 04:38:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Qlz5nbM6mlMtuquEgrxOOB4c3KeqAbszDah3H4ZWVpA=; b=aGZTzrn3XR2yaIXgguH5sC/cd7oekLonKSPDGhSU6uSo77sM3JH+UXDkGIjV4koMCf 7sedcq/chqeOsWXOYjCAsfskoUNsQGPT8ngAzBnN2D0dWfwwytWWhousoZBd2igFDVTt hiG/C7xne+okOQthCax/zevCPKljkyPNVPgZfm5qLl8tpmWkz0ZXvSQof7VjO3II18j/ SnfMxFz2mUwq5Ejbx4wDBUClaI7t0Fju9BQIImJ9QBjfpl+ummwhFeaxnhHqA5Q4thO8 ch5a+OHDZF/iBStdcF3+52DeNGVKYDVfMh3Iv6XN5OHI/wZwzniPgus2+8VMc90Uk/O8 dHSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Qlz5nbM6mlMtuquEgrxOOB4c3KeqAbszDah3H4ZWVpA=; b=mBO/s/3x94iYth1l2X1yNHzr3DPMln1XC5T0Bolu0qdLBd3lVn7Z6gt467YH3jDdyY 6mJMqmIRPzylwS5wtUX+fKm0roH+nh6DCPtKKuaSWyIL7Asmi7ftuepBE54AK6eRhEah zrBFyiNm2hCYGDwCf5BuIl6fV6M3Oq2cTdzY5iyz60cUmtZuMzNal5nEzHcUmcowRe+8 HbonfPbpUhBoUeESynEWroGx9HDNn7S4di04wqDNfPE9roYu8LIESqYHEGiLXjX+j76F CxYDJJ1YEOJLZTpe2A2GMirYXKA/EN20GnpXjr6o5VCCh4bbxds/A/eqAoylN1osCFHd GKrw==
X-Gm-Message-State: AHYfb5g/0ixIYNZ58ChhUbHlAxMeETNKoDx47pwJJPDURiTaUtq4+Czt z2ZFFpOrkc8nbS1JP7JL3w9do+Z1AQ==
X-Received: by with SMTP id j21mr1348399iti.165.1502969917755; Thu, 17 Aug 2017 04:38:37 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 17 Aug 2017 04:38:36 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
From: Martin Thomson <>
Date: Thu, 17 Aug 2017 21:38:36 +1000
Message-ID: <>
To: Bradley Meck <>
Cc: "Matthew A. Miller" <>, DISPATCH <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [dispatch] Dispatching Work on ECMAScript Media Types Updates
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 17 Aug 2017 11:38:40 -0000

On 17 August 2017 at 20:03, Bradley Meck <> wrote:
>> My initial reaction to this statement was: so why aren't we seeing a
> request for a new media type?
> This was discussed in a few different places, ultimately culminating in no
> body wanting to take that route. You can read some info on that in the link
> to the informative TC39 issue It
> appears you might be more interested in the HTML side of things, which would
> be that a new media type would not load with the specification they have
> already started deploying ( there was an issue about this on HTML side in
> ). Some discussion about a `mode`
> parameter instead of media type is in an issue on this proposal
> . That might be
> the better route since it will work in web browsers.

I'm not questioning the decision (though I appreciate the pointers,
thanks), just pointing out that there is an obvious question arising
from your introductory text.  You don't need to defend the decision,
but you should answer that question by mentioning that link metadata
(type=module) ensures that no one else asks the question.

The discussion (and outcome if I'm reading correctly) on #1 leading to
mode= certainly seems sensible.  Please pick a default of mode=script
and save us all headaches.

Question, mainly for my gratification: if I include a module in a
<link rel=preload>, how do I signal that it's a module?  You can't use
a type= attribute there, because that key is taken for something else
(media type).  I know that browsers like doing things like pre-parsing
in addition to preloading.

I have to assume that you just use native es6 modules keywords rather
than importScript in workers, so you don't need explicit
identification there.

>> Nit: There Are So Many Proper Nouns In This Document.  Is that really
>> necessary?
> I think this is in part a stylistic thing of my writing. I tend to avoid
> pronouns and am capitalizing grammar productions in the same manner as the
> ECMAScript specification. We could make stylistic changes though!

Consistency good >> Too Many Capitals Are Bad

(In other words, don't change on my account.)