Try wrapping the <form> tag in a <p>?

I have to admit that when I did this I did manage to get it to validate if I recall. If you can confirm that the above fixes the validation error, I shall update this post.

document type does not allow element X here; missing one of Y start-tag ✉
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 “<a>”, “”, or “”).

Line 403, column 368: document type does not allow element “form” here; missing one of “object”, “applet”, “map”, “iframe”, “ins”, “del” start-tag
…’feedburner-sub-window’, ‘scrollbars=yes,width=550,height=520′); return false”>

I’m setting up a new blog with Squarespace and trying to stick to XHTML 1.0 Strict.

I had some problems with your suggested changes at first, until I realised that FeedBurner have changed their URL for the email form since you posted this.

There are a few changes to the URL as follows:

Old: http://www.feedburner.com/fb/a/emailverifySubmit?feedId=xxxxx

New: http://feedburner.google.com/fb/a/mailverify?uri=MyFeedName

This is the validated XHTML 1.0 Strict code I implemented today on our blog and it’s working fine:

(You’ll need to replace all instances of ‘MyFeedName’ — http://feeds.feedburner.com/MyFeedName)

Subscribe to Email:

Cheers

James

I was building a new design for the site essentially from the ground up, so I picked the most recent iteration of XHTML to build it to.

It doesn’t make much difference, but I had been using XHTML 1.0 Transitional which allows certain tags which are somewhat archaic and take away from that warm, fuzzy feeling that you have a nice clean, modern, (erm… mostly?) compliant design.

I’d like to know the reason why you chose the doctype XHTML 1.1?

Apparently not! Because on my blog I moved that code outside of onsubmit and into an include file (the same code, just put elsewhere), W3C didn’t pick it up on my blog.

Have updated my post. Thanks again for the correction!

In your code there’s a straight & in the following line:
onsubmit=”window.open(‘http://www.feedburner.com/fb/a/emailverifySubmit?feedId=xxxxx&email=’

…juste before “email=”.

I wouldn’t have paied attention to this until the W3 validator hit my fingers! lol

This way you have the valid code for 1.0, too.

Take care!*

Where do I need to replace it? I can’t spot anywhere (other than in JavaScript, where I think it’s OK to do so) where I’ve used a straight &.