RFC: Access Control over JavaScript Properties Globally and Per-Domain

[David Faure]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 13 October 2002 21:17, Daniel Naber wrote:
> On Sunday 13 October 2002 20:15, Leo Savernik wrote:
> 
> > Currently Java, JavaScript and Plugins are handled on separate tabs
> > though their configuration data is saved under the common key
> > [Java/JavaScript Settings]. Ui-wise that should stay that way,
> 
> I think allowing Java/javascript etc. is about "trust", and if you trust a 
> website to have useful and secure javascript, you normally trust it to 
> have useful and secure java and plugins, too. So I think all these (domain 
> specific) settings belong together into one dialog.

And how are you going to name that dialog? "Trust"? ;-)

I think it's better to have per-domain JS settings together with the global JS settings,
per-domain nsplugins settings together with the global nsplugins settings, etc.
Otherwise, you have to either merge everything into one monster dialog,
or separate global settings from per-domain settings, which doesn't sound optimal either.

Note that the kdeaddons "HTML configuration" plugin allows to change
all those things in a central place for a given domain (assuming someone adapts
that plugin to save the settings as per-domain settings, once Leo's change is done),
so the splitting of the configuration options for a given domain in kcontrol won't
be a big usability problem imho.

- -- 
David FAURE, david at mandrakesoft.com, faure at kde.org
http://people.mandrakesoft.com/~david/
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
Get the latest KOffice - http://download.kde.org/stable/koffice-1.2/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9qpz872KcVAmwbhARAk9hAJ0c6s2dpS1BcxxmbmaxCb3V6JPxfwCfVfOa
WCG19+twzHrLv2Ye7qqEF7E=
=it8H
-----END PGP SIGNATURE-----