Bug 158325 - Validation errors mixing JSTL and HTML
Summary: Validation errors mixing JSTL and HTML
Status: CLOSED DUPLICATE of bug 152620
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-22 11:08 EDT by Bob Gallagher CLA
Modified: 2010-01-13 16:08 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Gallagher CLA 2006-09-22 11:08:58 EDT
I have the following jsp content:

<HTML>
<BODY>
<c:forEach var="item" items="${sitenav.items}" begin="0" step="1" varStatus="status">
	<c:choose>
		<c:when test="${status.first}">
<div class="topNavRight"><ul>
		</c:when>
		<c:when test="${!item.group}">
<li><c:out value='<A href="${item.href}" class="${sitenav.navclass}" style="${sitenav.navstyle}">${item.label}</A>' escapeXml='false'/></li>
			<c:if test="${status.last}">
</ul></div>
			</c:if>
		</c:when>
	</c:choose>
</c:forEach>
</BODY>
</HTML>

Errors are being reported on the line </ul></div>
    no start tag (<div>) and no start tag (<ul>)
Turning off HTML validation will stop the errors from being reported.
Comment 1 David Williams CLA 2006-09-23 00:05:02 EDT
See also bug 157673 to consider from a "tag dependent" point of view. 

We'll also should re-examine those parts of the DOM parser that decides 
when it should implicitly end an HTML element. 

Comment 2 Amy Wu CLA 2006-09-28 10:18:19 EDT
Is this a duplicate of bug 152620?
Comment 3 Bob Gallagher CLA 2006-09-28 12:50:30 EDT
Yes I would say that this defect is a duplicate of bug 152620 and the others (particularly 154858) that have been made a duplicate of it. But I think this will warrent more than a "note in the documentation" as pages built with JSTL are common.
Comment 4 Bob Gallagher CLA 2010-01-13 16:08:25 EST

*** This bug has been marked as a duplicate of bug 152620 ***