Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032)

Chatting with @smaug---- I think the concern is usage of the signal `abort` event outside the realm of abortable operations. E.g., using the signal `abort` event as an indication you need to show some UI.

However, the design is such that the `abort` event is for the purposes of implementing abortable operations consuming signals only. And not as an independent "trigger" point to go do something else.

The "trigger" to go do something else (such as displaying UI) should always be (an) (abortable) operation(s) and its/their completion value(s) (which could be abort or timeout).

Perhaps this is something we need to further clarify in the specification.

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