W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: handling fallback content for still images

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Fri, 6 Jul 2007 01:40:35 +1000
Message-ID: <5f37426b0707050840n4bf2c67h15255d9e318f9e6@mail.gmail.com>
To: "Robert Burns" <rob@robburns.com>
Cc: public-html@w3.org

lol, that's weird, but yep... it would work. Bit boring when you press
"Play" though.
I've added CSS image replacement techniques to the wiki,



On 7/6/07, Robert Burns <rob@robburns.com> wrote:
>
> On Jul 5, 2007, at 10:20 AM, Jon Barnett wrote:
>
> > I'm adding one more possible solution to the wiki: the CSS3
> > "content" property.
> >
> > While it is outside the scope of HTML, HTML 5 could recommend it
> > for an image with rich fallback content if it can be considered a
> > viable solution.
> >
> > Another "con" I failed to verbalize is that it ties the URL of the
> > image - which is often considered part of "content" - to CSS, which
> > is "presentation".  Using the "style" attribute to specify it helps
> > with this.
> >
> > Feel free to edit its pros and cons.
>
>
> I too have another suggestion (one that I think authors might use
> whether we want the to or not; especially if we don't provide a
> decent alternative). Authors can simply use the element <video
> src='mystillimage'>,fallback</video>. This will allow them to provide
> semantically rich or media rich fallback for their still images
> without having to resort to @longdesc. After all, what is a still
> image, but a video with only one frame. I'll add that to the wiki too
>
> Take care,
> Rob
>
Received on Thursday, 5 July 2007 15:40:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:46 UTC