danriegsecker / swfobject

Automatically exported from code.google.com/p/swfobject
0 stars 0 forks source link

Invalid target in .js code? #209

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Apply the swf Object 2/2.1 to a swf file in a webpage.

2. When web page is monitored using HTTP Watch (http://www.httpwatch.com)
an invalid path is found and gives an error. Invalid path seems to be
coming from swfobject.js

3. This error is also found while using http watch on the sample template
file provided with the SWFobject 2/2.1 zip file.

What is the expected output? What do you see instead?

Expected output is http watch to show no invalid file paths and no errors
in finding any files.

What version of the product are you using? On what operating system?

2/2.1 - Issue is found on both versions. Operating system is Windows XP

Original issue reported on code.google.com by danee...@gmail.com on 30 Oct 2008 at 9:54

GoogleCodeExporter commented 9 years ago
RE: an invalid path is found and gives an error

What's the invalid path and the error?

Original comment by bobbyvandersluis on 31 Oct 2008 at 10:35

GoogleCodeExporter commented 9 years ago
I'm betting it's failing to find "expressInstall.swf".... that's where my money 
is 
at.  :)

Original comment by get...@gmail.com on 31 Oct 2008 at 4:04

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Well express install works fine so it does seem to find it. Actually this is an 
error
that we can see happening outside of our sites as well. We ran http watch on 
these
two links I found on this site

http://www.bobbyvandersluis.com/swfobject/testsuite_2_1/test.html
http://www.bobbyvandersluis.com/swfobject/testsuite_2_1/test_dynamic.html

And it has the same error on both links. Any suggestions?

The invalid path is "http:/:/". Like I said from what we have gathered it 
apparently
comes from the .js file. I don't know Javascript but it looks like that invalid 
path
is hard-coded in the .js file if I'm not mistaken.

Original comment by danee...@gmail.com on 31 Oct 2008 at 8:16

GoogleCodeExporter commented 9 years ago
Ok, this comes from the deferred script to make the domload work in IE, which
requires some trickery.

My question is, although your tool says it's an invalid path, we have good 
reasons to
use this construct. It's offering functionality and not causing any bugs, so 
what's
the real problem?

Original comment by bobbyvandersluis on 1 Nov 2008 at 9:11

GoogleCodeExporter commented 9 years ago
Ok, I don't think that this is causing any trouble.

Original comment by bobbyvandersluis on 2 Nov 2008 at 8:15

GoogleCodeExporter commented 9 years ago
No real problem persay except it had an invalid path and was coming from the swf
object script so I figured maybe I should at least let someone know this was
happening in case it was something that had been missed. Glad to know it is a 
non-issue:)

Original comment by danee...@gmail.com on 3 Nov 2008 at 3:55

GoogleCodeExporter commented 9 years ago
Got more descriptive feedback from production dept:

"What our concern is, is that when the page loads, it pauses on the error and 
then
continues loading.  It seems that the error is causing the page to load slower 
than
normal. When the page loads, you can see the HTTP watch pause on the error.  
Then,
the page continues loading and everything else comes in."

Just wanted to post that since it was a bit more descriptive of the possible 
problems
this may cause. Anyway thanks for looking into this.

Original comment by danee...@gmail.com on 3 Nov 2008 at 9:20

GoogleCodeExporter commented 9 years ago
Ok, I have added this as an argumet to issue report 165:
http://code.google.com/p/swfobject/issues/detail?id=165

Original comment by bobbyvandersluis on 4 Nov 2008 at 9:40