Re: Proposal: @parsing="loose | strict"

On 14 Jul 2009, at 08:16, Doug Schepers wrote:

> When the parsing is loose, the error-correction algorithms defined  
> in HTML5 must be applied; when the parsing is strict, there must be  
> no error-correction (as is commonly the case for XHTML in most  
> browsers).
>
> This way, authors could optionally enforce strictness when they want  
> or need to, and then change/remove the value when they are ready for  
> publication, or when the needs change.  It is possible that there  
> would be instances where strict parsing makes it out of development  
> and into production code, but this would have relatively few  
> negative consequences (the kind of author who uses this would  
> probably product strict code anyway, and would know it if they  
> didn't), and would be easily corrected.  And, quite frankly, some  
> people simply prefer stricter parsing for aesthetic or whatever, and  
> this would provide them with that option while not imposing it on  
> others.

If you want only your browser to complain about errors, then you don't  
need everyone else's browser to support this feature.

Just use Firefox extension like this one:

https://addons.mozilla.org/en-US/firefox/addon/249

It shows you page errors in status bar. You could probably extend it  
to show screen of death if you want to.

It also automatically eliminates risk of sending strict page to users  
when that was not intended.

-- 
regards, Kornel

Received on Tuesday, 14 July 2009 09:43:48 UTC