Currently there's only one load-queue being made and as soon as go() is called, any load() results in a direct server requests.

Tools, gadgets and big user scripts can benefit from the ability to queue things as well and make a server request happen with go() when they want it.

According to Trevor this should not be the default behaviour (ie. after the initial go() call was made any load() should by default directly result in a server request) - but agreed that having a flow like this in a gadget is not bad at all:

mw.loader.stop().
mw.loader.load( ... );
mw.loader.load( ... );
mw.loader.go();

Version: 1.18.x
Severity: enhancement