Attn Marijn

My first suggestion would be both plain and html signatures and trigger 
on the message type when openning up a new message.

As far as editing, display both and allow editing from the same page, so 
there is no confusion as to which one you are editing or that the other 
one even exists.

Lyle

On 05/06/13 20:48, Surgemail Support (Marijn) wrote:
>
> Yes surgeweb does turn on the plain text editor if it detects it is 
> running on an iOS device as there is no html editor available on those 
> platforms like there is on the desktop browsers.
>
> I'd not done any testing in terms of interaction with signature 
> handling, but yes that is expected behaviour and have just run some 
> tests myself which confirms that.
>
> There is no easy way around it no as it stands. What are you proposing 
> as the ideal behaviour for your "way around this"?
>
> Some thoughts, none of which ideal:
> - If plain text editor is detected and signature has html content I 
> just wash wash the html by stripping the html tags. But that is bound 
> to turn into a bit of a dogs dinner as soon as you have any form of 
> significant formatting in an html signature.
> - Possibly easier solution is just to disable the signature addition 
> for plain text messages. Would be easy and I would be in favour of 
> this one, but that is bound to get the signature lovers up in arms.
> - Or separate signature for text mode, but that is a bit ugly in terms 
> of maintenance etc...
>
>
> Marijn
>
>
>
>
> On Sunday 05/05/2013 at 1:16 pm, Lyle Giese  wrote:
>> It looks like iOS makes SurgeWeb turn off the html editor and then 
>> outgoing messages are in plain text and an html signature looks 
>> mangled to the user(it's just showing the html source code actually).
>>
>> I don't have access to an iPad to test, but is there a way around this?
>>
>> Lyle Giese
>> LCR Computer Services, Inc.
>>
>>
>
>
>
>