Last modified: 2011-05-05 17:49:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 27605 - Script errors displayed in Internet Explorer 7
Script errors displayed in Internet Explorer 7
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal trivial (vote)
: ---
Assigned To: Krinkle
Depends on:
  Show dependency treegraph
Reported: 2011-02-21 11:18 UTC by Nadeesha
Modified: 2011-05-05 17:49 UTC (History)
2 users (show)

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


Description Nadeesha 2011-02-21 11:18:05 UTC
Script errors are getting displayed in the followings.


2. (page edit)




6. (recent changes)


8. (page edit)


10. (page edit)


12. (page edit)





17. (page edit)




21. (recent changes)
Comment 1 Mark A. Hershberger 2011-02-22 02:10:32 UTC
not sure if this is a MW/RL problem or something particular to WMF wikis. Marking as a WMF problem for now.

Tested on and got

"onloadFuncts.length is null or not an object" Using debug=true, I found it was from this area:

59 window.addOnloadHook = function( hookFunct ) {
60 // Allows add-on scripts to add onload functions
61 if( !doneOnloadHook ) {
62 onloadFuncts[onloadFuncts.length] = hookFunct;
63 } else {
64 hookFunct(); // bug in MSIE script loading
65 }
Comment 2 Krinkle 2011-03-08 21:58:00 UTC
Mostly broken javascript, deprecated functions and a few breakages due to the HTML structure/order that has changed in 1.17

Will move all of those wikis up in my Tour project [1]. I go through them by alphabet but I'll go through those first (I've done a few others like that as well).

Summarized my activity/checklist during the 1.17-edition of the Tour:
* Fix broken javascript that thows exceptions and warnings
* Update any calls to deprecated functionality with their successors to avoid breaking again when the deprecated functions are removed and to be future-proof
* Remove any redundant defintions, statements and declerations in CSS that are now in-core
* Validate with JSHint (atleast with non-strict options)
* Where applicable contact the local JS developer(s) and make further suggesions with what's posisble with the new modules [2] (modules that aren't successors but simply new)


Comment 3 Krinkle 2011-03-09 00:54:53 UTC
Removing blocker for now. Cannot be fixed in core, but local javascript.
Comment 4 Krinkle 2011-05-05 17:49:28 UTC
Most of these have been tour[1]'ed in the mean time.

Although not all of the linked wikis above have been toured yet, regardless, this is still not a bug in the software (atleast not anything specific).

Marking INVALID.


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