[VE][79] Error Message Feedback

Hi,

Your validator highlights a validation error thus:

> /Line 318 <http://validator.w3.org/check#line-318>, column 48/: end 
> tag for element "STRONG" which is not open
>
> |...oatId=["","<strong>Parameters</strong*>*<br 
> />{action=LoginUser}<br />{_u=10911|
>
> The Validator found an end tag for the above element, but that element 
> is not currently open. This is often caused by a leftover end tag from 
> an element that was removed during editing, or by an implicitly closed 
> element (if you have an error related to an element being used where 
> it is not allowed, this is almost certainly the case). In the latter 
> case this error will disappear as soon as you fix the original problem.
>
> If this error occured in a script section of your document, you should 
> probably read this FAQ entry 
> <http://validator.w3.org/docs/help.html#faq-javascript>.
>

When the code at line 318 is actually setting a JavaScript variable thus:

> 316: <script language="JavaScript1.2" type="text/javascript">
> 317: <!--
> 318:     paramFloatId=["","<strong>Parameters</strong><br 
> />{action=LoginUser}<br />{_u=1091158721708}<br 
> />{template=Index.vm}<br /><br /><strong>Cookies</strong><br 
> />{subjectheight=425}\n{jsessionid=FE9A32570AE9356DF7E9A47E1BB97DAF}\n"];
> 319: //-->
> 320: </script>

i.e. The closing tag that is being highlighted is within a JavaScript 
variable assignment.

I don't mind so much that the JavaScript variable assignment is being 
examined for valid mark-up, but if it is then it would be nice if the 
opening tag was also detected.  The more correct thing to do is to 
probably not validate JavaScript variable assignments (or better still 
validate them as stand alone fragments).

Thanks for providing such a great tool as well an an opportunity to 
provide feedback.

Scott

-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au

Received on Thursday, 29 July 2004 23:59:48 UTC