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]  $ object in javascript
Date: Tue, 27 Dec 2016 15:11:06 -0500	[thread overview]
Message-ID: <20161127151106.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1612271144060.15985@carhart.net>

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

Implementing the spec is valuable, or at the very least reading the spec,
so that the piece you decide to implement, you're implementing it right!
But I do believe, with the above caveat, that find&fix is the biggest bang for the buck, and we don't have a lot of resources here, so on we go.
(I sometimes wonder how many fulltime programmers maintain chrome or edge or whatever.)

I think we need to amass a list of sites that people want, that just don't work.
That's a market driven approach.
Kevin is already doing that; he has 2 or 3 that people have asked about,
that he is looking into.
My latest pet pieve is an entire domain, nasa.gov.
I'm a big space fan, and I love to read the articles,
but every page comes up blank, with or without js.
Didn't use to; the site use to be very accessible.
Not any more.
That's the problem with edbrowse, if you're not swimming forward you're falling behind.
I also can't listen to nasa tv with realplayer, though I could before.
That's another story.
Anyways, Kevin, you might add nasa.gov to the list of desirable and unworkable pages.

Karl Dahlke

  reply	other threads:[~2016-12-27 20:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 16:03 Karl Dahlke
2016-11-29 16:24 ` Chris Brannon
2016-11-30  0:47 ` Kevin Carhart
2016-11-30  7:30   ` Karl Dahlke
2016-11-30  7:43     ` Tyler Spivey
2016-11-30  7:54       ` Karl Dahlke
2016-12-01  0:04         ` Kevin Carhart
2016-12-01  1:17           ` Karl Dahlke
2016-12-25 13:06             ` Adam Thompson
2016-12-26 14:52               ` Karl Dahlke
2016-12-27  3:04                 ` Kevin Carhart
2016-12-27  3:49                   ` Karl Dahlke
2016-12-27  4:17                     ` Kevin Carhart
2016-12-27  4:38                       ` Karl Dahlke
2016-12-27 18:37                         ` Adam Thompson
2016-12-27  4:59                       ` Chris Brannon
2016-12-27  6:53                         ` Kevin Carhart
2016-12-27 15:21                           ` Chris Brannon
2016-12-27 20:13                             ` Kevin Carhart
2016-12-27 13:26                         ` Karl Dahlke
2016-12-27 15:47                           ` Chris Brannon
2016-12-27 18:48                             ` Adam Thompson
2016-12-27 20:23                               ` Chris Brannon
2016-12-28 11:42                                 ` [Edbrowse-dev] Edbrowse in NetBSD Adam Thompson
2016-12-28 11:50                                   ` Chris Brannon
2016-12-28 12:15                                     ` Adam Thompson
2016-12-27 19:11                   ` [Edbrowse-dev] $ object in javascript Adam Thompson
2016-12-27 19:47                     ` Kevin Carhart
2016-12-27 20:11                       ` Karl Dahlke [this message]
2016-12-27 20:45                         ` [Edbrowse-dev] nextSibling and previousSibling Kevin Carhart
2016-12-27 21:14                           ` Chris Brannon
2016-12-28 11:38                       ` [Edbrowse-dev] $ object in javascript Adam Thompson

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