- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 28 Dec 2011 18:12:51 -0500
- To: Lea Verou <leaverou@gmail.com>
- CC: Brian Kardell <bkardell@gmail.com>, www-style@w3.org
On 12/28/11 5:57 PM, Lea Verou wrote:
> Ideally, with separate pseudoclasses for HTTP errors and
> broken data.
I don't think that's necessarily terribly realistic. The two can't be
told apart reliably, for one thing: lots of servers return random HTML
with a 200 response on HTTP errors.
> If the same concept is applied to linked scripts and CSS
> files, it's even more important that they are separate, as most CSS
> files these days intentionally contain errors ("progressive
> enhancement") so it would be useless otherwise.
There is no such thing as a "parse error" from the point of view of CSS,
yeah. But there are non-HTTP-level fatal errors (e.g. inability to find
a decoder for the declared encoding, security policies blocking the
load, etc, etc).
-Boris
Received on Wednesday, 28 December 2011 23:13:29 UTC