In article <[EMAIL PROTECTED]>, "Gervase Markham"
<[EMAIL PROTECTED]> wrote:
>> I think that if the page is broken then it's the fault of the webmaster
>> who created the page and Mozilla should tell the user that there is an
>> error in page and tell more about the error and to contact webmaster of
>> the badly coded page.
>
> This becomes complicated (for the case in question) when you start
> adding pluggable new URI schemes to Mozilla. The "sanity-checking" code
> would have to be updated for each scheme.
I don't see why that is a problem. "Basic" sanity checking for
conformance to the generic URI syntax (RFC 2396) can happen in a
centralized location, but anything beyond that is--and *should*
be--scheme-specific.
Braden
