The issue here is "what is incorrect code?" -- a web coder can serve up
completely valid code, according to the w3c alidator, that is really
awful (this, also, is purely subjective). For actual scripting
languages the same is true - a coder can serve up code from procedural
hell but it runs perf
On 9/8/05, Chris Taylor <[EMAIL PROTECTED]> wrote:
> . they should refuse to parse incorrect code.
Hi
The issue here is "what is incorrect code?" -- a web coder can serve up
completely valid code, according to the w3c alidator, that is really
awful (this, also, is purely subjective). For actual
On 9 Sep 2005, at 9:13 am, Andrew Krespanis wrote:
I already see the HTML errors for every page I view [1].
The real nightmare is having the javascript console always open... so
many javascript errors all over the web :( (esp. on google sites!!)
And when you browse with the beta versions of F
On 9/9/05, Paul Bennett <[EMAIL PROTECTED]> wrote:
> although I foresee browsing with that extension may be a version of hell for
> many of us - can you imagine seeing the html errors for *every* page you
> viewed?
I already see the HTML errors for every page I view [1].
The real nightmare i
>Screenshots of a browser displaying (X)HTML errors in the same manner that a
>compiler
>does may get the message across that valid markup is important to those that
>make the
>decisions about such things. I'd certainly find it useful.
although I foresee browsing with that extension may be a
Well Fx already do this to some extent. If you go strict strict, yes
that´s two 'strict' ;-)
Serving not well-formed xhtml as application/xml+xhtml to Fx will get
you attention.
Regards,
Anders Ringqvist
Chris Taylor wrote:
Exactly. I was actually thinking the other day, browsers
should be
2005/9/8, Chris Taylor <[EMAIL PROTECTED]>:
> > Exactly. I was actually thinking the other day, browsers
> > should be more like compilers... they should refuse to parse
> > incorrect code. Then the enforcement would be on the output
> > end, too.
>
> Perhaps some clever person could write a Firef
> Exactly. I was actually thinking the other day, browsers
> should be more like compilers... they should refuse to parse
> incorrect code. Then the enforcement would be on the output
> end, too.
Perhaps some clever person could write a Firefox extension that does
this - if Chris Pederick is on
