Wikimedia Bugzilla is closed!

"var matches=s.match(/^(?:([^:]+):)?(.*?)(?:\.(\w{1,5}))?$/)"

Seems to be related to mw.Title class (mediawiki/mediawiki.Title.js).

What were you doing when you saw the bug?

I originally reported this bug to Ironholds; I was viewing http://en.wikipedia.org/wiki/Special:NewPagesFeed - I did it without any extensions in Chromium, and I was still getting that error in the console.

Here is the full error message:
Uncaught TypeError: Cannot call method 'match' of undefined bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.UserBuckets%2CmarkAsHelpful%7Cext.UserBuckets.AccountCreationUserBucket%7Cext.articleFeedback.startup%7Cext.articleFeedbackv5.startup%7Cext.gadget.HotCat%2CNavigation_popups%2CTwinkle%2CUTCLiveClock%2CmySandbox%2Cteahouse%7Cext.pageTriage.external%2Cmodels%2Cutil%7Cext.pageTriage.views.list%7Cjquery.autoEllipsis%2CcheckboxShiftClick%2CclickTracking%2CcollapsibleTabs%2CdelayedBind%2ChighlightText%2Cjson%2CmakeCollapsible%2Cmw-jump%2Cplaceholder%2Cspinner%2Csuggestions%2CtabIndex%2Ctipsy%7Cmediawiki.Title%2Capi%2CjqueryMsg%2Clanguage%2Cuser%7Cmediawiki.action.watch.ajax%7Cmediawiki.api.watch%7Cmediawiki.legacy.mwsuggest%7Cmediawiki.page.ready&skin=vector&version=20120522T032159Z&*:619

Unfortunately, that error message isn't much use for debugging since ResourceLoader groups all the Javascript into one big minified file. Could you go to http://en.wikipedia.org/wiki/Special:NewPagesFeed?debug=true and see if you get the same error? If so, please post the error that you get from that URL. Thanks!

Yep, it's still happening:

Uncaught TypeError: Cannot call method 'match' of undefined bits.wikimedia.org/static-1.20wmf3/resources/mediawiki/mediawiki.Title.js:153

Actually, this appears to be a conflict with an extension I'm using in Chromium, as, when I switch to Private Browsing mode (which disables all extensions), the error message doesn't appear...

Interesting. I wonder if this is the same bug that is causing bug 37023. If you can track down which extension it is, that would be helpful. Thanks for the debugging assistance.

I'll try to isolate the issue.

Any luck tracking down which extension was causing the conflict?

Logan: Did you manage to isolate this?

I am no longer able to reproduce this issue in Chrome 24.0.1294.0 canary on Mac OS X.

Then we'll call it accidentally fixed until it comes up again :)