[whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112)

Hi... So I've been adding AbortController/AbortSignal support to the (experimental) FLEDGE APIs, and I think in our case the requirement for the argument field to be called 'signal' in https://dom.spec.whatwg.org/#abortcontroller-api-integration is somewhat undesirable, as the passed in config object to the API already has:
  auctionSignals
  sellerSignals
  perBuyerSignals
... so an unqualified 'signal' in this company feels confusing; I would have much preferred 'abortSignal' if it were spec-permissible.


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

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