W3C home > Mailing lists > Public > public-html@w3.org > June 2009

[Bug 7010] New: Making <applet> non-conforming may hinder royalty-free <video> adoption

From: <bugzilla@wiggum.w3.org>
Date: Wed, 10 Jun 2009 08:09:49 +0000
To: public-html@w3.org
Message-ID: <bug-7010-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7010

           Summary: Making <applet> non-conforming may hinder royalty-free
                    <video> adoption
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


http://www.bluishcoder.co.nz/2009/06/video-for-everybody-html-5-video.html#9069120310304449626
cites <applet> being non-conforming as a reason not to use Cortado as a
fallback for <video>.

If one wants to serve royalty-free Ogg video using <video> to Firefox 3.5,
Chrome 3 and Safari 3.1 or later + XiphQT and still have a fallback for IE and
Opera, it seems that it would be useful to be able to use a single
no-JavaScript <applet> fallback for both IE and Opera without having a
validator whine about it.

If one only wants to have a Cortado fallback in IE assuming Opera ships <video>
soon enough, one could use <object>, but according to Sun's documentation[1],
that alternative required the classid attribute which is also non-conforming in
HTML5.

Please allow a conforming and easy-to-author way to fall back onto Cortado in
desktop browsers that don't support <video>. After all, <video> has *designed*
fallback mechanism. It's rather silly if using the mechanism is non-conforming.

[1]
http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/using_tags.html


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 10 June 2009 08:09:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:38 GMT