W3C home > Mailing lists > Public > public-html@w3.org > April 2010

Re: ISSUE-107 Change Proposal: Replace <object> fallback example

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 28 Apr 2010 15:22:32 -0700
Cc: public-html <public-html@w3.org>
Message-id: <B9ABD5A9-E7BD-4592-B2FC-BBC8F797E799@apple.com>
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>

On Apr 22, 2010, at 5:15 AM, Lachlan Hunt wrote:

> Hi,
>  This is an alternate change proposal for ISSUE-107.

Recorded here:
http://dev.w3.org/html5/status/issue-status.html#ISSUE-0107

Regards,
Maciej

>
> *Summary*
>
> The example provided for using the the param element to pass  
> parameters to a plugin within a page does not demonstrate best  
> practice.  This example should be replaced with a more appropriate  
> example.
>
>
> *Rationale*
>
> The current spec providedes an unrealistic example designed to  
> discourage the use of plugins due to their proprietary nature.   
> While encouraging the use of vendor-neutral technologies over  
> proprietary technologies is a noble goal, the example would better  
> serve web developers by demonstrating how plugins can be used  
> without being detrimental to those without the plugin installed.
>
>
> *Details*
>
> Replace the example provided in "The param Element" section  
> (currently section 4.8.5) with the following:
>
> ---
>
> <!DOCTYPE HTML>
> <html lang="en">
> <head>
>  <title>O3D Utah Teapot</title>
> </head>
> <body>
>  <p>
>   <object type="application/vnd.o3d.auto">
>    <param name="o3d_features" value="FloatingPointTextures">
>
>    <img src="o3d-teapot.png" alt="3D teapot illustration rendered  
> using O3D.">
>    <p>For an enhanced experience, we recommend that you install
>       the <a href="/get-plugin">O3D plugin</a>.
>   </object>
>   <script src="o3d-teapot.js"></script>
>  </p>
> </body>
> </html>
>
> ---
>
> Note: This example is based on this commonly used 3D teapot
> http://en.wikipedia.org/wiki/Utah_teapot
>
> As in the current example in the spec, the param element in the  
> example needs to be highlighted.
>
>
> *Impact*
>
> *Positive Effects*
>
> * Shows a more realistic example, illustrating the use of the param  
> element.
> * Encourages best practice by providing better quality fallback.
>
>
> *Negative Effects*
>
> None.
>
>
> *Conformance Classes Changes*
>
> None.  This is a change to a non-normative example only.
>
>
> *Describe any risks.*
>
> None.
>
>
> *References*
>
> None.
>
> -- 
> Lachlan Hunt - Opera Software
> http://lachy.id.au/
> http://www.opera.com/
>
Received on Wednesday, 28 April 2010 22:23:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:17 UTC