- From: Joe D Williams <joedwil@earthlink.net>
- Date: Wed, 14 Apr 2010 09:00:24 -0700
- To: "Julian Reschke" <julian.reschke@gmx.de>, "Lachlan Hunt" <lachlan.hunt@lachy.id.au>
- Cc: <public-html@w3.org>
>> alternative content, or at least a link to some sort of substitute >> for >> the missing content. Including the advice to obtain the plugin in >> addition to that would be acceptable, but consider how useless such >> advice would be on its own, on most devices other than desktop >> computers, like mobile phones, set top boxes, TVs, etc. > > I agree that supplying links to alternate content that doesn't > require a plugin is good. But this is not an authoring guide (where > it makes sense to discuss these kinds of choices). > > That being said, would something like: > > <object type="application/vnd.o3d.auto"> > <param name="o3d_features" value="FloatingPointTextures"> > This page requires the use of the FOOBAR O3D plugin. Get it > from the <a href="...">FOOBAR O3D Download Page</a>. If this plugin > is not available for your browser, then please view <a > href="...">this static image</a>. > </object> > > address this? The normal fallback opertion would allow the author to specify the alternate content directly. So, THis might be a better example: <object type="application/vnd.o3d.auto"> <param name="o3d_features" value="FloatingPointTextures"> <img src='thisstaticimage.png' title='alternative to FOOBAR O3D' > This object uses the FOOBAR O3D plugin. Get it from the <a href="...">FOOBAR O3D Download Page</a> </object> Then if the plugin won't play, then the image is shown, and if the image is not available then the user gets the text with link. At least the example would show the multiple levels of fallback as an alternative to text only. Thanks and Best Regards, Joe > > Best regards, Julian > >
Received on Wednesday, 14 April 2010 16:10:19 UTC