Return-Path: Delivered-To: apmail-incubator-jspwiki-dev-archive@locus.apache.org Received: (qmail 17031 invoked from network); 12 Jan 2008 21:32:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jan 2008 21:32:00 -0000 Received: (qmail 3474 invoked by uid 500); 12 Jan 2008 21:31:50 -0000 Delivered-To: apmail-incubator-jspwiki-dev-archive@incubator.apache.org Received: (qmail 3464 invoked by uid 500); 12 Jan 2008 21:31:50 -0000 Mailing-List: contact jspwiki-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jspwiki-dev@incubator.apache.org Delivered-To: mailing list jspwiki-dev@incubator.apache.org Received: (qmail 3455 invoked by uid 99); 12 Jan 2008 21:31:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2008 13:31:50 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Janne.Jalkanen@ecyrd.com designates 193.64.5.122 as permitted sender) Received: from [193.64.5.122] (HELO mail.ecyrd.com) (193.64.5.122) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2008 21:31:24 +0000 Received: from [192.168.0.12] (cs181005170.pp.htv.fi [82.181.5.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.ecyrd.com (Postfix) with ESMTP id 5D5A44821F for ; Sat, 12 Jan 2008 23:31:29 +0200 (EET) Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <15cc92000801121323s44ed88bsf82376b791a1a847@mail.gmail.com> References: <15cc92000801120725s705fb562pa1dd06c4c6612f40@mail.gmail.com> <5004B08D-6BAB-4A14-A8C9-326FCC2A62D3@ecyrd.com> <15cc92000801121323s44ed88bsf82376b791a1a847@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Janne Jalkanen Subject: Re: FF issues on xhtml/css Date: Sat, 12 Jan 2008 23:31:20 +0200 To: jspwiki-dev@incubator.apache.org X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org 'Cos it's sometimes really hard to figure out where the

tags may or may not go. JSPWikiMarkupParser.paragraphify() tries real hard, but it does sometimes get it wrong. In fact, I would very much like to get rid of

tags altogether, and move to pure

s with a paragraph class. You can see that many blogging software (e.g. blogger) already does this - they put in two
-tags for paragraph breaks, and put a div around everything else. It's really easy to get invalid HTML with plugins. If a plugin contains a block element (e.g. div or hr) you must close the

before calling a plugin - but there's no way to know. You can't close paragraphs just randomly... So you can't rely on the

tag being there. (Yeah, we could pipe everything through jtidy. But that would slow things down quite a bit.) /Janne On 12 Jan 2008, at 23:23, Dirk Frederickx wrote: > Janne, > > That's exactly what I'm doing ;-) > Just ran into this strange bug while testing. > > Why is jspwiki not --always-- rending text inside html tags. > > Eg >

Title

text text text > > or > >

Title

text text text

> > > Any particular reason for this ? > > > dirk > > On Jan 12, 2008 6:43 PM, Janne Jalkanen > wrote: >> >> How about defining it differently on the print stylesheet? We do >> have jspwiki_print.css for exactly this purpose. >> >> /Janne >> >> >> On 12 Jan 2008, at 17:25, Dirk Frederickx wrote: >> >>> I was looking into JSPWiki printing issues on FF and IE, running >>> into >>> following issue. >>> ( https://issues.apache.org/jira/browse/JSPWIKI-128 ) >>> >>> Here is the html : >>> {{{ >>> >>>

some header

>>> First part of the text has no tags around it ... >>>
>>> Here is a commentbox >>>
>>> More text is comming here after. >>> >>> }}} >>> >>> Here is the css for commentbox >>> {{{ >>> .commentbox { float : left; } >>> >>> >>> }}} >>> >>> This renders perfecty on various browsers: Safari, Opera, Mozilla. >>> However, Firefox (also Camino) freak out: printing yields an blank >>> page ! >>> Removing the float style resolves the problem. >>> >>> Apparently, having float elements subsequent to html #text elements >>> seems to give problems. >>> >>> One rough measure is just remove all foats from printed pages. >>> >>> >>> Any other suggestions ? >>> >>> >>> dirk >> >>