Bugzilla

(In reply to Ben Bucksch (:BenB) from comment #70)
> > For those sending only plaintext:
> >   Update the compose editor to disable rich text (links, images, etc)
> >   Sanitize pasted or dragged text to remove links, images, etc.
> >   Disable all menu items that interact with those elements
> 
> We have patches for that, and we'll contribute them - in a new bug ticket, to avoid having too much happening here in this bug.

Is this bug with patches coming soon? We would something before 102 for the new text in the preferences to make sense.

Also, how do we plan on handling when a user selects "Options > Send Format > Only Plain Text" during composition? Are we going to similarly disable the styling elements? Also, what should we do with the existing message at this point? If we sanitise it we should warn the user if it will lead to data loss. We also need to consider what would happen if the user then presses Control+Z: just like that I suspect the xul:editor would reverse the sanitisation. If no one has a nice clean solution for this, I'll open a separate bug and we can just leave it as it was -- silently convert the message, with potential data loss, when we send it -- until we figure something out.

(In reply to Ben Bucksch (:BenB) from comment #70)
> > For those sending only plaintext:
> >   Update the compose editor to disable rich text (links, images, etc)
> >   Sanitize pasted or dragged text to remove links, images, etc.
> >   Disable all menu items that interact with those elements
> 
> We have patches for that, and we'll contribute them - in a new bug ticket, to avoid having too much happening here in this bug.

Is this bug with patches coming soon? We would need something before 102 for the new text in the preferences to make sense.

Also, how do we plan on handling when a user selects "Options > Send Format > Only Plain Text" during composition? Are we going to similarly disable the styling elements? Also, what should we do with the existing message at this point? If we sanitise it we should warn the user if it will lead to data loss. We also need to consider what would happen if the user then presses Control+Z: just like that I suspect the xul:editor would reverse the sanitisation. If no one has a nice clean solution for this, I'll open a separate bug and we can just leave it as it was -- silently convert the message, with potential data loss, when we send it -- until we figure something out.