> It isn't the behavior I see in Chromium, where a form element with > id=submit does not mask document.form.submit, but a form element with > id=foo is available as document.form.foo.
Then that is the behavior I should probably replicate, i.e. create the named link unless it is submit, reset, or action. I'm pretty sure I wrote that code seven years ago for a reason. So I'll make that change, with comments, and push. Here is how I think it all evolves. Some website that is really popular, like facebook, for example, has some bogus html or bogus javascript. Firefox, for example, doesn't want to be the new browwser on the block that can't run facebook. So they deliberately program around the bogus js or html code in facebook. And that gives facebook no insentive to clean up their code. It just goes on, across many websites that are too big to fail. Over two decades, all these little exceptions are programmed into all the browsers out there, and they aren't documented anywhere in any reliable way, so if we're serious about edbrowse we have to rediscover all these exceptions and program them into our DOM. As Charlie Brown says, oh good grief. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
