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] version
Date: Sun, 18 Feb 2018 02:43:38 -0500	[thread overview]
Message-ID: <20180118024338.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1802171922310.17556@carhart.net>

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

I don't know, it may be more complicated than that.
I use google.com a zillion times a day, and it may throw all sorts of js errors under edbrowse, but I don't care because I run with

nojs google.com

In other words, I can perform the public search without js.
facebook.com is probably a nightmare, but I can use mobile.facebook.com just fine, even without js.
The question might be, which sites are high runner, and important to function properly, and also require js.
These are usually more than just browse.
Some like amazon that you order products, or paypal.com for financial, or any of the banking sites.
These are the steepest in terms of js complexity, and they may even have those nasty js tests to see if your browser is proper,
but they are among the most important in terms of accessibility.
My entire line-oriented approach / philosophy doesn't really work if I can't do my banking online.
I'd like to never ever ever have to run a screen program, that would be my dream come true.

Here's another approach: any website that puts up a message
"Your browser doesn't support javascript", and I've seen a lot of these,
we should track through and find out why it is saying that.
It's like an acid test but real world.
And it won't be easy because a lot of those tests are in try catch and don't cause any errors that we can see.
Can we somehow see errors that are hidden inside try catch?
Maybe, see duktape.errCreate and Duktape.errThrow in the programmers guide.
And there are the acid tests themselves, which we should go back to some day.
Just a lot to do, and I need about 8 fulltime engineers to help me, but I haven't won the lotto yet.

Karl Dahlke

  reply	other threads:[~2018-02-18  7:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 11:56 Karl Dahlke
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04   ` Karl Dahlke
2018-02-16 19:11     ` Adam Thompson
2018-02-18  2:19   ` Karl Dahlke
2018-02-18  2:42     ` Kevin Carhart
2018-02-18  3:03       ` Karl Dahlke
2018-02-18  3:39         ` Kevin Carhart
2018-02-18  7:43           ` Karl Dahlke [this message]
2018-02-18  8:17             ` Dominique Martinet
2018-02-18  8:47               ` Dominique Martinet
2018-02-18  8:30             ` Kevin Carhart
2018-02-18  7:45         ` Kevin Carhart
2018-02-18  8:55           ` Karl Dahlke
2018-02-18 11:29           ` Karl Dahlke
2018-02-18 14:08           ` Karl Dahlke
2018-02-19  1:07             ` [Edbrowse-dev] version / dyndns Kevin Carhart
2018-02-19  3:58               ` [Edbrowse-dev] update on dyndns Kevin Carhart
2018-03-24 16:07 [Edbrowse-dev] version Karl Dahlke
2018-03-25  8:11 ` Kevin Carhart
2018-06-11 15:45 [edbrowse-dev] version Karl Dahlke

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:

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

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


* 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).