Hi LD, LB>On Tue, 02 May 2000 21:31:18 -000, Mike Millen wrote: LB>MM> If Arachne can't interpret JS then at the very least it should IGNORE LB>MM> the JS sequences and correctly display the rest... which the latest LB>MM> version still cannot do. LB>Have to disagree with you here ... LB>Arachne currently ignores some javascript and deals with some of the LB>other jsnit that's out there. If it didn't I couldn't use half the LB>places on WWW that I do. You're absolutely right... it ignores *some* and deals with *some* but there are sites I've been to where js throws Arachne completely. I'm getting quite good at hitting F4, deleting a chunk of js, then hitting F2 before Arachne will display a page. This is the latest version. Not good enough yet! LB>MM> (Though to be fair... it's not reasonable to say LB>MM> that JS shouldn't be used just because Arachne can't handle it, LB>MM> when the mainstream windoze browsers use it correctly). LB>Second, it is hardly fair to compare Arachne to "mainstream browsers" LB>when it is often NOT the browsers that handle problems but instead the LB>bloatware of WinXxxx they have to design around/under/over/through. I didn't mean to compare Arachne to other browsers, merely say that I consider Arachne's problems due to js are down to Arachne itself, not the js. The js works ok and has every right to be there. Windoze and Linux users don't have a problem with it. It would be nice if (when?) Arachne does support js, but until then I'm quite happy to continue using it in preference to the windoze products, but while Arachne is broken when it comes to ignoring js then I believe it's a legitimate problem that is seriously compromising Arachne's capability as a viable web browser and Michael should treat it with some priority. Mike
