https://bugzilla.wikimedia.org/show_bug.cgi?id=34861
--- Comment #4 from kipod <[email protected]> 2012-03-01 20:03:20 UTC --- thanks for the pointer - will do that. i still think that it makes little sense to require adding dependencies on core functions as in "mw.user", "mw.options" etc. it can also creates problems for things in site common.js, and personal common.js. these do not have the dependency mechanism, so they are left with the need to package parts of themselves in "mw.loader.using()", just in order to gain access to username. most people will take the easy way out and will revert to using wgUserName - exactly the opposite of what we want to happen. to summarize: i still think it's a bug, even though the dependency mechanism offers a solution for gadgets, IMO this solution is a "bug workaround" rather than a legit answer, and it does not provide solutions for site common.js and personal common.js peace. (In reply to comment #1) > (In reply to comment #0) > > Have you added the module "'mediawiki.user" as a dependency for that gadget, > on > MediaWiki:Gadgets-definition? > > See > * [[ResourceLoader/Migration guide (users)#Migrating user scripts]] > * [[ResourceLoader/Default modules]] > for more info. upon reading, it actually lists mw.user as one of the "default modules", which i read as "modules which are always available". the problem is that "mw.user" exists, but parts of the functionality (specifically, "mw.user.name()") are still missing when the gadgets run, so on further examination - definitely a bug. peace. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
