[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: overflow: (Re: HTML for KMail ...)
From:       Marc Mutz <mutz () kde ! org>
Date:       2002-07-19 16:26:27
[Download RAW message or body]

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

On Friday 19 July 2002 17:14, Vadim Plessky wrote:
> On Friday 19 July 2002 6:22 pm, Marc Mutz wrote:
> |  On Friday 19 July 2002 15:22, Vadim Plessky wrote:
> |  <snip>
> |
> |  > So, would it be incorporated into KMail's CSS for heders?
> |  > Or there is a chance to use pure XML?..
> |
> |  <snip>
> |
> |  See my previous mail. XML is totally out of the question, since we
> | need to inline HTML content, because of the missing <object>
> | functionality in khtml.
>
> Ok, now I see: <object>  is the real problem in KHTML (not CSS, not
> Tables)
<snip>

Let's say it this way: For KMail, it would make things _a lot_ easier if 
<object width="100%"> would just insert a maximum width frame with the 
content. Esp. with another HTML page. This way, we'd just put every 
body part's content into an <object> of itself and be done with it:
1. It couldn't influcence our css rules
2. It could be hidden and shown with a simple DOM call
3. We wouldn't need to worry about the kind of data shown there, since 
khtml would sort it out for us.

Maybe we should compile a KMail wishlist for khtml ;-)

Marc

- -- 
Marc Mutz <mutz@kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9OD2z3oWD+L2/6DgRAj4jAKDzGRhDxI0SuMBZv0M0WEIPAS4BOACgiVbc
y39ZLD8umpYAfq2MSzNwxXM=
=aOXA
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]