[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 42707] Javascript speed problem (http://nagoya.apache.org)
From:       smileyjonathan () yahoo ! com ! au
Date:       2002-10-31 2:41:10
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=42707     




------- Additional Comments From smileyjonathan@yahoo.com.au  2002-10-31 03:41 -------
I think the bugzilla login ate my formatting.  I'll try that again in the hope 
you can read it more easily... 
 
Warning: I'm only running Konqueror 3.0.4, not 3.1-rc1.   
   
While speed is an issue, there's a more serious problem.  While JavaScript is   
running, Konqueror freezes completely.  There's no feedback to tell a user   
it's busy doing something.  No menus or buttons work, if other windows are   
brought to the front, they are not redrawn, etc.   
   
See my later bug report #42707 on how I think a well-written piece of software   
should behave in such circumstances.  Somebody else has the same problem in   
bug #36914.  Although #422707 is listed as resolved, I don't believe the   
resolution is satisfactory.   
   
  If a piece of software isn't responding at all to user input, isn't   
redrawing exposed windows and there's no visible sign that something is going   
on, most people won't wait 30 seconds before concluding it's broken.  I think   
it will be very hard to find a "good" timeout value given the variety of   
machine speeds and scripting requirements out there.  The popup is a bandaid  
solution.  
   
  Could you at least spin the toolbar cog image while the interpreter is  
running and allow the stop button to abort the script?  Can I also suggest you  
write "JavaScript running" in the status line, but in a way that text (perhaps  
maliciously) written to Window.status doesn't clobber it?  The area where the  
download progress bar appears may be a good spot.  
  
  Ideally, run the user interface in a spearate thread.  That way the user  
doesn't have to hunt for the window that is hanging the entire Konqueror  
application and stop it.  JavaScript that creates new windows can make it hard  
to find the culprit.  
   
  On the speed comaprison, although , Konqueror 3.0.4 takes at least 5 times  
as long to run the script as Mozilla 1.0 (Mozilla/5.0 (X11; U; Linux i686;   
en-US; rv:1.0.0) Gecko/20020529).  
  
    Mozilla 1.0: 9 seconds  
    Konq 3.0.4:  48 seconds (5 times slower)  
  
Sorry, for being so difficult.  I'd like to contribute to actually solving the  
problem, but I just don't have time (not even to download 3.1-rc1).  Hopefully  
the detailed bug report and suggestions help in some small way.
_______________________________________________
Konq-bugs mailing list
Konq-bugs@mail.kde.org
http://mail.kde.org/mailman/listinfo/konq-bugs
[prev in list] [next in list] [prev in thread] [next in thread]