edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  startpage
Date: Sun, 09 Feb 2014 18:23:26 -0500	[thread overview]
Message-ID: <20140109182326.eklhad@comcast.net> (raw)

> 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

             reply	other threads:[~2014-02-09 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-09 23:23 Karl Dahlke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-10 19:47 Karl Dahlke
2014-02-10 20:40 ` Chuck Hallenbeck
2014-02-10 23:52 ` Chris Brannon
2014-02-11  0:04   ` Chuck Hallenbeck
2014-02-11  0:29     ` Chris Brannon
2014-02-11  0:42       ` Chuck Hallenbeck
2014-02-09 19:04 Karl Dahlke
2014-02-09 22:12 ` Chris Brannon
2014-02-09 17:35 Karl Dahlke
2014-02-09 18:29 ` Chris Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140109182326.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).