- From: jugglinmike <web-platform-tests-notifications@w3.org>
- Date: Fri, 17 Feb 2017 16:39:30 GMT
- To: public-web-platform-tests-notifications@w3.org
> It would work to work around that by waiting for `window.onload` instead,
> correct?
Yes, and that is far simpler/more readable. I've updated the patch to do that.
> The test that checks the later stylesheets (`for (i = 5; i < 8; i++) {`)
> should also do the waiting?
It couldn't hurt! (For reference: this is not technically necessary because the
Chromium instability is limited to "alternate" stylesheets with a non-empty
`name` attribute. In those cases, it exhibits a strange "deferred loading"
behavior: the resource is fetched, and that operation influences the timing of
the `onload` event, but it does not block page evaluation (despite the `<link>`
tag being declared in the head).
View on GitHub: https://github.com/w3c/web-platform-tests/pull/4828#issuecomment-280700429
Received on Friday, 17 February 2017 16:39:42 UTC