Glenn wrote:
> It's not the JS itself that causes the problem.
>It *is* the occurence of "<" symbols within the JS.
>Arachne interprets the "<" as the beginning of the next html tag.
>Since it is *not*.... the rest of the page doesn't get displayed.
>
>Attached is a prime example.
(snip)
Actually the main problem with that file is that "<!--" isn't closed (no
"-->"). Arachne can't handle this (it's not correct HTML - where does the
comment end?).
A certain source code came into my possesion on monday afternoon (read: I
stole it).
Changes so far:
1. JavaScript is ignored (everything between <SCRIPT> and </SCRIPT>)
ex. http://www.hninc.com/ now works, unfinished comment tags such as the
one from Glenns example will not. (So no need for an external utility to
ignore JS).
2. All spaces at the start of tags are ignored (there was some server that
sent < IMG ...> IIRC).
3. The JavaScript OnClick event is partialy implemented (only for <A>)
<A HREF="#" OnClick=window.open('someURL'...)>Idiotic link made by
Microsoft program</A>
will now work.
4. Probably slightly more stable (JavaScript/comment related).
Michael (and noone else) will get the source when I'm a little more
finished (ie. as soon as I've figured out more things to change and
implemented them <g>).
And with that I hope we won't see any more complaints about JavaScript in a
while, nor the police knocking on my door ;-)
A problem might exist if </SCRIPT> is found inside the <SCRIPT></SCRIPT>
area (the same probably goes for comments) but neither of these are common.
Another problem are the site designers that think this is valid (works in
Netscape 4 and up IIRC):
<SCRIPT>
...
<A HREF="somefile.htm">Click me!</A>
...
</SCRIPT>
I don't think we can easily solve that one (except when/if complete
JavaScript is added).
BTW: I said that it should be easy to port Arachne to 32-bit, it's not that
easy (I wonder if I actually have the latest source - it's from the 9th of
June IIRC) but I'm down to adding the 32-bit Watcom library now. However I
wonder if there's much point - SVGAlib 1.27 doesn't have VESA support :(
