-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello devs,
I'd like to propose the use of js for Savane (or some more use thereof). All the work going on to make the interface and client rendering in general 'better', seems to touch the sort of code/paths where some js would come in handy/be nice for some users. I know some of us like to use lynx (Just me? ;-) and other text-only (w/o js) browsers, so it would not be a good idea to enable by default, I guess, but what about clients we know have (at least basic) js i.e., Moz, Konq/Safari, MSIE? Or, a new user preference to enable/disable js globally (but wouldn't be used (at all?) in the home|main, login, logout, change password/fetch password hash and change user prefs pages, so the user can fix if needed) ? Some examples I can quickly think of: selection of all artifacts and moving them to another tracker, select all in lists (most admin areas - could also enable some 'command' like buttons), confirmation of deletion of 'stuff', general user alerts, etc.. This could of course add more places where XSS 'sploits could be inserted, but shouldn't be hard enough to cast/strip completely. (Though, IMO, if you follow a link without looking at it with an un-trustworthy eye, you're asking for trouble ;-) Does this sound interesting? :-) Hmm.. Maybe we could have a RFC/SEP(Savane Enhancement Proposal ;-) directory in CVS/items on the trackers @ gna.org like the post-it's, for this kind of stuff, too? Elfyn - -- Elfyn McBratney beu on irc.freenode.net/savannah.[non]gnu.org PGP Key ID: 0x456548B4 PGP Key Fingerprint: 29D5 91BB 8748 7CC9 650F 31FE 6888 0C2A 4565 48B4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBU9BDaIgMKkVlSLQRAsQrAJ9MvX5E3lnXPVmb9LI1oce/Dcv1AgCfS4n+ kRRO2GRlOfHW+LDdTwkD9eY= =OVDX -----END PGP SIGNATURE----- _______________________________________________ Savane-dev mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/savane-dev
