> 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 _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
