- From: Ilya Grigorik <web-platform-tests-notifications@w3.org>
- Date: Thu, 25 Aug 2016 16:27:34 GMT
- To: public-web-platform-tests-notifications@w3.org
```
+ observer.observe({entryTypes: ["resource"]});
+ var img = document.createElement("img");
+ img.src = img_location;
+ document.body.appendChild(img);
+ img = document.createElement("img");
+ img.src = img_location;
+ document.body.appendChild(img);
+ }, "Only one resource entry per resource");
```
It's still not clear to me if this is correct. If you follow the RT processing model verbatim, then there should be multiple records, since the second image should (at least in theory) initiate a fetch, which should then hit the appropriate caches and pull out the right data.
However, in practice, in Chrome you only see one request because the request is fulfilled via the ~"renderer memory cache", which is not specified anywhere... I think we should solve that first (probably within Fetch), and then we'll be in a position to answer this.
/cc @toddreifsteck @annevk
View on GitHub: https://github.com/w3c/web-platform-tests/pull/2919#issuecomment-242451855
Received on Thursday, 25 August 2016 16:27:42 UTC