Last modified: 2012-09-27 01:10:44 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 T26208, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24208 - "undefinedundefinedundefined" are shown in edit page "Special characters" on zh.wiki
"undefinedundefinedundefined" are shown in edit page "Special characters" on ...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.16.x
All All
: Normal normal (vote)
: ---
Assigned To: Adam Miller
http://meta.wikimedia.org/w/index.php...
:
: 24220 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-01 10:30 UTC by Waihorace
Modified: 2012-09-27 01:10 UTC (History)
5 users (show)

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


Attachments

Description Waihorace 2010-07-01 10:30:24 UTC
(See also: http://meta.wikimedia.org/w/index.php?title=2010_Wikimedia_design_and_feature_change/Bug_reports#"undefinedundefinedundefined" are shown in edit page "Special characters" on zh.wiki)

"undefinedundefinedundefined" are shown in edit toolbar "Special characters" list (at the end), please fix it.
Comment 1 Roan Kattouw 2010-07-01 16:28:37 UTC
Adam: I've heard about this bug before but could never reproduce it in FF 3.6. Maybe it's a Chrome thing?
Comment 2 Roan Kattouw 2010-07-01 16:38:38 UTC
In case Adam gets to this before I finish dinner: I think the cause is in the for loop on jquery.wikiEditor.toolbar.js:500 . It's an object-style for .. in loop but the var it iterates over is an array, so it should use for(var i = 0; i < ...
Comment 3 Brion Vibber 2010-07-01 16:44:53 UTC
No problem when I test in Chrome 6 dev / Linux... or Chrome 5.0.375.70 or 5.0.375.86 on Win7.

There may be a particular combination of settings, possibly involving skin, language, and variant preferences, which ends up triggering it. Might also involve other particular options.

Are you getting this bug both when logged in and logged out? Any particular settings we should test?
Comment 4 Roan Kattouw 2010-07-01 17:08:54 UTC
(In reply to comment #3)
> No problem when I test in Chrome 6 dev / Linux... or Chrome 5.0.375.70 or
> 5.0.375.86 on Win7.
> 
> There may be a particular combination of settings, possibly involving skin,
> language, and variant preferences, which ends up triggering it. Might also
> involve other particular options.
> 
> Are you getting this bug both when logged in and logged out? Any particular
> settings we should test?
It's probably some user script or, more likely, a library, that's messing with Array.prototype .
Comment 5 Adam Miller 2010-07-01 17:25:30 UTC
Roan, I tried but can't replicate it. I'm out the rest of today, but can look again late tonight or tomorrow if you can't figure it out.
Comment 6 Roan Kattouw 2010-07-01 17:55:00 UTC
Fixed in r68841. My suspicion from comment #4 was right: morebits.js (used by Friendly and Twinkle, two fairly popular user scripts) adds functions to Array.prototype and we had the wrong kind of for loop iterating over the special character arrays.
Comment 7 Max Semenik 2010-07-01 21:46:56 UTC
*** Bug 24220 has been marked as a duplicate of this bug. ***

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


Navigation
Links