| October 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
| Sep Nov | ||||||
This site is no longer maintained.
My current weblog.
Thursday, October 17, 2002"Composite is a chrome overlay which enables a streamlined Mozilla Editor for html composition in textareas. To use the editor, hit ctrl-e in a textarea." Unfortunately, seamless inline editing (like WYSIWYG HTML mode in IE/Win) is apparently being held up by an internal flame war among the Mozilla developers. [Dive Into Mark]
The inline flame war is Bug 97284 and has been going on for over a year. To me it has always seemed obvious that they should take a two-pronged approach, creating a "proper" implementation that embeds Composer and providing a wrapper that is compatible with IE's implementation.
I've got one gripe with Composite, aside from it not being inline: it doesn't support pasting of HTML that originates from IE/Win. I think the problem is with Composer, not Composite itself. Composer seems to want the clipboard data as "text/html", while IE supplies "HTML Format". They ought to be compatible with each other, but there's some sort of encoding issue that I haven't been able to figure out...
