Last modified: 2012-06-19 22:24:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T28291, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26291 - Allow queing load()'s after the first go() as well by implementing a stop()
Allow queing load()'s after the first go() as well by implementing a stop()
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
ResourceLoader (Other open bugs)
1.18.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-09 21:00 UTC by Krinkle
Modified: 2012-06-19 22:24 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2010-12-09 21:00:13 UTC
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();
Comment 1 Bugmeister Bot 2011-08-19 19:12:55 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 2 Krinkle 2012-06-19 22:24:50 UTC
No longer needed. Use cases (both the one mentioned and ones mentioned elsewhere) are either  obsolete, superseded or no longer valid.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links