- From: Joe D Williams <joedwil@earthlink.net>
- Date: Tue, 15 Dec 2009 11:46:24 -0800
- To: "Joe D Williams" <joedwil@earthlink.net>, "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>
- Cc: "Julian Reschke" <julian.reschke@gmx.de>, "Jonas Sicking" <jonas@sicking.cc>, "Boris Zbarsky" <bzbarsky@mit.edu>, <public-html@w3.org>
> Now that all browsers support a first cut at <object>, let's take
> the time to give it a reliable home in xhtml and html documents.
Also, hopefully soon we can replace this example using our <video>
element. When all browsers can support <video> anyone seriously
interested in presentung video including movies or other fixed frame
per second media would upgrade their user code so that this block of
elements becomes working fallback if the <video> element fails becaue
<video> can't play the offered mime(s).
Also, consistent and secure operation of <video> and <object> and may
promote lower level usage, such as the opportunty for <canvas> to
render a video, even a movie, on abitrary 2D and 3D surfaces.
On the other hand, it depends upon the author's intent. Maybe <embed>
is the best choice after all. The author would need to be sure that
there was some sort of UA extension that is registered to deliver the
resource. Any player that could learn how to register itself to handle
the mime could be used by <embed> or <object>, or maybe even under the
covers by <video> to play it. Thus, thanks to the Greatest plugin ever
created for the WWW and commercial applications, producing great
advances in interactive authoring and delivery, if the client is
almost any vintage html web browser, if Adobe is available, then the
structure:
<video>
<source ...>
<object ,,, >
<embed src="someurl' type="application/x-shockwave-flash">
</object>
</video>
should play anywhere, past and forever
> Now that all browsers support a first cut at <object>, let's take
> the time to give it a reliable home in xhtml and html documents.
I can't help but note that the same could be said about <embed>. It
could be said that all major browsers have a first cut at support for
<embed>. An amazing amount of work has gone into the detailed
specification of <embed> as an interactive element in the HTML 5
document. At first viewing I thought well mostly all this stuff
produces extensions/restrictions/specializations (except formatting of
the interfaces) to <embed> that could or maybe should naturally
apply/be available to <object>. Then <object> is adding some
standardizable <object> interface features for html and xhtml and even
xml interactives, so maybe not all the same.
Thank You and Best Regards,
Joe
Received on Tuesday, 15 December 2009 19:47:08 UTC