I've just switched to trying Chrome's native promises with the polyfill and am getting a different callback ordering. This is affecting ProcessLoadDependencies at the following section:
1.1.1.15 (1a) RequestLoad is called for the load record.
1.1.1.16 (5) The load record is added to the linkset.
The issue is that proceedToFetch is running 1.1.1.11 CallFetch before the load record is added to the linkset. This then invokes the failure check if load.linkSets.length == 0 return since it thinks there was a load failure.
The fix is to change this failure check to if load.status == 'failed' instead.
This may be Chrome's promise implementation acting up. But it may be worth noting.
guybedford
commented
10 years ago
I've just switched to trying Chrome's native promises with the polyfill and am getting a different callback ordering. This is affecting
ProcessLoadDependenciesat the following section:The issue is that proceedToFetch is running 1.1.1.11 CallFetch before the load record is added to the linkset. This then invokes the failure check
if load.linkSets.length == 0 returnsince it thinks there was a load failure.The fix is to change this failure check to
if load.status == 'failed'instead.This may be Chrome's promise implementation acting up. But it may be worth noting.