--===============3288439200166251==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_d3i5+Z8SS1OtdY1";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_d3i5+Z8SS1OtdY1
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 04 June 2003 23:54, Ingo Kl=F6cker wrote:
<snip>
> IIRC up until KDE 3.1 it wasn't possible to tell khtml which style
> sheet it should use. Marc should be able to give you more precise
> information because it was him who looked at that several moons ago.
<snip>

The problem was that khtml didn't accept a setUserStyleSheet() when no=20
document was present and that a stylesheet loaded via the <link> tag=20
wasn't checked for changes.

I don't think we should go for xml+css yet. It certainly has appeal, but=20
I don't see how inline content (think image/*, text/html) can be=20
processed in this framework.

I'm all for moving all physical markup to use CSS, though, and will add=20
that as during the html formatting rework that's underway (see my resp.=20
wishlist item on bugs.kde.org ;-)

Marc

=2D-=20
The illegal we do immediately.
The unconstitutional takes a bit longer.            -- Henry Kissinger

--Boundary-02=_d3i5+Z8SS1OtdY1
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA+5i3d3oWD+L2/6DgRAqFAAJoClJ1S1naECVtIJWHqSEeChqRZSACgq5hy
XMtJz94FnM9j9iW5stCjjr4=
=VPUh
-----END PGP SIGNATURE-----

--Boundary-02=_d3i5+Z8SS1OtdY1--


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

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

--===============3288439200166251==--