[
http://www.stripesframework.org/jira/browse/STS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11956#action_11956
]
Nikolaos commented on STS-751:
------------------------------
> Wow. You guys must *really* hate HTML validator warnings. ;)
LOL. Actually if you do regularly validate and use HTML doc type this is more
annoying than it appears... It's 1 warning "per" tag that is not correct... .
So if you have a form with 5, 10 or whatever improperly closed elements on a
page you could easily get a dozen or more extraneous warnings you need to wade
through to with "each" of the following form:
# Warning Line 5, Column 51: NET-enabling start-tag requires SHORTTAG YES
<p>First name:<input type="text" name="firstname" /></p>
The sequence <FOO /> can be interpreted in at least two different ways,
depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/'
terminates the tag <FOO (with an implied '>'). However, since many browsers
don't interpret it this way, even in the presence of an HTML 4.01 Strict
DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve
its use solely for those written in XHTML.
Finding your legitimate warnings and errors in the enlarged list is the "real"
annoying part :-)
> On a serious note, I do have some major misgivings about implementing this as
> an attribute to a layout tag. Layouts are not required for use with other
> tags that happen to emit HTML so I don't think it's appropriate to require
> use of layout tags to enable or disable XHTML. We were thinking something
> more along the lines of a simple tag that could be inserted at the top of a
> page to set options ...
>
> <s:options xhtml="false" />
>
> or something like that.
Great point. Decoupling the mechanism from the Layout tag would allow more
flexibility e.g. for HTML fragments w/ or w/o Ajax, etc...
> Add support ala Struts to generate HTML or XHTML compliant close tags
> ---------------------------------------------------------------------
>
> Key: STS-751
> URL: http://www.stripesframework.org/jira/browse/STS-751
> Project: Stripes
> Issue Type: Improvement
> Components: Tag Library
> Affects Versions: Release 1.5
> Environment: No specific OS required; no specific Java version
> required; etc...
> Reporter: Nikolaos
> Priority: Minor
> Attachments: stripes-xhtml-patch.tar.gz, stripes-xhtml-patches.tar.gz
>
>
> HTML and XHTML documents have some key differences.
> For example - if we consider the <input> tag:
> - In HTML, the <input> tag has no end tag e.g. <input name="website.url"
> type="text" size="30">
> - In XHTML, the <input> tag must be properly closed, like this <input />
> e.g. <input name="website.url" type="text" size="30" />
> Stripes 1.5.x however does not have a mechanism to discern whether or not to
> properly close tags or not and as such takes the safer approach which is to
> explicitly close tags as it results in valid XHTML and is not an error for
> HTML but results in a warning when validating HTML documents. Although the
> latter is not a critical issue it does result in needless or unnecessary
> complaints when validating and as such is an annoyance albeit minor.
> Struts since 1.x has solved this issue quite easily by allowing the inclusion
> of the xhtml="true" attribute to mark that closure is required (false
> indicates no closure). In this manner authors of XHTML and HTML documents
> are equally satisfied in not having any errors or extraneous warnings.
> Timothy Stone had reported this issue and classified it as a bug here:
> http://www.stripesframework.org/jira/browse/STS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11931#action_11931
> The issue was rightly closed as "Not a bug" as most of the discussion was
> based on a non-w3c validator which yielded results that considered the
> validation unsuccessful which is not the case with the w3c validator (not to
> mention that it is irrelevant whether or not XHTML is considered dead or we
> should align to HTML 5 - etc...).
> As such this issue report is a re-statement of the above closed issue
> reported as an improvement and setting the stage for patch to be attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
