syntax error ?

[bobpit]

1st issue:

In the sampleform.html there is the line:

<input type="hidden" name="env_report" value="REMOTE_HOST,REMOTE_ADDR,HTTP_USER_AGENT,AUTH_TYPE,REMOTE_USER">

Shouldn't this close with "/>" ??

So it should be:

<input type="hidden" name="env_report" value="REMOTE_HOST,REMOTE_ADDR,HTTP_USER_AGENT,AUTH_TYPE,REMOTE_USER"/>

I made this change and DreamweaverCS3 cleared many of the validity checks it reported to me.

+++++++++++++++++++++++++++


2nd issue:

DreamweaverCS3 reports the following error for the following line of code:
"The tag: "form" doesn't have an attribute: "name" in currently active versions.[XHTML 1.0 strict]"

<form method="post" action="http://soultherapynow.com/formmail.php" name="SampleForm" enctype="multipart/form-data" />

I suspect it is some XHTML version compatibility problem.

The form was working fine anyway. I just want to clear all the error messages.

[russellr]

Hi,

Thanks for the report.

I've now gone through all our sample forms and made them XHTML (transitional) compliant.

[bobpit]

I am visiting again this old issue.

I built the site in Dreamweaver and using the [XHTML 1.0 strict] format. But I see I have a lot of incompatibility problems when I add 2rd party products (like formmail).

Since you made this update, why didn't you make it [XHTML 1.0 strict] compliant?

[russellr]

Hi,

Good question, and, I suspect that the sample forms are probably XHTML 1.0 strict compliant.

I haven't checked though.

I have a philosophical problem with XHTML 1.0 strict.

The main problem is that they've removed the "target=" attribute from <form> and <a> tags.

This means it is no longer legal to open a link in another window.

I don't have a major issue with the concept of that for normal web pages (in fact, we've just gone through our whole website and removed this from almost all links).

But, when you have web applications like our Configuration Wizard (http://www.tectite.com/wizards/fmconf.php), you absolutely need to be able to make links open in a new window.

The usual answer is to use JavaScript. But, what if you want, as we do, to write a web application that does not require JavaScript?

I think the people who work on these standards have lost the plot a little on issues such as this.

So, we're anti-strict and pro-transitional for the time being.