Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110)

I ran into this issue today. I definitely agree that the `setTimeout` logic isn't that burdensome, but the fact that `AbortController` uses `AbortSignal` internally, but that you can't actually use the `AbortSignal.timeout()` functionality was frustrating. The APIs very much look like something that should work.

I was actually looking to use `AbortController` to simplify some logic where I'm only using a timeout to abort a request that's related to some secondary page initialization logic for metrics. It's not critical that the request completes, so we want a short timeout on it.

To summarize: because `AbortSignal` has the timeout method, it feels broken that you can't use that with `AbortController`.

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

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