Re: ISSUE-107 Change Proposal

On Wed, 14 Apr 2010, Lachlan Hunt wrote:
> 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.

Exactly. The text proposed above is exactly the same as the text in the 
spec now, except it's less honest about it.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'