I thought this slowness was fixed with the jquery updates and subsequent updates? I guess not...

Possibly related: bug 40630. I tried to investigate that one briefly and got nothing.

I reproduced this using my IE and found that it takes 40s until 10 letters appeared after I typed them (which took less than 5s). Also, not only typing was affected but also navigation worked much slower.

Please remember changing your interface language to "de" when you attempt to reproduce the issue.

If you reproduce it, please also remember switching off the user preference at [[Special:Preferences#mw-prefsection-editing]] (section Advanced options, checkbox "Enable input method") You don't have to explicitly activate IME; it starts freezing your browser as soon as you have it just loaded.

Please immediately disable this by default for the affected group, fix it or I will install a JavaScript at Commons that will do the job (disabeling in user preferences if the the user is likely affected by this issue as soon as site js can change prefs after logging in).

You have 24 hours to fix it until I will take action at Commons.

It can't go on that such a serious issue persists for more than 1 month, which is, according to Bug 40630, well known to its developer.

Getting offtopic / meta:

(In reply to comment #3)

You have 24 hours to fix it until I will take action at Commons.

I totally understand frustration, but would you please consider changing your tone to something more friendly and less commanding? Assume people mean well.

It can't go on that such a serious issue persists for more than 1 month,
which is, according to Bug 40630, well known to its developer.

That ticket was filed ten days ago, not sure where the "1 month" statement comes from. It's hard to fix bugs that are unknown.

JavaScript issues in Internet Explorer are notoriously hard to debug. If you
read this, and you can help provide *actionable profiling data*, please do not
hesitate to do so!

It's pretty concerning that Rainer is writing a wall of text with threats here,
without even providing details like Windows version or Internet Explorer
version. I/we understand that the bug is hurting you. Deflecting that pain is
unfortunately not going to help you in getting your issue resolved. Please,
please, please provide as many details as possible so that I/we can take action
instead of share your pain.

without even providing details like Windows version or Internet Explorer
version

IE version is right there in the bug title: IE 8. I've just tested on IE8 and it's reproducable; other wikis (Narayam-less) are snappy, Commons with uselang=de is extremely sluggish, not just for typing, but even for things like navigation or page scrolling. (IE 6 hung when I tried to open the main page, but I'm running it via MultipleIEs and this might causes issues by itself.)

(The bug I linked as possibly related has been reported on IE 6, 8 and 9.)

(In reply to comment #4)

something more friendly and less commanding

I don't command anything. Either it is fixed or I will disable it. I just told
it because I think it's nice if you know about it, in case you want to
reproduce this issue at Commons.

It's hard to fix bugs that are unknown.

Isn't it the job of you paid developers to create software that doesn't cause
more harm than it helps? So why do you often don't test your software in the
real world? It simply sucks that you demand unit tests, statistics etc. from
volunteers but produce software that causes reproducable serious issues in one
major browser.

(In reply to comment #5)

JavaScript issues in Internet Explorer are notoriously hard to debug.

Yes they are but this is no excuse for throwing out Internet Explorer users.
You can use Microsoft Script Editor (
http://en.wikipedia.org/wiki/Microsoft_Script_Editor ); it allows you setting
breakpoints to exactly the position you like, inspecting variables etc. There
is even a video by our well known JavaScript expert Crockford about debuggers.
In IE 8, there are developer tools for free and they are there by default.

It's pretty concerning that Rainer is writing a wall of text with threats here,
without even providing details like Windows version or Internet Explorer
version.

If you would have read the bug title, you would know it's about Internet
Exporer 8. It is on Windows XP. I am pretty sure you can also use Windows 2003
to reproduce it. I am not inclined doing *your work* testing this on all
Internet Explorer versions > 6 and concluding consequences.

I am tired of the characteristic having you paid developers to convince that a
problem exists (e.g. "provide *actionable profiling data*"). It is a minimal
effort trying to reproduce it under Vista and Windows XP (if it is your
argument that you did not know which OS to use). Simply *do it* without
"concerning" about my "wall of text with threats" here.
If you permit me this simile: It's like if I would sell you fizzies instead of
orodispersible tablets and demand you to prove it by measuring/quantifying the
C02 released in your mouth.

The problem-symptoms were described on-wiki more than one time at different
places and different times. I never saw one of you responding there. It was not
hard to run into this bug.

Use your software to see whether it is usable.
If you would be interested in fixing and finding bugs, you would actually use
Wikimedia live sites with different browsers and different settings regularly
instead of swearing on your unit tests or inventing other excuses.

You can use Microsoft Script Editor

Or the Microsoft Script Debugger (which is also fine)
http://www.youtube.com/watch?feature=player_detailpage&v=DwYPG6vreJg#t=2791s

[offtopic again]

(In reply to comment #7)

I don't command anything.

Still there are friendlier (and more productive) ways to express criticism than issuing an ultimatum, aren't there? I wouldn't add "You have 24 hours to provide missing information otherwise I'm going to close your bug report as INVALID" comments either. Of course you can write that you plan to deactivate it soon if there's no fix available - I'm only after your wording.

Isn't it the job of you paid developers

There's no you and me here. No need for fingerpointing or artificial segregation. If QA didn't work out in this case, let's investigate and improve.

(In reply to comment #5)
It's like if I would sell you fizzies

Difference is that nothing is sold here, hence obligations are different.
"Free and Open Source Software is not the same as "the developers must do my bidding." Everyone here wants to help, but no one else has any obligation to fix the bugs you want fixed. Therefore, you should not act as if you expect someone to fix a bug by a particular date or release. Aggressive or repeated demands will not be received well and will almost certainly diminish the impact and interest in your suggestions."
(Last paragraph from https://bugzilla.mozilla.org/page.cgi?id=etiquette.html )

Wild guess by me and Hoo: this is caused by binding four delegate events to the extra ugly selector "input:not([type]), input[type=text], input[type=search], textarea, div[contenteditable=true]" in \Narayam\resources\ext.narayam.core\ext.narayam.core.js, function addInputs(), called in \Narayam\resources\ext.narayam.js.

Possible fixes (if this is actually the issue, I don't have time to check now, I'm just a volunteer):
a) drop the delegation entirely
b) (this is, uh, weird) bind a delegate even to all forms instead, and then, for every form, enable Narayam on it (by binding a delegate event just right now, but on the form, not document) when it's activated (click or mouseover, maybe, or focus on any input inside, if we can detect it without further butt-ugly selectors). I'm not sure if this is a good idea.

Also, this just might get fixed by merging in jQuery 1.8.2 - someone should check this?

(In reply to comment #9)

I wouldn't add "You have 24 hours to

While you wouldn't say it, it happened in the past. Before I could address people's concerns the bug was WONTFIXEd within 24h.

and will almost certainly diminish the impact and interest in your suggestions

This is a critical bug. Neither it is a suggestion nor a feature request. The Wikimedia Foundation is fundraising for the main goal to run its sites. Bugzilla is the bugtracker for this and yes, I can "demand" a Bugfix here. Even in free open source software. Also your interests aren't mine? You aren't interested that MediaWiki works?

As for feature requests, I observed that they were declined or simply not fixed anyway, so it doesn't matter if you are inclined to fix them now or not.

But I don't think it would have grabbed so much attention if I had used a calm and peaceful tone. Sounds paradox but is my experience.

• This bug has been marked as a duplicate of bug 40630 ***