You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Fetch throws an error when called with AbortSignal Failed to execute 'fetch' on 'Window': member signal is not of type AbortSignal.
To Reproduce
Steps to reproduce the behavior:
import{AbortController}from"@azure/abort-controller";constcontroller=newAbortController();constsignal=controller.signal;fetch("https://www.google.com",{ signal }).then(response=>response.json()).then(content=>{console.log(content);});
Expected behavior
AbortSignal should be compatible with Standard AbortSignal
Additional context
Seems to be working fine in Edge
The text was updated successfully, but these errors were encountered:
Hi @joheredi, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.
Describe the bug
Fetch throws an error when called with AbortSignal
Failed to execute 'fetch' on 'Window': member signal is not of type AbortSignal.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
AbortSignal should be compatible with Standard AbortSignal
Additional context
Seems to be working fine in Edge
The text was updated successfully, but these errors were encountered: