- From: Philippe Le Hegaret <plh@w3.org>
- Date: Fri, 04 Apr 2014 15:40:57 -0400
- To: Christian Biesinger <cbiesinger@google.com>
- Cc: public-web-perf@w3.org
On Tue, 2014-04-01 at 19:32 -0400, Christian Biesinger wrote: > Hi there, > > I was looking at test_resource_reparenting.html and I think it is > incorrect. Per the HTML spec, image loading is triggered > asynchronously, see step 8 here: > http://www.whatwg.org/specs/web-apps/current-work/multipage/edits.html#update-the-image-data > > As a result, if an <img> element gets re-parented immediately, it > abort the initial async task, and queue a new async task for the new > document. So, only move_to_child should show up in the resource list > here. I believe you're correct. Since there is no cache involved, the fetching algorithm will always get aborted and no resource will get fetched. I added your issue to https://critic.hoppipolla.co.uk/r/393 I need to go through them at some point. Help is welcome btw. > Incidentally, I can't find a repository that contains that test, I can > only find an open pull request: > https://github.com/w3c/web-platform-tests/pull/402/commits > The webperf repository doesn't seem to have the test anymore? It got moved to github now indeed and the tests are awaiting corrections and reviews: https://github.com/w3c/web-platform-tests/issues?labels=wg-webperf&state=open I added https://dvcs.w3.org/hg/webperf/file/8de44381205b/tests/SEE_GITHUB_INSTEAD.txt in the hope of making it clearer -- Philippe
Received on Friday, 4 April 2014 19:41:00 UTC