[Kst] [Bug 143854] Exiting the JavaScript console removes all tabs

George Staikos staikos at kde.org
Thu Apr 5 19:03:07 CEST 2007


------- 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=143854         




------- Additional Comments From staikos kde org  2007-04-05 19:03 -------
> OK... we can't fix it totally... but having a trivial way to render  
> kst dead
> that the user wouldn't expect would kill kst is not a good thing.
>
> Is there anything we can do to reduce the cross-section for this bug?
> eg,
> 1) is it easy to disable the command "exit" from javascript, so you  
> wont
> trigger the bug that way.


    It's not a javascript command, it's a kstcmd command.  However  
then there is no way to exit it if run from the commandline if we  
remove exit and ctrl+d.  We're trading one of many bad situations for  
another.

> 2) is it easy to make ctrl^d a global shortcut to do nothing at all?


    I think so.

> Do either of these choices have any obvious problems?


    All of this is probably more work than

    Also, for example, the user can access anything in the UI and do  
all kinds of whacky things with KstUI.  Remember you can't protect  
users from themselves and there is always going to be a way to make  
Kst crash or behave strangely.  At least we don't crash.  If this  
(very) corner case happens, the user can File->Save As, exit, reload,  
and continue.  And we can fix KMDI in 1.4.1 or later.

   Making it impossible to exit the command prompt as a workaround  
for a bug in a KDE component really doesn't make any sense to me.

--
George Staikos
Staikos Computing Services Inc.      http://www.staikos.net/


More information about the Kst mailing list