- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Feb 2014 20:42:56 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24564 --- Comment #10 from Gabor Krizsanits <gkrizsanits@mozilla.com> --- Hmmm... the latest version seems very promising so far. I have a few concerns regards of performance, but I think we should focus first on the right behaviour and this version is pretty clear in that respect. I guess the only part I'm not sure is, why do we need to block fetching (fetch readiness) instead of just block script execution in the very same way as the algorithm describes (just with 'ready for script execution' flag in the list). Is there a reason why in your example c should not be fetched/parsed with its scripts blocked before b is done? The other part is not entirely clear how all these algorithms in the spec work together exactly. More specifically when should one check for fetch readiness? Every time an import finishes we find the next candidate that can be fetched? One thing for the map. I wonder if it would make sense to make it a <location, loader> map instead of a <location, import document>. But I guess this is more like an implementation detail... -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 13 February 2014 20:43:02 UTC