Last modified: 2012-05-03 02:42:46 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 T36664, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34664 - Javascript errors in firebug and page flash on commons when debug=true
Javascript errors in firebug and page flash on commons when debug=true
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
1.19
All All
: High normal (vote)
: 1.19.0 release
Assigned To: Nobody - You can work on this!
https://commons.wikimedia.org/wiki/Ma...
:
Depends on:
Blocks: 31217
  Show dependency treegraph
 
Reported: 2012-02-24 00:53 UTC by Mark A. Hershberger
Modified: 2012-05-03 02:42 UTC (History)
3 users (show)

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


Attachments

Description Mark A. Hershberger 2012-02-24 00:53:56 UTC
Firebug gives me the following error when going to the main page with debug=true while not logged in:

  skin is not defined
  https://commons.wikimedia.org/w/index.php?title=MediaWiki:AnonymousI18N.js&
  action=raw&ctype=text/javascript
  Line 14

Note that the page flashes with content and then goes blank.
Comment 1 Brion Vibber 2012-02-24 01:07:18 UTC
I can confirm this, but it's damned odd.

End up with a web page that's empty except for loading the MediaWiki:AnonymousI18N.js in its <head>.... very weird.

I wonder if importScript() (via mw.loader.load) is somehow breaking very badly, but only in debug mode and only specific times/ways?
Comment 2 Roan Kattouw 2012-02-24 21:37:54 UTC
(In reply to comment #1)
> I can confirm this, but it's damned odd.
> 
> End up with a web page that's empty except for loading the
> MediaWiki:AnonymousI18N.js in its <head>.... very weird.
> 
That's probably someone using document.write() when they shouldn't.
Comment 3 Mark A. Hershberger 2012-02-25 18:24:39 UTC
See also Bug 34696
Comment 4 Mark A. Hershberger 2012-02-25 19:09:24 UTC
in any case worksforme now

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


Navigation
Links