Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033)

@kanongil In this case "instrumentation" is something like APM. 

We have spent time talking to API consumers about this and have plenty of examples and use cases. Here is a common one (I'll use the web terminology since this is whatwg/dom but there are plenty of others).

 - I have a framework over my web components / React.
 - Components can "cancel rendering" because the user navigated away or the time allotment for rendering is up or an API request timed out. 
 - I have a high order component above those that needs to catch the timeout/cancellation and abort it (componentDidCatch in React speak).
 - That component presumably does not have access to the signal (coming from a hook in the framework React speak).

This is just an example, it _can_ be worked around (by for example making the signal global, injecting the signal to _all_ components) but that would create pretty ugly code from what I recall.

I am happy to loop in library/sdk authors we have talked to about this in the past if that'd help.

-- 
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/issues/1033#issuecomment-974821611