[dev] Full HTML/CSS support on message view

[Michael M Slusarz]

Quoting Rui Carneiro <rui.carneiro at portugalmail.net>:

> On Thu, Sep 10, 2009 at 9:20 PM, Michael M Slusarz <slusarz at horde.org>wrote:
>
>> Quoting Rui Carneiro <rui.carneiro at portugalmail.net>:
>>
>>> First step is to embed the message on an iframe before showing the
>>> message.
>>> This will "reset" all previous CSS conditions so we might need to set a
>>> few
>>> like font family, size or color.
>>>
>>
>> Agreed.  We can simply create a stripped down-stylesheet for this purpose
>> (so that it is cached by the server).  For dimp, it will be easiest to
>> create a hidden iframe on load, and then clone this iframe as needed to view
>> the HTML code.
>>
>
>  So your idea is to create 1 iframe for each html part of the message?

Yes.  There may be more than 1 HTML part viewed inline, and these  
parts may have other, non-HTML parts inbetween.

>> This "#horde_unique_id" should be the id of the element (e.g. div) where
>>> the
>>> email message will be shown. This way only the elements inside
>>> "horde_unique_id" will be affected by message's CSS.
>>>
>>
>> I don't understand why we need this.  If the message part contains CSS
>> definitions, it will only be applied within the iframe.  And none of the
>> base Horde CSS will be applied within the iframe.
>>
>
> I think AOL (Yahoo might be working on it) use this to simplify forward and
> reply messages. When you click forward on a html message on this client,
> they transform the body element to one div with an unique id (e.g. <div
> id="horde_unique_id">). This prevent the new message's CSS from corrupting
> the forwarding one.

We don't add any CSS to outgoing messages, so this is irrelevant.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]