Opened 8 years ago

# newsflashmacro produces invalid xhtml-strict when used in the !NewsFlashStart/!NewsFlashEnd notion

Reported by: Owned by: jholg Ryan J Ollos normal NewsFlashMacro minor xhtml, xhtml-strict 0.11

### Description

When using NewsFlashMacro in the NewsFlashStart/NewsFlashEnd notion, I get invalid xhtml-1.0-strict on a previously clean trac page:

Validation Output: 7 Errors

1. Error Line 87, Column 22: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag.

<div class="newsflash">

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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

1. Error Line 88, Column 3: end tag for "div" omitted, but OMITTAG NO was specified.

</p>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

1. Info Line 87, Column 0: start tag was here.

<div class="newsflash">

1. Error Line 90, Column 5: end tag for "p" omitted, but OMITTAG NO was specified.

</div>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

1. Info Line 89, Column 0: start tag was here.

<p>

1. Error Line 91, Column 3: end tag for element "p" which is not open.

</p>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

1. Error Line 130, Column 9: end tag for element "div" which is not open.

</div>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

1. Error Line 88, Column 4: XML Parsing Error: Opening and ending tag mismatch: div line 87 and p.

</p>

1. Error Line 90, Column 6: XML Parsing Error: Opening and ending tag mismatch: p line 89 and div.

</div>

This does not happen if I use the

{{{
#!NewsFlash
}}}


syntax, which seems to be the recommended way.

Cheers, Holger

### comment:1 Changed 6 years ago by Ryan J Ollos

Owner: changed from Noah Kantrowitz to Ryan J Ollos

### Modify Ticket

Action
as new The owner will remain Ryan J Ollos.