> Sorry, browsers have to deal with the infinite number of legacy 
> documents that already make an infinite number of mistakes. 
> Significantly changing that behaviour is just not possible.

The IE team is correcting this kind of mistakes: 
http://blogs.msdn.com/ie/archive/2005/08/29/457667.aspx.

It is possible that <link> and <meta> in places other than <head> may not get 
parsed in the future.

> Here's one example.

> http://au.lge.com/

Horrible! <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 
inside a table. But... meta name="description" and meta name="keywords" are in 
a correct location.

Franklin Tse

-----Original Message-----
From: Lachlan Hunt [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 26, 2006 00:38
To: Tse Shing Chi (Franklin/Whale)
Cc: 'atom-syntax'
Subject: Re: PaceResurrectAutodiscovery

Tse Shing Chi (Franklin/Whale) wrote:
> No. Authors take the responsibility to correct the mistakes. Browsers 
> should not help them to do so.

Sorry, browsers have to deal with the infinite number of legacy 
documents that already make an infinite number of mistakes. 
Significantly changing that behaviour is just not possible.

However, this is getting way off topic for this list.  If you have an 
issue with the way HTML5 error handling is being defined, I suggest you 
raise the issue on the WHATWG mailing list.

> I cannot imagine if <meta> and <title> are being used anywhere in a
> HTML document.

Here's one example.

http://au.lge.com/

Note the meta element that occurs within a <table>, of all places!

-- 
Lachlan Hunt
http://lachy.id.au/


Reply via email to