W3C home > Mailing lists > Public > html-tidy@w3.org > October to December 2001

RE: enclose-block-text bug

From: Reitzel, Charlie <CReitzel@arrakisplanet.com>
Date: Fri, 12 Oct 2001 15:43:27 -0400
Message-ID: <B5C79DDBC655D311B6BD0008C7E64D76013C18B6@CAM-1CC-MAIL01>
To: "'Parsons, Rick'" <rick.parsons@eds.com>, tidy-develop@lists.sourceforge.net
Cc: "'html-tidy@w3.org'" <html-tidy@w3.org>
The tidy-dev list is probably the right place.  Sorry if we didn't respond.


On the enclose-block-text issue, I am not highly familiar with the issue it
addresses - mixed content model support in block elements - but taking a
look at the text itself, it may be technically correct.  Basically, it has
enclosed all the otherwise unenclosed text nodes within a <p> ... </p> pair.
Agree, however, that the inserted <p> tags should probably usurp all content
of its parent.

<li><em>vacant</em> <strong>Feock (inc. Devoran)</strong>

<p>, <strong>Forrabury</strong>, <strong>Fowey</strong></p>
</li>

Should be

<li><p><em>vacant</em> <strong>Feock (inc. Devoran)</strong>
, <strong>Forrabury</strong>, <strong>Fowey</strong></p>
</li>

I.e. the opening <p> tag needs to be moved back to the beginning of the <li>
content.  Coming in the middle, as it does now, it renders strangely on the
browser because beginning a new paragraph starts on a new line.  Even at the
beginning, putting in <p> elements messes with the vertical spacing on <li>
elements.  Opinions?

On the spacing issue, I think we are essentially at a feature freeze for
current work and are trying to clear up bugs and couple remaining issues.
Can you enter a feature request on Source Forge?

take it easy,
Charlie

-----Original Message-----
From: Parsons, Rick [mailto:rick.parsons@eds.com]
Sent: Friday, October 12, 2001 9:51 AM
To: 'html-tidy@w3.org'
Subject: enclose-block-text bug


[I originally sent this to the Tidy-dev list and got no response, so perhaps
that was the wrong place]

I tried out the enclose-block-text: yes option on the Sep 1 cut (Sep 15
build) of tidy [win32] with these strange results. It seems to be disturbed
by inline elements, only starting the <p> at the first raw text.

While I am here, I didn't see any response to Guillaume Rousse's query about
"spacing between siblings" [html-tidy@w3.org 9 Aug]. I would support the
call for an option to disable the generation of extra blank lines in the
output, or even suppress them entirely. There is "pretty print" and there is
bloated!


Cheers,

Rick Parsons

OPC: St. Ives and Towednack
R E N O W D E N One Name Study
West Penwith Resources http://west-penwith.cornwall.eu.org/
email: mailto:rick.parsons@bigfoot.com
website: http://www.parsons1998.freeserve.co.uk/
address: 18, Brighton Road, Redland, Bristol, BS6 6NT England
telephone: +(44) 117 974 1288
Received on Friday, 12 October 2001 15:42:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:46 GMT