- From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Date: Wed, 14 Apr 2010 15:44:05 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: "public-html@w3.org" <public-html@w3.org>
On 2010-04-13 20:11, Julian Reschke wrote: > A more realistic example would use fallback text with instructions about > where to actually get the plugin. > > Such as: > > <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>. > </object> I don't agree with the content of this proposed change because it encourages the kind of useless fallback content that should be discouraged. The ideal fallback should instead provide some kind of 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. -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
Received on Wednesday, 14 April 2010 13:44:34 UTC