tb-planning at ilias.ca
Tue Mar 27 00:34:42 UTC 2012
On 12-03-26 7:40 AM, Axel wrote:
> On 24/03/12 20:22, JoeS wrote:
>> On 3/23/2012 7:41 PM, Unicorn.Consulting wrote:
>>> Bug 250539 <https://bugzilla.mozilla.org/show_bug.cgi?id=250539> is
>>> one that appears in support on a regular basis and clearly is a big
>>> I would also suggest that introducing Compose in a tab without fixing
>>> the composer code would be worse than doing nothing at all. Users are
>>> disgruntled but sort of accepting that the composer is clearly not
>>> getting any attention. Introducing the 'compose in a tab' without due
>>> fixes to the composer would rightly or wrongly lead users to the view
>>> that the composer is receiving attention, but it is the fancy stuff,
>>> not the basic usability of the composer and it more than likely going
>>> to upset them
>> I must agree completely here.
>> Compose in a tab is just another rendition of broken editor.
> Yes, better CSS support would go a long way towards fixing the Composer
> as well. I find that I can do quite fancy stuff (when using stationery
> in order to edit the html), without too much effort; a style editor for
> the styles dropdown with some nice templates might be a first "cheap"
> step. Only problem is the CSS compatibility with other mail programs;
> e.g. AFAIK outlook still expects css styles to be inline, so there would
> have to be an optional "compatibility mode" when sending out emails.
For clarification, are you guys saying that compose in tab should not be
implemented, unless bug 250539 is fixed?
On 12-03-26 12:25 PM, Mike Conley wrote:
> Since it was before my time, I'm curious to know what happened to the previous attempt at this...what went wrong?
I think what you're remembering was the "Compose for Thunderbird"
extension, which not only moved the compose window to a tab, but also
completely replaces the current compose window with CKEditor. See
Jonathan stopped working on it almost a year ago, because he didn't have
More information about the tb-planning