Re: [whatwg/fetch] Request's associated element (#912)

In general, I'd like to avoid adding dependencies from Fetch spec to specific elements, because Chromium is separating fetch implementation from HTML/DOM implementation (different processes, different directories, etc.). I'm afraid that `fetch request's element` can be used for more frequent interactions between Fetch and elements in the future (in unrelated contexts), which might be hard to implement.

Also, I feel there might be better places (outside Fetch spec) to be associated with elements.
[Element Timing spec](https://wicg.github.io/element-timing/#sec-modifications-DOM) says

> Every image resource that is fetched from a URL has an associated image request, which is a fetch request.

But [image request](https://html.spec.whatwg.org/multipage/images.html#image-request) and [fetch request](https://fetch.spec.whatwg.org/#concept-request) are different.

For example, in the case of

```
<img id="img1" src="a.jpg">
<img id="img2" src="a.jpg">
```

there would be two image requests (one for each `<img>`) and one fetch request.
If Element Timing wants to report two entries (i.e. one `PerformanceElementTiming` entry for each `<img>`) in this case, I expect we want to associate `Element` with image requests (in HTML spec) or something else, not fetch requests.

-- 
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/fetch/issues/912#issuecomment-509379879