I agree that folks have been talking about JS for a long time, and that it's frustrating, but what I'm suggesting is that we need to tackle a different problem first.
This isn't an academic question - without knowing how the DOM is going to work (or even if there is one), the JS conversation can't be anything but theoretical (or, at best, very incomplete in the concrete). I'm just trying to see if any work was already going on in this space, or if there was any interest in a team effort to attempt it. On 11/22/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Nov 22, 2006, at 2:51 PM, Christopher Hart wrote: > Would an "easier" (yet still monumental) starting point be to > tackle the DOM > implementation independent of a JS engine? All of this is pointless unless someone is willing to step up and JFDI. Otherwise, it's just rehashing the same theoreticals. People have been talking to me about adding JavaScript support for years, and nobody has ever done it. http://search.cpan.org/dist/WWW-Mechanize/lib/WWW/Mechanize/ FAQ.pod#JavaScript xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
