Hi Chad.

Yep, SWFObject does not support application/xhtml+xml as stated on the
documentation page:

Does SWFObject 2 support MIME type application/xhtml+xml?

SWFObject 2 does NOT support XML MIME types, which is a design decision.

There are a number of reasons why we are not supporting this:

   - Only a very small (non-significant) amount of web authors is using it
   - We are unsure if it is the direction to go. Internet Explorer does not
   support it and all other major browser vendors are aiming their arrows at a
   new standard way of HTML parsing (with HTML 5), which departs from the
   current W3C vision of parsing HTML as XML
   - We save a considerate amount of file size and effort (testing, issue
   resolving) by not supporting it



You can try the latest SWFObject v2.3 beta on GIT (
https://github.com/swfobject/swfobject ), as there has been considerable
code changes which *could mean* it now works...


Cheers,
Aran


On Fri, Oct 7, 2011 at 12:46 PM, Chad Roberts <[email protected]>wrote:

> I have seen a couple of messages that seem to touch on the problem
> that I'm seeing, but none of them seemed to fully address what I'm
> seeing with my application, or perhaps I missed something critical
> somewhere along the way.  Hopefully, someone can point me in the right
> direction.
>
> When I use the content type of "application/xhtml+xml" on my page, IE9
> winds-up giving me the following exception:  SCRIPT5022: DOM
> Exception:  SYNTAX_ERR (12).
>
> I looked into swfobject to see the function (in swfobject.js) that is
> generating the exception.  It appears below.
>
>        function createIeObject(url) {
>                var div = document.createElement("div");
>                div.innerHTML = "<object classid='clsid:D27CDB6E-
> AE6D-11cf-96B8-444553540000'><param name='movie' value='"
>                                + url + "'></object>";
>                return div.firstChild;
>        }
>
> Tracing it through, I can see that the "div.innerHTML =" statement is
> what is blowing up.
>
> My first thought was to close the <param> element, which successfully
> made the exception go away, but had the unfortunate side-effect of my
> movie not loading/playing.
>
> Eventually, I wound-up changing my content type to text/html for IE9
> and that made the exception go away and my movie played properly.
>
> I would rather avoid needing to use a different content type for IE9,
> especially since IE9 is supposed to support the application/xhtml+xml
> content type nicely and all other browsers seem to be working properly
> with it.
>
> Has anyone else here faced the same problem?  More importantly, has
> anyone here fixed or worked-around the same problem?
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "SWFObject" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/swfobject?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"SWFObject" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/swfobject?hl=en.

Reply via email to