Forums

I've been trying to track down this bug for a while and finally seem to have narrowed it down to forms loaded with the content plugin (V3.1 RC5.2), e.g.

{chronocontact}myformname{/chronocontact}

It only fails in IE9 standards mode, it's fine in IE 8 and IE 7, and it's fine if you turn on Compatibility View in IE9 -- though the bug doesn't TRIGGER compatibility view. If something else on the page triggers the compatibility view option, then you can turn it on and the form will render properly.

I'm attaching a screenshot of the IE9 DOM tree showing what's going on. It looks like the <form> tag is closing immediately after it opens. Interestingly, the form still works, but CSS or jQuery selectors such as "form input.name { foo: bar; }" are not applied, because the input elements are no longer children of the <form> element.

Any ideas what's going on? I'm running Joomla! 1.5.23 and ChronoForms V3.2.0. Thanks!

EDIT: W3C validator isn't happy with it either, produces this error:

Line 145, Column 286: document type does not allow element "form" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
…ocontact&task=send&chronoformname=product_info_request&Itemid=64" >
✉
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>").

Maybe it's related to the WYSIWYG editor I'm using? JCE 1.5.7.13

EDIT: Solved! The WYSIWYG was wrapping the plugin line in <p> tags, and I just changed that line to a <div> instead. Simple enough, now if I could only figure out how to get DirectPHP to process <div> lines...😀