When looking at a weird stack trace :jmarshall was getting from the WorkerRef debugging logic for XHRs I noticed that an unintentional aspect of the worker XHR creating a main-thread XHR on its owning window's global is that we will get DisconnectFromOwner notifications from the window that will race the worker teardown which I do not believe where anticipated / compensated for inside the worker XHR implementation. It's a straightforward fix for us to not call Abort in that case.
Bug 1900681 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When looking at a weird stack trace :jmarshall was getting from the WorkerRef debugging logic for XHRs I noticed that an unintentional aspect of the worker XHR creating a main-thread XHR on its owning window's global is that we will get DisconnectFromOwner notifications from the window that will race the worker teardown which I do not believe were anticipated / compensated for inside the worker XHR implementation. It's a straightforward fix for us to not call Abort in that case.