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]  script tags in scripts
Date: Fri, 11 Sep 2015 06:17:13 -0400	[thread overview]
Message-ID: <20150811061713.eklhad@comcast.net> (raw)
In-Reply-To: <20150911073939.GA29720@toaster.adamthompson.me.uk>

> I'm not sure what we can do about this,
> but I'm inclined to think that whatever we do won't catch every case and that
> at some stage we have to accept that and move on.

That was true of my parser, true of tidy5, and true of any parser,
however, as you point out regularly, we should handle most websites
that other browsers handle.
And when we don't,
entire web pages shouldn't disappear beyond the point of error.
This bug is produced by fanfiction.net and fictionpress.com,
two high volume sites that work on every other browser.
And by the way, my thanks to those users who exercise and test our bleeding edge software;
you're as brave as a Windows 10 insider.
In any case, tidy5 needs to fix this,
or we need to find a way to preprocess around it,
the latter meaning I'd have to keep at least half of my parser,
which I really wanted to throw away entirely.   :(

Karl Dahlke

  reply	other threads:[~2015-09-11 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  0:17 Tyler Spivey
2015-09-11  1:10 ` Karl Dahlke
2015-09-11  5:28   ` Kevin Carhart
2015-09-11  7:39     ` Adam Thompson
2015-09-11 10:17       ` Karl Dahlke [this message]
2015-09-11 18:02         ` Adam Thompson
2015-09-11 18:55           ` Karl Dahlke
2015-09-11 16:37     ` 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=20150811061713.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).