In article <2c0f16264d.jess(a)itworkshop.invalid>,
Jess Hampshire <jess(a)itworkshop.uklinux.net> wrote:
On usenet JMB wrote:
> Note also that there's very little focus on gracefully
> invalid HTML in NetSurf at present - there's enough work
> to do to get it to render valid sites correctly.
If practical (ie depending on what approach you take) when this is
addressed, could I request that the graceful handling be able to be
switched on and off?
The reasons being:
1. If I'm designing a site (and I now use NS as the primary
view it) and I make a stupid mistake, it is nice if the browser doesn't
hide it for me.
2. Would it slow down the rendering of good sites?
I would like to go a little further and enquire whether the apparent
use of an xml parser could not make available parsing errors (if any) as
either a simple list called up from a menu or as an optional use of
Incidentally, one of the reasons I use other browsers for a
disappointingly large proportion of the time is that, despite the fact that
Netsurf obviously understands processing instruction syntax, it quietly
ignores those for the 'xml-stylesheet' engine - when, particularly if the
type is text/css, it could use them. I keep coming across more and more
documents using these rather than html 'link' elements - probably generated
server-side from some original xml document of some kind.
[PGP key available if desired]