W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: An error pseudoselector for media

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 3 Feb 2012 06:24:25 -0800
Message-ID: <CAAWBYDBSF4nz7qtUpxi9Xn4V1hUWQuerC7RHZwB=d5eMQrK7JA@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: "www-style@w3.org" <www-style@w3.org>
On Thu, Feb 2, 2012 at 10:57 PM, Charles Pritchard <chuck@jumis.com> wrote:
> It occurred to me this evening, as I was chatting on webapps about
> createObjectURL, that an error pseudoselector for image elements would be
> darn handy.
>
> I had to use JavaScript for my project recently, because my primary image is
> a PNG but I've embedded an SVG resource as a fallback.
> Well, my primary image is an SVG at a separate url, and my fallback is an
> embedded SVG... but the point remains.
>
> It'd be swell to have something like this
>
> #myImage::error {
>  content: url(#fallback);
> }
>
> <img src="howdy.png" />
> <svg id="fallback" />
>
> I know that there are some vendor specific selectors that touch the
> periphery of this case.
> They're mostly about handling the image-broken visualization.
>
> onerror does not succumb to issues of CORS, so it seems quite safe to use it
> as a semantic with CSS.
> Further, it's possible that an error will occur at any time, such as a low
> memory condition.
>
> That's something that JS is not so awesome at handling.

Yes, Matt Wilcox started a thread on this subject a few weeks ago.  I
recommend reading that and continuing the conversation there.

~TJ
Received on Friday, 3 February 2012 14:25:16 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:50 GMT