Bug 132858

Summary: password dialogs are not wide enough
Product: [Applications] kdepasswd Reporter: Martin Fabian Hohenberg <martin.hohenberg>
Component: generalAssignee: Geert Jansen <g.t.jansen>
Status: RESOLVED DUPLICATE    
Severity: normal CC: finex, mboquien
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Please note that there is no way to get an idea of what host requests the password

Description Martin Fabian Hohenberg 2006-08-23 13:17:13 UTC 
Version:           3.5.4 (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu2~dapper1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

Currently, the password dialogs have a somewhat fixed width. Most of the time, the dialog width is not sufficient for displaying the hostname. This is a usability bug, because especially in applications that make use of the network transparency part of KDE such as quanta, the user does not necessarily only work with one host, and does not know for which host a password dialog is opened. The user now has to manually resize the password dialoge to get that information.

It would be better if the dialog title automatically gets a width that is sufficient for displaing the hostname. Alternatively, the hostname should come first in the title bar. 

See screenshot for problem (my english is rather shaky)
Comment 1 Martin Fabian Hohenberg 2006-08-23 13:18:07 UTC 
Created attachment 17467 [details]
Please note that there is no way to get an idea of what host requests the password
Comment 2 FiNeX 2008-12-26 15:42:48 UTC 
Someone can confirm the current situation? I've tried to login on a couple of website and the current width seems right to me.
Comment 3 Christoph Feck 2010-06-07 23:33:10 UTC 
KIO dialogs that request a password display the requesting host name within the dialog instead of the window title.

*** This bug has been marked as a duplicate of bug 231241 ***