5 Replies Latest reply on Nov 1, 2006 5:15 PM by dee-man

    SWF loading issue in MSIE

      I am an experienced Flash developer, but I have never seen this before.

      Here is what is going on:
      My page calls a JavaScript function (from an included JS) that does Flash version detection and then writes the <object> into the page if the Major version is 7 or newer. This seems to work fine in every browser I have tried it in, but I have just encountered a really strange problem with it in MSIE 6 on Windows XP ...

      The SWF loads and displays correctly if viewed at this URL: www.silverdock.com

      The SWF doesn't load at all, but IE renders a box with a scrollbar in its place at this URL: www.silverdock.com/index.html

      These two URLs are displaying the same exact HTML file (I have double and triple checked this).

      The <object> tag's contents look like this:

      <object width="400" height="300">
      <param name="movie" value=" http://v2.silverdock.com/fl/sdp_v2.1.11.swf?c=101&v=1" />
      <param name="quality" value="high" />
      <param name="wmode" value="transparent" />
      <embed src=" http://v2.silverdock.com/fl/sdp_v2.1.11.swf?c=101&f=&v=1" quality="high" wmode="transparent" type="application/x-shockwave-flash" width="400" height="300"></embed>

      Does anyone know what the problem is?

      Any suggestions would be appreciated greatly.
        • 1. Re: SWF loading issue in MSIE
          TimSymons Level 1
          I see no difference when I test your links. The pages look exactly the same. I am using XP SP2 with IE 6.0.2900.2180.xpsp_sp2_gdr.050301-1519

          Since you are experienced, I hesitate in mentioning this because you probably have already tried it but try clearing your Cache, Forms and Passwords. To clear your Forms and Passwords, you will need to select the Content tab under Internet Tools. Then select the Auto Complete button.

          • 2. Re: SWF loading issue in MSIE
            Level 1
            I have certainly tried clearing cache without any effect, but thanks for taking the time to look at this.

            I am running:
            Windows XP Professional (Service Pack 2)
            MSIE 6.0.2900.2180.xpsp_sp2_gdr.050301-1519
            Flash Player 9,0,16,0

            I don't think this bug is limited to this version of the Flash Player (in fact I think it is a MSIE problem, as other machines in the office show the same behaviour with different versions of the Flash Player (including player 8).

            Also, this was brought to my attention by the customer who discovered the behaviour (we didn't build their site, just the Flash video player and the PHP application that drives it -- including the dynamically generated JS include that writes the SWF into the page).

            Now I am even more mystified, since I was under the impression this was an IE issue, but you aren't seeing it with the same version of IE, yet our customer's systems are all showing as are our internal ones ...

            Anyone else have any light to shed on this issue?
            • 3. Re: SWF loading issue in MSIE
              TimSymons Level 1
              OK, here is ironic. I told you to clear your cache but the only reason it worked for me the first time was because I was looking at a cached version and not the separate links.

              Once I set my browser and Proxy server correctly I see what you described and noticed the following. I viewed your source HTML and saw this:

              http://v2.silverdock.com/fl/sdp_v2.1.11.swf?c=101&f=&v=1&i=http%3A%2F%2Fwww.silverdock.com %2Findex.html

              This line of code was on the version that did not work.

              http://v2.silverdock.com/fl/sdp_v2.1.11.swf?c=101&f=&v=1&i=http%3A%2F%2Fwww.silverdock.com %2F

              This was the line of code on the version that did work.

              Now, I know that you are generating these dynamically which is why they were different, however, if you copy and paste those 2 links into your browser's Address bar you will see that the first one does not work while the second one does.

              Since you are passing them into the Flash file it would seem that the something is happening in the Flash file that doesn't like the additional "index.html" portion of the location string.

              It may be a place to start also it doesn't match with what you posted as being in the <object> tag in your first message.

              To get these two strings I brought up each page. Then in the address bar I typed the following:


              When the window updated, I viewed the source of the page.

              • 4. Re: SWF loading issue in MSIE
                Level 1
                Thanks Tim, I think you're on to something there.

                I was focused on this being something in Internet Explorer not liking the code, because it works fine in Firefox, but I noted that passing those two different query URLs directly (I clicked the links in your post) has different results in IE ... URL that includes the complete path as a GET argument doesn't work in IE while the other one does (Again different from Firefox).

                So the problem is not solved, but that does help to narrow it down ... now to figure out why the Flash Player (in MSIE) doesn't like that argument on the URL ...
                • 5. Re: SWF loading issue in MSIE
                  Level 1
                  Big thanks to TimSymons for providing some insight that helped solve this one.

                  As it turns out, the problem was caused by the runtime variables being passed to the SWF as GET arguments. The line of code in the embed that was causing the SWF's loading failure was this:

                  <param name="movie" value=" http://v2.silverdock.com/fl/sdp_v2.1.11.swf?c=101&f=&v=1&i=http%3A%2F%2Fwww.silverdock.com %2Findex.html" />

                  Simply re-ordering the runtime variables in the embed solved the problem:

                  <param name="movie" value=" http://v2.silverdock.com/fl/sdp_v2.1.11.swf?c=101&v=1&i=http%3A%2F%2Fwww.silverdock.com%2F index.html&f=" />

                  As I said, I don't really know WHY this worked, but it did work, so for now the problem is solved and I can try to isolate the behaviour more at my leisure.