[Edward Kuns]

Is there a way to configure HTML validation so that it will not flag IE-only tags such as “onDragEnter” and “onBeforeUnload” and so on as warnings? Also, is there a way to configure HTML validation so in an EMBED tag, one’s parameters being passed to a Java applet are not all flagged as errors?

Also, the validation appears to not like JSP2 EL expressions in certain locations. For example, in the following code:

<c:set var=”checkedOrNot” value=”${not empty traceMap[jgroupsName] ? ‘checked’ : ”}”/>
<input type=”checkbox” name=”trace.${jgroupsName}” value=”trace” ${checkedOrNot}>

the HTML validator flags ${checkedOrNot} as an undefined attribute name.

Finally, how does one tell the validator that certain JSP files are fragments and are not expected to contain an entire HTML document?

[Riyad Kalla]

Is there a way to configure HTML validation so that it will not flag IE-only tags such as “onDragEnter” and “onBeforeUnload” and so on as warnings? Also, is there a way to configure HTML validation so in an EMBED tag, one’s parameters being passed to a Java applet are not all flagged as errors?

You can turn off HTML validation, but that is all.

Also, the validation appears to not like JSP2 EL expressions in certain locations. For example, in the following code:

<c:set var=”checkedOrNot” value=”${not empty traceMap[jgroupsName] ? ‘checked’ : ”}”/>
<input type=”checkbox” name=”trace.${jgroupsName}” value=”trace” ${checkedOrNot}>

Is this in a JSP or HTML file?

Finally, how does one tell the validator that certain JSP files are fragments and are not expected to contain an entire HTML document?

The spec suggests using the “.jspf” extension, we honor this and will treat the pages as fragments if you do so. There is a setting under “JSP Editor” in the MyEclipse preferences where you can specify other extensions to treat as fragments, but jspf is the preferred and default setting.

[Edward Kuns]

Is there a way to configure HTML validation so that it will not flag IE-only tags such as “onDragEnter” and “onBeforeUnload” and so on as warnings? Also, is there a way to configure HTML validation so in an EMBED tag, one’s parameters being passed to a Java applet are not all flagged as errors?

You can turn off HTML validation, but that is all.

Is it possible that this can be a future enhancement? How would one request this? (I am a very new subscriber.) I have already found the HTML validation to be very helpful, but I have a LOT of false complaints of things that are legal HTML. For example, the EMBED tag description says that certain media types will have proprietary tags. Thus, it is expected that the EMBED tag, in particular, may legally have unrecognized tags.

It would be wonderful to be able to specify on a tag-by-tag basis extra allowed attributes.

Also, the validation appears to not like JSP2 EL expressions in certain locations. For example, in the following code:

<c:set var=”checkedOrNot” value=”${not empty traceMap[jgroupsName] ? ‘checked’ : ”}”/>
<input type=”checkbox” name=”trace.${jgroupsName}” value=”trace” ${checkedOrNot}>

Is this in a JSP or HTML file?

JSP file. Everywhere that I have an EL expression inside an HTML tag, the HTML validation treats the EL tag as if it were a literal HTML tag, it seems. To be a little more explicit, if I have EL in the VALUE of an HTML tag attribute, all is OK. But if I use the EL to give the whole attribute and value, the HTML validation doesn’t appear to see the EL as variable text, but as a literal text.

The spec suggests using the “.jspf” extension, we honor this and will treat the pages as fragments if you do so.

I’ll try that. Thanks.

[Riyad Kalla]

Is it possible that this can be a future enhancement? How would one request this? (I am a very new subscriber.) I have already found the HTML validation to be very helpful, but I have a LOT of false complaints of things that are legal HTML. For example, the EMBED tag description says that certain media types will have proprietary tags. Thus, it is expected that the EMBED tag, in particular, may legally have unrecognized tags.

It would be wonderful to be able to specify on a tag-by-tag basis extra allowed attributes.

It is extremely pedantic, it is 4.01 strict so it does tend to complain about a few things that are common practice. I can’t speak to the tag-by-tag validation, this is the first time fine tuning the validation has been brought up in detail, I can’t say it would likely be soon but it is something we can take into consideration as we further expand our functionality.

JSP file. Everywhere that I have an EL expression inside an HTML tag, the HTML validation treats the EL tag as if it were a literal HTML tag, it seems. To be a little more explicit, if I have EL in the VALUE of an HTML tag attribute, all is OK. But if I use the EL to give the whole attribute and value, the HTML validation doesn’t appear to see the EL as variable text, but as a literal text.

In our 5.0 release and later our editors will get a nice kick with some big upgrades (hopefully some EL autocomplete, things of that nature). but those items are still a ways off. Hang in there with us, sorry for the trouble.

[Eric]

I also want better control of the validation, or at least to have the html validator use the doctype of the file.

[Author]

Posts