On Nov 11, 7:12 am, "Edward K. Ream" <[email protected]> wrote:
> data.html is contains many "challenging" features. In this regard, it is a
> good test. But it is a bad *unit* test, because the challenges are hidden in
> a lot of cruft.
After a pleasant hour or so of "distilling", here is the essence of
the problems contained in data.html, imo::
QQQQQ
<html>
<head>
<!-- OOPS: link elements terminated two different ways -->
<link id="L1">
<link id="L2">
<link id="L3" />
<link id='L4' />
<title>TITLE</title>
</head>
<body>
<table id="T5">
<!-- OOPS: the div and p elements not properly nested.-->
<p>
<div>Paragraph</p>
<p>
Paragraph 2</p>
<p>
</div>
</p>
</table> <!-- T5 -->
<script language="JavaScript1.1"></script>
<script language="JavaScript1.1"></script>
<noscript><img id="IMG1"></noscript>
</body>
</html>
QQQQQ
Distilling this wasn't easy: it was very easy to delete too much,
thereby making the import work again. Having said that, I suspect
that some of the elements shown can be distilled away.
This improperly nested and terminated tags are going to be quite a
trick for skipToMatchingTag to handle so as not to disrupt the proper
nesting of the imported Leo nodes.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
