Christian Boltz wrote :
> Am Samstag, 22. November 2008 schrieb David Goodwin:
> > Christian Boltz wrote :
> > > c) add a "show password" link (with a $CONF setting to enable it,
> > > default should be disabled) which displays the password
> > > somewhere (using flash_info or a alert() feeded with a AJAX
> > > request) This would have some advantages:
> > > - it works in every browser, not only if you have some extension
> > > - it only transfers the password on request - which reduces the
> > > risk (and number) of passwords in browser cache etc. a lot - it
> > > fixes all the problems in edit-mailbox I described above - it would
> > > easily allow to mail a notification to the user, which might be
> > > required by some people/companies for privacy or policy reasons
> > c) sounds good, but I've no motivation to write it; so either we
> > ditch the change, or someone writes a patch...
> I reverted the patch for now (r485) - and opened a feature request so
> that we don't forget about it:
> > (So far, Postfixadmin is AJAX free, perhaps it should stay this way?)
> I don't want to do "big" things with AJAX. But I don't see a problem in
> using something like
> The fallback could be that the "show password" link uses flash_info for
> this - with the disadvantage of causing a page reload (and possibly
> loose changes).
> BTW: I don't see a real problem with AJAX - nearly every browser I know
> supports it. OK, you could argue with lynx or even netscape 4 ;-) - but
> people using lynx are probably the same that do a quick query in MySQL
> if they want to find out the password. And people using netscape 4,
> well, that's their own fault *g*
I don't have anything against JS; aside from to use it properly should
really pick and standardise on an appropriate JS library!
[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk ]
Get latest updates about Open Source Projects, Conferences and News.