Last modified: 2013-03-06 05:26:39 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 T30846, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 28846 - Make it possible to debug private mw.loader variables
Make it possible to debug private mw.loader variables
Status: NEW
Product: MediaWiki
Classification: Unclassified
ResourceLoader (Other open bugs)
1.17.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-05-06 05:35 UTC by Tim Starling
Modified: 2013-03-06 05:26 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Tim Starling 2011-05-06 05:35:22 UTC 
Please use less private member variables (i.e. constructor function scope) in ResourceLoader. Especially mediaWiki.loader.registry, mediaWiki.loader.jobs etc. Using public variables in such circumstances would make it easier to support and easier to isolate bugs. 

Alternatively, develop a patch for Firebug which allows private variables to be viewed.
Comment 1 Trevor Parscal 2011-05-06 17:07:30 UTC 
The problem with exposing these is that people will start using them directly, and relying on them, causing the implementation to be unchangeable without breaking backwards compatibility.

If we need better debugging functionality, then lets add that in with methods that allow read only access to the otherwise private data.
Comment 2 Tim Starling 2011-06-23 01:05:49 UTC 
OK, updated bug summary.
Comment 3 Bugmeister Bot 2011-08-19 19:12:58 UTC 
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 4 Krinkle 2013-03-06 05:26:39 UTC 
These, at least anno 2013, can be trivially inspected in Chrome Dev Tools when setting a breakpoint (or inspecting it directly during run time).

I dont know about Firebug.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links