Re: [whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112) from M.K. on 2024-06-10 (public-webapps-github@w3.org from June 2024)

From: M.K. <notifications@github.com>
Date: Mon, 10 Jun 2024 11:59:24 -0700
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/issues/1112/2159087833@github.com>

@domfarolino Could you expand on that 👎 ? Do you see a benefit in restricting the property name to the generic word?
Ideally, the spec should even provide a link to arguments for that restriction. Currently, I can only see the risk/cost.
The only argument I found in this thread is that other APIs use the generic name, but that's not a good reason in itself. The other APIs hopefully have good reasons of their own, maybe that in *their* specific context only one kind of signal makes sense.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1112#issuecomment-2159087833
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1112/2159087833@github.com>

Received on Monday, 10 June 2024 18:59:28 UTC