On Wed, 26 Nov 2008, [EMAIL PROTECTED] wrote: > On 11/26/08, Rainer Schöpf <[EMAIL PROTECTED]> wrote: > > On Tue, 25 Nov 2008 at 23:57 -0500, [EMAIL PROTECTED] wrote: > > > This counters your first post stating the TEXTAREA element is > > > collapsed. > > > > No, it doesn't. As I explained in my first post, textarea elements are > > collapsed when using the default sitemap. By changing type="xml" to > > type="html" > > in map:serialize, I get the code shown in my last message. > > > > So, my question is: what are the problems with this approach? You seem to > > say > > that it's not good enough, because of cocoon's limitations. > > Rainer > > I missed some information. > Which serializer had the problem? > Which serializer are you using now? Does the problem still appear? > > The HTMLSerializer is usually the final step. > The XHTMLSerializer requires browsers that understand XHTML. > The XMLSerializer is used mostly for internal pipelines, not for > sending webpages to a browser. > > HTTP's content-type header must match the data. Do not claim XHTML is > "text/html"; use "application/xhtml+xml". (My guess why not > "text/xhtml" is committees.)
I see now where our misunderstanding comes from. When I install lenya 2.0.2 from source, it references in its toplevel sitemap.xmap file only the classes XMLSerializer and the HTMLSerializer. There are two variants of the XMLSerializer: "xhtml" with mime-type text/html "xml" with mime-type text/xml In the default publication's sitemap.xmap the second one is used for internal pipelines, the first one for the final step. The HTMLSerializer is _not_ used. As a consequence, empty elements like textarea area collapsed, leading to disappearing text or out of order display. In my test publication, I use the HTMLSerializer for the final step, and the page looks as I expect it. (Actually it is a bit more work, since the sitemaps for several modules like tinymce need to be changed as well.) So, I wonder whether the default publication should be changed likewise. Thanks, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
