After enabling the global output filter of htmltidy module http://drupal.org/project/htmltidy the controls on the top of the img_assist page suddenly didn't fit into the top frameset.

It would be nice if the html/css validated correctly.

This is with htmltidy.module revision 1.56.2.5

Comments

darren oh’s picture

Status: Active » Closed (fixed)

Ambiguous issue. (What is the img_assist page?)

greggles’s picture

Status: Closed (fixed) » Active

Sorry I was ambiguous. I meant the page that pops up when you click img_assist underneath a text box.

Specifically the page is ?q=img_assist/header/browse which is inside of a frameset, but that's the specific section that was getting reformatted by htmltidy.

Specifically the errors from the w3c validator are:

Below are the results of checking this document for XML well-formedness and validity.

1. Error Line 33 column 72: ID "img_assist_header" already defined.

...img_assist/header/browse" method="post" id="img_assist_header">

An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).


2. Info Line 30 column 10: ID "img_assist_header" first defined here.

3. Error Line 35 column 96: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.

...an id="browse">

The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "

" or "

") inside an inline element (such as "", "", or "").


4. Error Line 48 column 36: document type does not allow element "div" here.


Page execution time was 40 ms.

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).


5. Error Line 48 column 103: document type does not allow element "div" here.

...s.

Memory usage:

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Thanks.

sun’s picture

Status: Active » Fixed

This should have been fixed in the latest development snapshots. If not, please provide a patch.

Anonymous’s picture

Status: Fixed » Closed (fixed)