Version: 3.5.8 (using 3.5.8, Gentoo) Compiler: Target: x86_64-pc-linux-gnu OS: Linux (x86_64) release 2.6.22-3-amd64 Hello, Editing Wikipedia (and any Mediawiki website) is very slow with Konqueror when Javascript is enable, to the point that it takes ages to edit anything. Disabling JS makes it much better. No problem to edit the same sites with Firefox or Seamonkey.
How would I go about enabling that mode? Can I see the problem in the sandbox or such?
Yes, you can see that in the Sandbox, but it is much more obvious if the page is long.
I first thought that the problem was because of RAM shortage, but I have 4 GB of RAM now, and I have plenty of free memory. When editing with Konqueror and JS enabled, it looks like as I am editing over an old 56 KB modem line. :( Everything I tape takes forever. However browsing is not a problem, and it is even faster than Firefox / Seamonkey (I usually use Seamonkey for mail and editing).
Could you please give more detailed instructions on how to see the problem; in particular on when you're seeing the slowness? Are you using any fancy features or such?
I notice these delays too sometimes, but I suspected this had something to do with spell checking and not Javascript. I'll try to think of this bug report whenever I come across this problem in the 'wild'.
I observed this behavior just with the Long Description field in KDE Bugzilla. But it was the X server taking much of the CPU time, the Konqueror process appeared to behave normally. Running strace on Konqueror didn't reveal anything strange. strace'ing on the X process is almost impossible to get something useful out of it.
Now I have 3.5.9 and it is not as bad as it was before, although it is still slower than FF and Seamonkey. I found that Konqueror doesn't keep JS in the cache the same way as other navigators. While editing Wikisource, I found that a JS function needed that the cache should be emptied on FF and Seamonkey to take into account the fact that the page was changed. It was not necessary on Konqueror. That might be an indication where is the issue.
Message from the Bugsquad and Konqueror teams: This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore. If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report. Thank you for your understanding.