From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 535E47890C for ; Fri, 11 Sep 2015 03:14:34 -0700 (PDT) Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-02v.sys.comcast.net with comcast id FmGu1r0032PT3Qt01mHDjb; Fri, 11 Sep 2015 10:17:13 +0000 Received: from eklhad ([IPv6:2601:405:4002:b0a:21e:4fff:fec2:a0f1]) by resomta-ch2-14v.sys.comcast.net with comcast id FmHD1r00A0GArqr01mHDfu; Fri, 11 Sep 2015 10:17:13 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <55F21D99.7070701@pcdesk.net> <20150911073939.GA29720@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.4.2+ Date: Fri, 11 Sep 2015 06:17:13 -0400 Message-ID: <20150811061713.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1441966633; bh=GTnrrTRFFphDbyYZrXqKIrHP9xLgLlim6P85oP+/t5o=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=boZOq5H0F0hGIRz9nIZU4TSdWDcn3AngDA7SzQEd6zZA3F+zm7z1p2NhSuGgFZVvc TH9cbaJpLnCZASNVOQTvxvTGJmB5/3gm60/6G/df7qoizTwAaHB66MsTL9DAFXk1sX OblEZMvVBtM7hxxFb2aSNcWBZhed7uCk1NuPyHGZuhMAdZiU6QZkRnQOK3iSEwV0L2 NMjLMwD9Xv7qY/V+bCs50j7glzgttsFBbjkirlr0EARm3rQoYw0ijQIiLdKd6yml+g zoLPi3owth0dMoZtScX+CBZARhp59HiPjk6jykk1jURSM4mBvxdJgVI1tNA8+Iqi/O NLMyeSu4X6EPw== Subject: [Edbrowse-dev] script tags in scripts X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2015 10:14:34 -0000 > 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