You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Tobin Juday (JIRA)" <ji...@apache.org> on 2007/02/09 18:50:16 UTC
[jira] Commented: (WW-1649) css_xhtml template produces invalid
xhtml
[ https://issues.apache.org/struts/browse/WW-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40063 ]
Tobin Juday commented on WW-1649:
---------------------------------
(1) is the only thing keeping my page from validating as valid XHTML. Please fix this. (And yes, I know I can just edit the template, I probably will do that, but it should be changed in the source as well.)
Thanks.
> css_xhtml template produces invalid xhtml
> -----------------------------------------
>
> Key: WW-1649
> URL: https://issues.apache.org/struts/browse/WW-1649
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.1
> Reporter: Gina Accawi
> Priority: Minor
> Fix For: 2.1.x
>
>
> XHTML produced using css_xhtml template is not valid XHTML. I have found two basic issues, and one suggested modification:
> 1. Form method should be "post" not "POST".
> 2. The attribute "name" is deprecated in favor of using "id". This issue seems to be more difficult to deal with given that there seem to be many places depending on name. The following elements should NOT use name attribute: a, applet, form, frame, iframe, img, and map. However, it should also be noted that many Javascripts, including some Ajax toolkits, rely heavily on the DOM method getElementById rather than getting them by name, making it more important to encourage the use of id over name.
> 3. This one is more the for the sake of using xml/object binding tools, wsdl generators and such: When creating empty tags, the /> should have a space between it and the content like so:
> Less good <br/>
> More good <br />
> I have not looked much deeper than a simple form with two selects, so I cannot say if I may be missing others. I use the W3C XHTML validator often in testing, which makes it fairly easy to detect problems with xhtml validity.
> thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.