--===============0247231056==
Content-Type: multipart/signed;
  boundary="nextPart2662034.MNFseJXT95";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2662034.MNFseJXT95
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le Vendredi 18 F=C3=A9vrier 2005 04:08, Jason Keirstead a =C3=A9crit=C2=A0:
> CVS commit by brunes:
>
> New Adium JS style. The patch I sent into the list was wrong again - it is
> simpler to just commit and if some people really hate it then revert.
>
> I encourage everyone to try and compare Adium_JS to Adium. If the new sty=
le
> suffices, we can get rid of the other Adium and use this one only.
>

> --- kdenetwork/kopete/kopete/chatwindow/chatmessagepart.cpp  #1.22:1.23
> @@ -170,5 +170,5 @@ ChatMessagePart::ChatMessagePart( Kopete
>
>          //Security settings, we don't need this stuff
> -        setJScriptEnabled( false ) ;
> +        setJScriptEnabled( true ) ;


=46or security reason, this shouldn't be commited.

There is still many ways to inject html (and then script) in the chat windo=
w.
Protocol that may support html rich text where the html string is simply=20
passed to the chatwindow.
The PGP plugin which can interpret the resulting code as html (you even did=
=20
that yourself)

I'm against that.

--nextPart2662034.MNFseJXT95
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCFd4zz58lY8jWrL0RAuivAJ9cdm9pltOB7yeZ8k84FFAG1//ydgCdFX1A
0I/ZInp/jqao0nUuPAdeDV8=
=5lqn
-----END PGP SIGNATURE-----

--nextPart2662034.MNFseJXT95--

--===============0247231056==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

--===============0247231056==--