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

(unknown charset) Re: Problem

From: (unknown charset) Dave Raggett <dsr@w3.org>
Date: Mon, 4 Oct 1999 11:25:37 +0100 (GMT Daylight Time)
To: (unknown charset) Darren Forcier <dforcier@allaire.com>
cc: (unknown charset) "'html-tidy@w3.org'" <html-tidy@w3.org>
Message-ID: <Pine.WNT.4.10.9910041121380.816-100000@OEMCOMPUTER>
On Mon, 27 Sep 1999, Darren Forcier wrote:

> The fixes for the custom tag support are working great. I can
> now set up new-blocklevel-tags and new-inline-tags for tidy
> configurations.
> If I have a custom processing tag like ColdFusion's <CFIF
> (expression) > tag and run it through Tidy with a custom tag
> configuration for it, the following happens:
> (old version)
> <CFIF True IS True>
>    This should always be output 
> <CFELSE>This will never output 
> </CFIF>
> (html-tidied version)
> <CFIF True="" IS="" True=""> This should always be output <CFELSE> </CFELSE>
> </CFIF>
> Two problems are occurring here. The CFIF tag expression "True
> is True" is being parsed and each item is being treated like it
> was a separate attribute. The second thing that is happening is
> the insertion of the extra </CFELSE>. The second problem is not
> really an issue, but if there was some way to turn off automatic
> attribute generation that would be a good thing.

Thanks for the report. You should be able to suppress the </CFELSE>
by declaring the tag as empty. I will look into a fix for the
attribute problem. Basically Tidy needs to treat the attributes
assuming they are minimized. 


-- Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
phone: +44 122 578 2984 (or 2521) +44 385 320 444 (gsm mobile)
World Wide Web Consortium (on assignment from HP Labs)
Received on Monday, 4 October 1999 06:26:41 UTC

This archive was generated by hypermail 2.3.1 : Friday, 13 July 2018 08:58:57 UTC