SWFObject 2.2 working well in XHTML 1.1 and XML+XHTML mime type

[Ken Berry Media]

Although my webpage utilizing SWFObject 2.2 is served over the
Internet as HTML, this SWFObject version does appear entirely
compatible with XHTML and the above mentioned MIME type in all current
browsers (tested: IE7+8, Mozilla, Safari, Chrome.)

SWFObject 2.2 does not officially support XHTML or the application/xml
+xhtml MIME type; regardless, the SWFObject 2.2 static publishing
method in this valid XHTML 1.1 document produces no Javascript or
Browser related errors:

reference: http://www.kenberrymedia.com/

[Aran Rhee]

XHTML is officially supported (as noted in our docs, all examples are XHTML 1.0 strict doctype).

We don't however officially support the XHTML + XML mime type for the reasons stated on the documentation page. If your page is working, then great, but if there are any issues then you are, as they say "on your own" :)

Cheers,

Aran

On Sun, Nov 15, 2009 at 4:11 PM, Ken Berry Media <mediake...@gmail.com> wrote:

Although the webpage utilizing SWFObject2.2 is served over the
Internet as HTML, this version does appear entirely compatible with
XHTML and the above mentioned MIME type.  So although SWFObject2.2
does not officially support XHTML, my experience has not produced any
notable issues except success.

reference:  http://www.kenberrymedia.illuminae.com/

[Ken Berry Media]

Thank you Alan,

XHTML 1.0 Strict and XHTML 1.1 are recommended to be served over the
Internet with the "application/xml+xhtml" MIME type. I understand;
therefore, that you are suggesting that users of XHTML incorporating
SWFObject 2.2 should serve their documents with the "text/html" MIME
type.

My testing indicates that although SWFObject 2.2 does not officially
support the "application/xml+application" MIME type, well formed XHTML
documents incorporating the "application/xml+xhtml" MIME type and
utilizing SWFObject 2.2 should not have any issues with current
Browsers. Of course, Javascript must also be enabled in the head of
the document with "content-script-type" set to "text/javascript."

Here is the W3C reference dated January 2009:

http://www.w3.org/TR/xhtml-media-types/

Ken

On Nov 15, 4:45 pm, Aran Rhee <aran.r...@gmail.com> wrote:
> XHTML is officially supported (as noted in our docs, all examples are XHTML
> 1.0 strict doctype).
>
> We don't however officially support the XHTML + XML mime type for the
> reasons stated on the documentation page. If your page is working, then
> great, but if there are any issues then you are, as they say "on your own"
> :)
>
> Cheers,
> Aran
>
> On Sun, Nov 15, 2009 at 4:11 PM, Ken Berry Media

> <mediakenberr...@gmail.com>wrote:

[Ken Berry Media]

If I recall correctly, it is also necessary to include:

<meta name="content-object-type" content="application/x-shockwave-
flash" />

in the head of the XHTML document served as application/xml+xhtml.
This additional code prepares all non-IE browsers properly for the
SWFObject 2.2 non-IE <object> subroutine.

Ken

On Nov 16, 11:16 am, Ken Berry Media <mediakenberr...@gmail.com>