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] either way
Date: Tue, 06 Feb 2018 20:41:35 -0500	[thread overview]
Message-ID: <20180106204135.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1802061431540.19453@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]

> wow, is it possible that things would
> actually work better if we removed attachEvent from startwindow entirely?

I put this back on the list because we should all think about it and discuss it.
I first thought about it 2 or 3 years ago:
we should emulate one browser, pick one, say Firefox, since we were using mozilla at the time,
and our objects and js etc should behave as much like firefox as possible,
and since every web site is tuned to support firefox, edbrowse will run.
I even thought about making firefox the default user agent, basically lie to the internet,
and you can switch over to edbrowse if you dare.
But I didn't go that way because I don't know enough about firefox, or any browser for that matter, to truly emulate it.
Instead we pretty much implemented whatever we thought we had to at the time, including imperfect implementations of parallel systems that do essentially the same thing.

Yes nasa runs exactly the same way if I globally substitute attachEvent with zattachEvent, thus taking it away.
It comes up empty however if I remove the addEventListener system.
I think the industry is gradually moving towards addEventListener, wherein attachEvent could be depricated.

It's not a crazy idea, it's a really good idea, pick a browser and aim to emulate that as closely as possible, I'm just not sure how to do that.
In the short run, should we just comment out the atachEvent system?
I don't know.
Or maybe turn it on or off with a variable, and by default that variable is off.
I guess I'd be ok with that.

We'll run into other situations I'm sure where we're trying to be too many things to too many people.

Karl Dahlke

       reply	other threads:[~2018-02-07  1:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180106130623.eklhad@comcast.net>
     [not found] ` <alpine.LRH.2.03.1802061431540.19453@carhart.net>
2018-02-07  1:41   ` Karl Dahlke [this message]
2018-02-07  5:00     ` Kevin Carhart

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=20180106204135.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).