Oops, thought I was adding reviewers earlier but was only adding to CC. See previous message.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
(I think the other reviewers already cover the ownership needed for review, so let me remove myself)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
David BokanI'm doing this following a discussion with Adam. The context is that we (Meet developers) would like the stack information that CreateOrEmpty provides, so we were thinking of just changing body.cc to use that, and preferably adding the fetch URL in the message as well for additional debuggability.
That would require an experiment for changing the message. But Adam also noticed that we should be providing the abort reason as well (if one is provided), which also would require an experiment. In which case we might as well do both at once.
A question though: What would be the best way to go about getting the URL into this message, assuming that's not problematic? The error is now coming from AbortSignal (https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/dom/abort_signal.cc;l=279;drc=0a4317210c4de343411da25ccf8145d3091b3007) which doesn't have that context. Could I provide an optional string to its constructor for a default abort reason? Or would the memory footprint for that be a concern?
Apologies for the delay. I can't say I have a ton of expertise specifically in Fetch/Abort as a general Blink core dev but given this isn't long lived and URLs aren't that big I don't see the issue in copying in the KURL. You could even pass in and hold a pointer to `FetchRequestData` which is GarbageCollected, assuming all this makes sense for Abort (which Adam would be better placed to judge)
Removing myself since I don't think I'm the best reviewer in the list for fetch-related things.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |