Re: [whatwg/dom] AsyncContext propagation to events (PR #1451)

@nicolo-ribaudo commented on this pull request.



> + </li>
+
+ <li><p>Run the originally-specified steps for this regular operation. If the steps return a value
+ or throw an exception, return or throw it in turn.
+</ol>
+
+<p>Specifications should set this extended attribute on methods which start an async operation which
+will eventually cause events to be fired on the instance on which the method was called.
+<span class="non-normative">An example of this is the {{XMLHttpRequest}} and its
+{{XMLHttpRequest/send}} method:</span> [[XHR]]
+
+<pre highlight=idl>
+[Exposed=(Window,DedicatedWorker,SharedWorker)]
+interface XMLHttpRequest : XMLHttpRequestEventTarget {
+  // ...
+  [PropagatesAsyncContextToEvents=("loadstart", "progress", "error", "load", "timeout", "loadend")] undefined send(optional (Document or XMLHttpRequestBodyInit)? body = null);

I'm not sure I understand the question. This is about WebIDL, not some JS-exposed option.

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

Message ID: <whatwg/dom/pull/1451/review/3850444014@github.com>