- From: David Woolley <forums@david-woolley.me.uk>
- Date: Thu, 28 Jun 2007 08:14:54 +0100
- To: www-style@w3.org
Mikko Rantalainen wrote: > Simon Pieters wrote: >> I don't understand why a parse error produces any more sign of why the >> error occured than replacing with U+FFFD. > > I don't understand it either. I cannot see a reason why user agent > couldn't log (and possibly display) a warning when it sees a U+FFFD. The I'm not convinced that the I18N people have understood that CSS is not like normal programming languages in that what would normally be considered parse errors are treated as actually being new features that the user agent doesn't yet know about, and which should be ignored (in the same way as recognized, but unsupported features). -- David Woolley Emails are not formal business letters, whatever businesses may want. RFC1855 says there should be an address here, but, in a world of spam, that is no longer good advice, as archive address hiding may not work.
Received on Thursday, 28 June 2007 07:14:39 UTC