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

Re: [css3-images] Generalize the notion of 'invalid images' for image() fallback

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 27 Feb 2012 17:22:12 -0800
Message-ID: <CAAWBYDDxYpGKyj79RPUb=X17O8v7iNSpTpDCHNfk2+FTY=txSw@mail.gmail.com>
To: www-style list <www-style@w3.org>
On Wed, Feb 22, 2012 at 10:57 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> This is something I meant to file on myself a while ago, but forgot about. :/
>
> Before this morning, the image() function only skipped an image if it
> was a format that the UA couldn't decode or knew wasn't an image.
> While addressing some LC feedback, I broadened this to also skip an
> image if it's a URL that uses a fragment identifier syntax the UA
> doesn't understand.
>
> I'd like to slightly broaden this "invalid image" definition so that
> other features can hook into it.  Specifically, I'd like to allow
> element() to trigger fallback in image() if it hits one of the "error"
> cases that currently produce a transparent image.  If element() is
> used alone, it would still produce a transparent image as currently
> specified; it would just trigger fallback if used in image().
>
> With an explicit hook, other sources of <image> could potentially hook
> into this as well, though I'm not currently aware of anything else
> that would want to.
>
> Any objections?

I've heard no objections since Wednesday, so I've made this change.

~TJ
Received on Tuesday, 28 February 2012 01:22:59 GMT

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