Bug 146616

Summary:	wordpress 'new post' make khtml freeze several times before loading
Product:	[Applications] konqueror	Reporter:	Chani <chanika>
Component:	khtml	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	finex, maksim
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Chani 2007-06-10 05:45:03 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

when I go to write a new post in wordpress, it takes about 30 seconds to load the page.
first, it does nothing for about 5 seconds (that's probably my lag). then it freezes for a couple of seconds. then I get the standard 'this script is freezing khtml' dialog and abort it. it freezes again for about 10 seconds, then shows the dialog again. after I abort, it freezes for another 5 seconds or so, and then finally displays the page.

since wordpress decides to load the same page again when I click 'publish', I have to go through this process twice for every new post. however, if I go to edit an existing post, this doesn't happen - the page loads just fine.

this has been going on since at least 3.5.5 - I reported it to wordpress, they ignored me, I forgot about it for a while, so now I'm hoping you guys can find a fix. :)

Comment 1 Maksim Orlovich 2007-06-10 17:35:07 UTC

Hi, could you please give a step-by-step on how you trigger it? Don't see it here in my (post-3.5.7) work tree.

Comment 2 Chani 2007-06-11 06:18:56 UTC

maksim: I simply go to http://chani.wordpress.com/wp-admin/post-new.php and it happens.
sadly I just deleted my gentoo partition, or I'd test it there... I wonder if it's a kubuntu thing.

Comment 3 Maksim Orlovich 2007-06-11 20:52:34 UTC

Hmm, doing the same on the test account doesn't seem to trigger that.. I'll see what versions my other machines have...

Comment 4 Chani 2007-06-13 09:55:31 UTC

possibly useless info: from kde4, the page takes about the same time to load, but doesn't need me to click anything - I guess it just kills off the messed-up javascript by default. I would've made a test post from kde4, but konq crashed when I hit the tab key :)

btw, the test account doesn't seem to have the password that was posted any more. I wanted to rule out the possibility that there was something weird about my personal account, however unlikely that may be.

Comment 5 Roland Wolters 2007-07-07 16:02:06 UTC

I had the same problem on Fedora, but it has been gone with the Update to KDE 3.5.7.
Can you test with a KDE 3.5.7 version if the problem still exists?

Comment 6 Chani 2007-07-08 07:17:33 UTC

it's hard to tell. I eventually clicked the little "don't ask again" box so 
that I wouldn't have to press a button to kill frozen javascript. it still 
takes a long time to load the page, but seems to spend only a couple of 
seconds actually frozen, instead of the 5-10 I had with 3.5.6 - but of course 
3.5.7 also seems to have brought a new bug. I'll go report that now.

Comment 7 Maksim Orlovich 2007-07-08 07:31:09 UTC

Any chance the bug you're going to report is this:
http://bugs.kde.org/show_bug.cgi?id=147661 ?

Comment 8 Chani 2007-07-08 07:36:13 UTC

> Any chance the bug you're going to report is this:
> http://bugs.kde.org/show_bug.cgi?id=147661 ?


yes, thanks :)

Comment 9 Naresh V 2008-04-25 20:35:11 UTC

I tried reproducing the bug a few minutes ago on Konqueror 3.5.9 and a wordpress.com blog. Wordpress.com is currently using version 2.5.*

The /wp-admin/post-new.php page loads just fine. Couldn't reproduce this bug.

Comment 10 Naresh V 2008-04-25 20:42:23 UTC

I'm sorry for the typo. This was tested using 3.5.7 on openSUSE 10.3.

Comment 11 Chani 2008-09-13 22:49:37 UTC

I'm not seeing this at all in recent kde4. should we close it?

Comment 12 FiNeX 2009-11-07 14:34:30 UTC

Someone else confirm that the bug is no more reproducibile on KDE 4?

Comment 13 Chani 2009-11-07 19:27:13 UTC

gosh, I'd forgotten about this. I'm pretty sure it's fixed.

Comment 14 FiNeX 2010-03-13 15:38:55 UTC

Yes, I can confirm it has been fixed.